Heartbeat abnormal data recording method, system and device, medium and program product

Abstract

The embodiment of the invention discloses a heartbeat abnormal data recording method, system and device, a medium and a program product. The heartbeat abnormal data recording method comprises the following steps: receiving current version data sent by a system on chip after each power-on through a control unit; monitoring the heartbeat state of the system on chip after each power-on; and carrying out associated storage on the heartbeat abnormal data of the abnormal heartbeat state of the system-on-chip after each power-on and the corresponding current version data. It can be seen that the version data and the heartbeat abnormal data corresponding to the system-on-chip are stored for the process after each time of power-on of the system-on-chip, a data basis is provided for follow-up analysis of the relation between the heartbeat abnormal phenomenon and the version of the system-on-chip, the analysis strength of abnormal operation of the system is improved, and the reliability of the system is improved. The method can effectively help engineers to understand heartbeat abnormal conditions of different software versions, and guarantee is provided for stability of hardware.

Description

Technical Field

[0001] The present invention relates to the field of communication technologies, and in particular, to a method, a system, a device, a medium, and a program product for recording heartbeat abnormal data. Background Art

[0002] A heartbeat signal is a periodic signal or message used to confirm whether both communication parties are still in a connected state and to detect whether the communication link is normal. In systems that require maintaining the stability and reliability of a communication connection, the heartbeat signal plays a very important role in data transmission.

[0003] In the related art, a microcontroller unit (MCU) only monitors and records whether the heartbeat is abnormal and cannot record the heartbeat abnormal data of multiple versions of the system. Therefore, how to record the heartbeat abnormal data of multiple versions of the system is an urgent problem to be solved currently. Summary of the Invention

[0004] Embodiments of the present application provide a method, a system, a device, a medium, and a program product for recording heartbeat abnormal data, solve the technical problem in the prior art that only monitors and records whether the heartbeat is abnormal and cannot record the heartbeat abnormal data of multiple versions of the system, and achieve the technical effect of recording the heartbeat abnormal data of multiple versions of the system.

[0005] In a first aspect, the present application provides a method for recording heartbeat abnormal data, which is applied to a control unit connected to a system on a chip. The method includes:

[0006] Receiving current version data sent by the system on a chip after each power-on;

[0007] Monitoring the heartbeat state of the system on a chip after each power-on;

[0008] Associatively storing the heartbeat abnormal data with an abnormal heartbeat state that occurs after each power-on of the system on a chip and the corresponding current version data.

[0009] Further, after receiving the current version data sent by the system on a chip after each power-on, the method further includes:

[0010] Judging whether the current version data sent by the system on a chip after this power-on matches the current version data sent by the system on a chip after the previous power-on;

[0011] If the current version data corresponding to the on-chip system in this power-on and the previous power-on match, the step of associating and storing the heartbeat anomaly data with abnormal heartbeat status that appears after each power-on of the on-chip system with the corresponding current version data includes:

[0012] Based on the heartbeat anomaly data and the corresponding current version data that have been stored by the control unit after the previous power-on of the on-chip system, accumulate the heartbeat anomaly data that appears after the on-chip system is powered on this time, and associate and store the accumulated heartbeat anomaly data with the corresponding current version data.

[0013] Further, if the current version data corresponding to the on-chip system in this power-on and the previous power-on do not match, the step of associating and storing the heartbeat anomaly data with abnormal heartbeat status that appears after each power-on of the on-chip system with the corresponding current version data includes:

[0014] Assign an initial value to the heartbeat anomaly data corresponding to the current version data after the on-chip system is powered on this time;

[0015] Based on the initial value, accumulate the heartbeat anomaly data that appears after the on-chip system is powered on this time, and associate and store the accumulated heartbeat anomaly data with the corresponding current version data.

[0016] Further, if the current version data corresponding to the on-chip system in this power-on and the previous power-on do not match, the step of associating and storing the heartbeat anomaly data with abnormal heartbeat status that appears after each power-on of the on-chip system with the corresponding current version data includes:

[0017] Judge whether the total number of versions corresponding to the current version data already stored in the control unit is greater than or equal to a preset quantity threshold;

[0018] In the case where the total number of versions corresponding to the current version data already stored in the control unit exceeds the preset quantity threshold, delete the earliest stored current version data and the corresponding heartbeat anomaly data in the control unit;

[0019] Associate and store the heartbeat anomaly data with abnormal heartbeat status that appears after the on-chip system is powered on this time with the corresponding current version data.

[0020] Further, in the case where the total number of versions corresponding to the current version data already stored in the control unit does not exceed the preset quantity threshold, the method further includes:

[0021] On the basis of retaining the current version data and the corresponding heartbeat anomaly data stored by the system-on-chip before this power-on, the heartbeat anomaly data of the system-on-chip with abnormal heartbeat status after this power-on is associated and stored with the corresponding current version data.

[0022] Further, after receiving the current version data sent by the system-on-chip after each power-on, the method further includes:

[0023] Sending each of the current version data and the corresponding heartbeat anomaly data locally stored in the control unit to the system-on-chip for storage by the system-on-chip.

[0024] Further, the control unit is connected to a remote diagnosis unit, and the method further includes:

[0025] Receiving and in response to a data request instruction sent by the remote diagnosis unit, returning to the remote diagnosis unit each of the current version data and the corresponding heartbeat anomaly data locally stored in the control unit.

[0026] In a second aspect, the present application provides a method for recording heartbeat anomaly data, which is applied to a system-on-chip. The system-on-chip is connected to a control unit, and the method includes:

[0027] After each power-on of the system-on-chip, sending current version data to the control unit; the control unit is used to receive the current version data sent by the system-on-chip after each power-on, monitor the heartbeat status of the system-on-chip after each power-on, and associate and store the heartbeat anomaly data of the system-on-chip with abnormal heartbeat status after each power-on with the corresponding current version data.

[0028] Further, after sending the current version data to the control unit, the method further includes:

[0029] Receiving each of the current version data and the corresponding heartbeat anomaly data sent by the control unit and storing them locally in the system-on-chip.

[0030] Further, the system-on-chip is connected to a remote diagnosis unit. After each power-on of the system-on-chip, the method further includes:

[0031] Receiving and in response to a data request instruction sent by the remote diagnosis unit, returning to the remote diagnosis unit each of the current version data and the corresponding heartbeat anomaly data locally stored in the system-on-chip.

[0032] Further, the method further includes:

[0033] After a version change occurs in the system-on-chip, update the current version data; the version change includes version upgrade and version rollback;

[0034] After the system-on-chip is powered on next time, send the updated current version data to the control unit.

[0035] In a third aspect, the present application provides a control system, the control system includes a control unit and a system-on-chip, the control unit is connected to the system-on-chip, the control unit is configured to execute to implement a method for recording heartbeat anomaly data provided in the first aspect, and the system-on-chip is configured to execute to implement a method for recording heartbeat anomaly data provided in the second aspect.

[0036] In a fourth aspect, the present application provides a device for recording heartbeat anomaly data, which is applied to a control unit, the control unit is connected to a system-on-chip, and the device includes:

[0037] A version receiving module, configured to receive the current version data sent by the system-on-chip after each power-on;

[0038] A heartbeat monitoring module, configured to monitor the heartbeat state of the system-on-chip after each power-on;

[0039] A heartbeat anomaly storage module, configured to associate and store the heartbeat anomaly data with the corresponding current version data when the heartbeat state of the system-on-chip is abnormal after each power-on.

[0040] Further, the heartbeat anomaly storage module is further configured to:

[0041] After receiving the current version data sent by the system-on-chip after each power-on, determine whether the current version data sent by the system-on-chip after this power-on matches the current version data sent by the system-on-chip after the previous power-on;

[0042] If the current version data corresponding to this power-on and the previous power-on of the system-on-chip match, based on the heartbeat anomaly data and the corresponding current version data already stored by the control unit after the previous power-on of the system-on-chip, accumulate the heartbeat anomaly data that appears after this power-on of the system-on-chip, and associate and store the accumulated heartbeat anomaly data with the corresponding current version data.

[0043] Further, the heartbeat anomaly storage module is further configured to:

[0044] If the current version data corresponding to the on-chip system in this power-on and the last power-on does not match, assign an initial value to the heartbeat anomaly data corresponding to the current version data after this power-on of the on-chip system;

[0045] On the basis of the initial value, accumulate the heartbeat anomaly data that appears after this power-on of the on-chip system, and store the accumulated heartbeat anomaly data in association with the corresponding current version data.

[0046] Further, the heartbeat anomaly storage module is further configured to:

[0047] If the current version data corresponding to the on-chip system in this power-on and the last power-on does not match, determine whether the total number of versions corresponding to the current version data already stored in the control unit is greater than or equal to a preset number threshold;

[0048] When the total number of versions corresponding to the current version data already stored in the control unit exceeds the preset number threshold, delete the earliest stored current version data and the corresponding heartbeat anomaly data in the control unit;

[0049] Store the heartbeat anomaly data of the on-chip system with an abnormal heartbeat state after this power-on in association with the corresponding current version data.

[0050] Further, the heartbeat anomaly storage module is further configured to:

[0051] When the total number of versions corresponding to the current version data already stored in the control unit does not exceed the preset number threshold, on the basis of retaining the current version data and the corresponding heartbeat anomaly data already stored by the on-chip system before this power-on, store the heartbeat anomaly data of the on-chip system with an abnormal heartbeat state after this power-on in association with the corresponding current version data.

[0052] Further, the heartbeat sending module is configured to:

[0053] After receiving the current version data sent by the on-chip system after each power-on, send each current version data and the corresponding heartbeat anomaly data locally stored in the control unit to the on-chip system for storage by the on-chip system.

[0054] Further, the control unit is connected to a remote diagnosis unit, and the device further includes a data request response module, configured to:

[0055] Receive and in response to a data request instruction sent by the remote diagnosis unit, return to the remote diagnosis unit each piece of the current version data locally stored in the control unit and the corresponding heartbeat anomaly data.

[0056] In a fifth aspect, the present application provides a heartbeat anomaly data recording device applied to a system-on-chip, where the system-on-chip is connected to a control unit, and the device includes:

[0057] A version sending module, configured to send current version data to the control unit after each power-on of the system-on-chip; the control unit is configured to receive the current version data sent by the system-on-chip after each power-on, monitor the heartbeat status of the system-on-chip after each power-on, and associate and store the heartbeat anomaly data of the system-on-chip with an abnormal heartbeat status after each power-on with the corresponding current version data.

[0058] Further, a receiving and storing module, configured to:

[0059] After sending the current version data to the control unit, receive each piece of the current version data and the corresponding heartbeat anomaly data sent by the control unit, and store them locally in the system-on-chip.

[0060] Further, the system-on-chip is connected to a remote diagnosis unit, and the device further includes a data response module, configured to:

[0061] After each power-on of the system-on-chip, receive and in response to a data request instruction sent by the remote diagnosis unit, return to the remote diagnosis unit each piece of the current version data locally stored in the system-on-chip and the corresponding heartbeat anomaly data.

[0062] Further, the device further includes a version update module, configured to:

[0063] After a version change occurs in the system-on-chip, update the current version data; the version change includes version upgrade and version rollback;

[0064] After the next power-on of the system-on-chip, send the updated current version data to the control unit.

[0065] In a sixth aspect, the present application provides a non-transitory computer-readable storage medium, when instructions in the storage medium are executed by a processor of an electronic device, enabling the electronic device to execute and implement a heartbeat anomaly data recording method provided in the first aspect, or enabling the electronic device to execute and implement a heartbeat anomaly data recording method provided in the second aspect.

[0066] In a seventh aspect, the present application provides a computer program product, including computer instructions, which are executed by a processor to implement a method for recording heartbeat anomaly data as provided in the first aspect, or the computer instructions are executed by the processor to implement a method for recording heartbeat anomaly data as provided in the second aspect.

[0067] One or more technical solutions provided in the embodiments of the present application have at least the following technical effects or advantages:

[0068] In the embodiments of the present application, the control unit receives the current version data sent by the system-on-chip after each power-on; monitors the heartbeat status of the system-on-chip after each power-on; and associates and stores the heartbeat anomaly data with abnormal heartbeat status after each power-on of the system-on-chip with the corresponding current version data. It can be seen that in the embodiments of the present application, for the process after each power-on of the system-on-chip, the corresponding version data and heartbeat anomaly data of the system-on-chip are stored, providing a data basis for analyzing the relationship between the heartbeat anomaly phenomenon and the system-on-chip version in the subsequent stage, improving the analysis intensity of the abnormal operation of the system, and effectively helping engineers understand the heartbeat anomaly conditions of different software versions, providing guarantee for the stability of the hardware. BRIEF DESCRIPTION OF THE DRAWINGS

[0069] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the following will briefly introduce the drawings required for the description of the embodiments. Obviously, the drawings in the following description are some embodiments of the present invention. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative efforts.

[0070] Figure 1 It is a schematic flowchart of a method for recording heartbeat anomaly data provided by an embodiment of the present application;

[0071] Figure 2 It is a schematic flowchart of the interaction among a control unit, a system-on-chip, and a remote diagnosis unit provided by an embodiment of the present application;

[0072] Figure 3 For the present application, an embodiment provides Figure 1 The corresponding schematic structural diagram of a device for recording heartbeat anomaly data. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0073] By providing a method for recording heartbeat anomaly data in the embodiments of the present application, the technical problem in the prior art that only monitors and records whether the heartbeat is abnormal and cannot record the heartbeat anomaly data of multiple versions of the system is solved.

[0074] The overall idea of the technical solution in the embodiments of the present application to solve the above technical problem is as follows:

[0075] In the embodiment of the present application, the control unit receives the current version data sent by the system on chip after each power-on; monitors the heartbeat status of the system on chip after each power-on; and stores the heartbeat abnormal data corresponding to the abnormal heartbeat status of the system on chip after each power-on in association with the corresponding current version data. It can be seen that in the embodiment of the present application, for each process after the system on chip is powered on, the corresponding version data and heartbeat abnormal data of the system on chip are stored, providing a data basis for analyzing the relationship between the heartbeat abnormal phenomenon and the version of the system on chip in the subsequent stage, improving the analysis intensity of the abnormal operation of the system, and effectively helping engineers understand the heartbeat abnormal conditions of different software versions, providing guarantee for the stability of the hardware.

[0076] In order to better understand the above technical solution, the above technical solution will be described in detail below in conjunction with the accompanying drawings of the specification and specific embodiments.

[0077] First, it should be noted that the term "and / or" appearing in this article is only a description of the association relationship of associated objects, indicating that there can be three relationships. For example, A and / or B can represent: A exists alone, A and B exist simultaneously, and B exists alone. In addition, the character " / " in this article generally represents an "or" relationship between the front and rear associated objects.

[0078] The heartbeat signal is a periodic signal or message used to confirm whether both communication parties are still in a connected state and to detect whether the communication link is normal. For example, in a modern intelligent hardware system, as the core processing units, the control unit MCU and the system on chip (SOC for short) need to monitor the heartbeat of the SOC when exchanging data and performing control operations to ensure smooth communication and normal operation of the hardware.

[0079] In the related art, the control unit MCU only monitors whether the heartbeat is abnormal and records it in the log. When an engineer needs to obtain heartbeat-related data, it can be obtained from the log. It should be noted that the control unit can only monitor whether the heartbeat is abnormal and record it in the log. The heartbeat data monitored by the control unit is independent of the version of the system on chip, that is, the analysis of the heartbeat abnormal phenomenon occurring in the system on chip based on the heartbeat data monitored by the control unit is limited. Further, the version of the system on chip is updated and iterated relatively fast, and the control unit cannot record the heartbeat abnormal data of multiple versions of the system on chip, so it cannot provide engineers with the heartbeat loss statistics of each version, resulting in insufficient diagnosis of the abnormal operation of the system. Therefore, how to record the heartbeat abnormal data of multiple versions of the system is an urgent problem to be solved currently.

[0080] In order to solve the above problems, an embodiment of the present application provides a method for recording abnormal heartbeat data, which is applied to a control unit, and the control unit is connected to a system on a chip. The method includes steps S11 to S13, such as Figure 1 shown.

[0081] Step S11, receiving current version data sent by the system on chip after each power-on;

[0082] Step S12, monitoring the heartbeat status of the system on chip after each power-on;

[0083] Step S13, storing the abnormal heartbeat data of the abnormal heartbeat state after each power-on of the system on chip in association with the corresponding current version data.

[0084] An abnormal heartbeat data recording method (including step S11-step S13) provided in an embodiment of the present application can be executed by any control unit that can monitor a heartbeat signal. The control unit is connected to the system on chip for communication. Relative to the system on chip, the role of the control unit is to ensure the operational stability of the system. In order to ensure the stability of the control unit, the software update iteration frequency of the control unit is lower than the software update iteration frequency of the system on chip. Relative to the control unit, the role of the system on chip is to provide users with more diversified software services. In order to meet the diversified needs of users as much as possible, the software update iteration frequency of the system on chip is higher than the software update iteration frequency of the control unit.

[0085] Regarding step S11, current version data sent by the system on chip after each power-on is received.

[0086] Whenever the control unit receives the corresponding startup instruction, it will power on the system on chip. After the system on chip is powered on, it needs to send a heartbeat signal to the control unit for the control unit to determine whether the system on chip has been powered on normally.

[0087] On the control unit side, if the heartbeat signal is not received within the preset time period, it means that the system on chip is not powered on normally, and the system on chip can be restarted, that is, the system on chip can be powered on again. If the system on chip cannot be powered on normally, an error prompt can be reported. If the control unit receives the heartbeat signal sent by the system on chip within the preset time period, it means that the system on chip is powered on normally.

[0088] After the system on chip is powered on normally, the control unit establishes remote procedure call communication (remote procedure call protocol, referred to as RPC) with the system on chip. From then on, data exchange can be realized between the system on chip and the control unit through the RPC protocol.

[0089] After establishing the RPC, the system-on-chip sends the current version data corresponding to its current version to the control unit. Herein, the current version data refers to the data that can characterize the current version model of the system-on-chip. For example, the current version data can be the ASCII codes of the last two letters in the current software version number of the system-on-chip. For instance, if the current software version number is H37A3632825BD, the current version data sent by the system-on-chip is the ASCII codes of the penultimate letter B and the last letter D, i.e., [66, 68].

[0090] It should be noted that although the MCU also performs heartbeat monitoring in the related art, the MCU does not know the version number of the SOC. That is to say, in the related art, the SOC does not send the current version information of the SOC to the MCU, resulting in the independence of the heartbeat monitoring data of the MCU and the software version of the SOC. In the embodiment of the present application, the SOC sends its own current version data to the MCU after each power-on, enabling the MCU to statistically analyze the heartbeat anomaly data in combination with the current version model of the SOC, providing diagnostic data for the heartbeat anomaly phenomenon, and facilitating the analysis of the heartbeat anomaly phenomenon.

[0091] Regarding step S12, monitor the heartbeat status of the system-on-chip after each power-on.

[0092] After the system-on-chip sends the current version data to the control unit, the control unit monitors whether the heartbeat status of the system-on-chip is normal after power-on. If the heartbeat status is detected to be abnormal, step S13 is executed. If the heartbeat status is normal, continue to monitor until the heartbeat status is abnormal or a shutdown instruction is received.

[0093] Among them, the control unit monitors whether the heartbeat status is normal mainly relying on timeout monitoring. For example, the system-on-chip sends a heartbeat signal to the control unit at a preset frequency, and the control unit uses a timer to determine whether the system-on-chip times out in sending the heartbeat signal. If it times out, it means that the current heartbeat status is abnormal.

[0094] Regarding step S13, associate and store the heartbeat anomaly data of the system-on-chip with abnormal heartbeat status after each power-on with the corresponding current version data.

[0095] When the system-on-chip has an abnormal heartbeat status after power-on, accumulate the heartbeat anomaly data, associate the accumulated heartbeat anomaly data with the corresponding current version data, and then store it. The heartbeat anomaly data can refer to the number of heartbeat losses.

[0096] For example, if the current version data is BE and the number of heartbeat anomaly data corresponding to the normal heartbeat state after the on-chip system is powered on this time is 3 times, and if the heartbeat state becomes abnormal later, then the number of heartbeat anomaly data will be incremented by 1 from 3 times to 4 times, and then BE and 4 will be associated and stored.

[0097] It should be noted that for each process after the on-chip system is powered on, steps S11 - S13 can be executed, enabling the control unit to store the version data of the on-chip system and its corresponding heartbeat anomaly data, thereby providing a data basis for subsequent analysis of the relationship between the heartbeat anomaly phenomenon and the on-chip system version, and enhancing the analysis of the abnormal operation of the system.

[0098] The control unit can use the byte stream method to structurally store different current version data and their corresponding heartbeat anomaly data, ensuring the persistence and stability of the data.

[0099] For example, as shown in Table 1, it is exemplary data of different current version data and their corresponding heartbeat anomaly data stored in the control unit. In Table 1, the data is stored sequentially from Byte0 to Byte49. Among them, every 4 Bytes correspond to a group of current version data and heartbeat anomaly data. The first Byte of the 4 Bytes stores the penultimate letter of the version number, the second Byte stores the last letter of the version number, and the third and fourth Bytes store the number of heartbeat losses corresponding to the current version number. For example, the number of heartbeat losses of version BD is stored in Byte0 - Byte3, where Byte0 stores B, Byte1 stores D, and Byte2 - 3 store 10 times. In addition, it can be seen from Byte47 - Byte49 in Table 1 that the total number of all stored versions and their heartbeat losses can also be counted for engineers' reference and analysis.

[0100] Table 1

[0101]

[0102]

[0103] In summary, in the embodiment of the present application, the control unit receives the current version data sent by the system-on-chip after each power-on; monitors the heartbeat status of the system-on-chip after each power-on; and associates and stores the heartbeat anomaly data with the corresponding current version data when the heartbeat status anomaly occurs after each power-on of the system-on-chip. It can be seen that in the embodiment of the present application, for each process after the system-on-chip is powered on, the corresponding version data and heartbeat anomaly data of the system-on-chip are stored, providing a data basis for analyzing the relationship between the heartbeat anomaly phenomenon and the system-on-chip version later, improving the analysis of the abnormal operation of the system, and effectively helping engineers understand the heartbeat anomaly conditions of different software versions, thus ensuring the stability of the hardware.

[0104] On the basis of the above solution, the embodiment of the present application also provides the following optimization solutions.

[0105] After receiving the current version data sent by the system-on-chip after each power-on, the method further includes steps S21 to S23.

[0106] Step S21: Determine whether the current version data sent by the system-on-chip after this power-on matches the current version data sent by the system-on-chip after the previous power-on.

[0107] Step S22: If the current version data corresponding to this power-on and the previous power-on of the system-on-chip match, the associative storage of the heartbeat anomaly data with the corresponding current version data when the heartbeat status anomaly occurs after each power-on of the system-on-chip includes:

[0108] On the basis of the heartbeat anomaly data and the corresponding current version data already stored by the control unit after the previous power-on of the system-on-chip, accumulate the heartbeat anomaly data that appears after this power-on of the system-on-chip, and associate and store the accumulated heartbeat anomaly data with the corresponding current version data.

[0109] Step S23: If the current version data corresponding to this power-on and the previous power-on of the system-on-chip do not match, the associative storage of the heartbeat anomaly data with the corresponding current version data when the heartbeat status anomaly occurs after each power-on of the system-on-chip includes:

[0110] Assign an initial value to the heartbeat anomaly data corresponding to the current version data after this power-on of the system-on-chip.

[0111] On the basis of the initial value, accumulate the heartbeat anomaly data that appears after this power-on of the system-on-chip, and associate and store the accumulated heartbeat anomaly data with the corresponding current version data.

[0112] Regarding step S21, for the current version data sent each time the system - on - chip is powered on, the control unit compares it with the current version data sent by the system - on - chip last time. If the two match, it means that the software version corresponding to the system - on - chip during the last power - on and the current power - on has not changed, that is, the system - on - chip has not undergone a version change, and then step S22 can be continued. If the current version data sent by the system - on - chip this time does not match the current version data sent during the last power - on, it means that the software version corresponding to the system - on - chip during the last power - on and the current power - on is different, that is, the system - on - chip has undergone a version change before this power - on, and then step S23 can be continued.

[0113] Regarding step S22, step S22 corresponds to step S13, that is, step S13 can be implemented according to step S22. If the system - on - chip has not undergone a version change before this power - on, then the heartbeat anomaly data that occurs after the system - on - chip is powered on this time should be merged with the corresponding heartbeat anomaly data after the last power - on. That is, the heartbeat anomaly data that occurs after the system - on - chip is powered on this time is accumulated on the basis of the corresponding heartbeat anomaly data after the last power - on. For example, if the version corresponding to the last power - on is BD and the number of heartbeat losses is 10 times, then the version corresponding to this power - on is still BD. If a heartbeat state anomaly occurs after this power - on, then add 1 to 10 to get 11 times, and store BD and 11 times associated in the control unit.

[0114] Regarding step S23, step S23 corresponds to step S13, that is, step S13 can be implemented according to step S23. If the system - on - chip has undergone a version change before this power - on, then the heartbeat anomaly data that occurs after the system - on - chip is powered on this time should be calculated separately. Since the system - on - chip has undergone a version change before this power - on, there is no corresponding heartbeat anomaly data for the current version data. Therefore, it is necessary to assign a value to the heartbeat anomaly data corresponding to the current version data, such as an initial value. The initial value can be selected according to the actual situation, and usually 0 is selected. That is, the heartbeat anomaly data that occurs after the system - on - chip is powered on this time is accumulated on the basis of the initial value. For example, if the version corresponding to the last power - on is BD and the number of heartbeat losses is 10 times, and the software version of the system - on - chip has changed during this power - on, and the corresponding version is BE, and the initial value 0 is assigned to the heartbeat anomaly data. If a heartbeat state anomaly occurs after this power - on, then add 1 to 0 to get 1 time, and store BE and 1 time associated in the control unit.

[0115] Furthermore, if the current version data corresponding to the system - on - chip during this power - on and the last power - on does not match, steps S31 - S33 can also be executed.

[0116] Step S31, determine whether the total number of versions corresponding to the current version data already stored in the control unit is greater than or equal to a preset quantity threshold;

[0117] Step S32, when the total number of versions corresponding to the current version data already stored in the control unit exceeds the preset quantity threshold, delete the earliest stored current version data and the corresponding heartbeat anomaly data in the control unit;

[0118] Step S33, associatively store the heartbeat anomaly data with the abnormal heartbeat state after the on-chip system is powered on this time and the corresponding current version data.

[0119] Each piece of current version data stored in the control unit is equivalent to a version model, and the total number of versions can be determined based on the number of current version data already stored in the control unit. For example, as shown in Table 1, it can be seen that there are 12 corresponding versions, so 12 is the total number of versions.

[0120] The earlier the current version data and its heartbeat anomaly data stored in the control unit, the lower their value. Therefore, an embodiment of the present application sets a preset quantity threshold to control the version data and heartbeat anomaly data that can be stored in the control unit.

[0121] If the total number of versions already stored in the control unit is greater than or equal to the preset quantity threshold, delete the earliest stored current version data and its heartbeat anomaly data in the control unit, and then store the current version data and its heartbeat anomaly data corresponding to this time. That is to say, multiple pieces of current version data and the corresponding heartbeat anomaly data stored in the control unit are stored in a way of pressing down and covering.

[0122] For example, if the total number of versions is 12 and the preset quantity threshold is 12, as shown in Table 1, it means that the control unit has already stored the heartbeat anomaly data of 12 versions. Then, it is necessary to delete the earliest stored relevant version data, that is, delete the version BD corresponding to Byte0 - Byte4 and its 10 deletions, and then move the relevant data of version BE and the subsequent version data forward, that is, move BE and 4 times to Byte0 - Byte4 for storage, and move the subsequent version data in turn. Finally, Byte44 - Byte47 is emptied, and the current version data corresponding to this power-on and the corresponding heartbeat anomaly data are associatively stored in Byte44 - Byte47.

[0123] When the total number of versions corresponding to the current version data already stored in the control unit does not exceed the preset quantity threshold, while retaining the current version data and the corresponding heartbeat anomaly data already stored in the system-on-chip before this power-on, the heartbeat anomaly data of the system-on-chip with abnormal heartbeat status after this power-on is associated and stored with the corresponding current version data.

[0124] For example, if the total number of versions is 2 and the preset quantity threshold is 12, it means that the control unit has already stored the heartbeat anomaly data of 2 versions, and there is no need to delete the relevant version data. The heartbeat anomaly data of the system-on-chip with abnormal heartbeat status after this power-on can be directly associated and stored with the corresponding current version data in the local of the control unit.

[0125] It can be seen that the embodiment of the present application stores multiple software versions and their corresponding heartbeat anomaly data in a push-down and overwrite manner. On the one hand, it can avoid occupying too much storage space in the control unit as much as possible. On the other hand, it can also ensure the update and alternation of version data and heartbeat anomaly data, thereby ensuring that the data provided for analyzing the heartbeat anomaly phenomenon is relatively the latest, and improving the analysis accuracy of the system's heartbeat anomaly phenomenon.

[0126] In the related art, if an engineer wants to obtain the heartbeat monitoring data corresponding to the control unit, he can only obtain it from the local log of the control unit, and cannot obtain it through remote means. To solve this problem, the embodiment of the present application provides a further optimized solution on the basis of the foregoing solution.

[0127] Specifically, when the control unit is connected to the remote diagnosis unit, the control unit receives and responds to the data request instruction sent by the remote diagnosis unit, and returns each of the current version data locally stored in the control unit and the corresponding heartbeat anomaly data to the remote diagnosis unit.

[0128] That is to say, a communication channel is established between the remote diagnosis unit and the control unit, so that the remote diagnosis unit can directly obtain each different current version data and its corresponding heartbeat anomaly data pre-stored in the control unit, realize remote and rapid fault troubleshooting, improve the fault repair efficiency, and enhance the user experience.

[0129] However, in order to ensure the stability of the control unit during the operation of the entire system, it is necessary to limit the access frequency of the remote diagnosis unit to the control unit, and try to reduce the occurrence probability of system jamming and narrow bandwidth caused by the remote diagnosis unit accessing the control unit multiple times. For example, the access frequency can be limited so that the interval time between every two adjacent data request instructions sent by the remote diagnosis unit is not less than 20 seconds.

[0130] Furthermore, in addition to directly obtaining various different version data and their heartbeat anomaly data from the control unit, the remote control unit can also obtain them from the system-on-chip. Specifically, after the control unit receives the current version data sent by the system-on-chip after each power-on, the control unit sends each of the current version data stored locally in the control unit and the corresponding heartbeat anomaly data to the system-on-chip for storage by the system-on-chip.

[0131] The system-on-chip stores various different version data and their heartbeat anomaly data in the local log of the system-on-chip. For the system-on-chip, after each power-on, the various different version data and their heartbeat anomaly data stored by the system-on-chip are statically stored. The remote diagnosis unit can directly access the system-on-chip to obtain various different version data and their heartbeat anomaly data. This can enable the remote diagnosis unit to obtain the desired data and avoid affecting the normal operation of the control unit due to frequent access by the remote diagnosis unit. That is to say, the control unit only needs to send various different version data and their heartbeat anomaly data to the system-on-chip for storage, and thus will not be affected by the remote diagnosis unit, ensuring the stable operation of the control unit.

[0132] In addition, during the process of the control unit monitoring the heartbeat state of the system-on-chip after each power-on, in the case where the system-on-chip has a heartbeat state anomaly each time, the control unit controls the system-on-chip to restart power-on, and then returns to execute step S11 - step S13.

[0133] Furthermore, when the control unit identifies that any of the heartbeat anomaly data is a preset limit value, an error alarm prompt is generated. For example, if the preset limit value is 65520, when the heartbeat anomaly data reaches the maximum value of 65520, the control unit will no longer continue to increase this count, which also means that there is an anomaly in the control unit. Thus, an error alarm prompt can be generated to remind relevant engineers to pay attention and repair and check in a timely manner.

[0134] In summary, in the embodiment of the present application, the control unit receives the current version data sent by the system-on-chip after each power-on; monitors the heartbeat state of the system-on-chip after each power-on; and associates and stores the heartbeat anomaly data that occurs when the system-on-chip has a heartbeat state anomaly after each power-on with the corresponding current version data. It can be seen that for each process after the system-on-chip is powered on, the embodiment of the present application stores the corresponding version data and heartbeat anomaly data of the system-on-chip, providing a data basis for analyzing the relationship between the heartbeat anomaly phenomenon and the system-on-chip version in the future, improving the analysis strength of the abnormal operation of the system, being able to effectively help engineers understand the heartbeat anomaly situations of different software versions, providing guarantee for the stability of the hardware, and realizing fast fault troubleshooting through the remote diagnosis function.

[0135] Based on the same inventive concept, an embodiment of the present application provides a method for recording heartbeat abnormal data, which is applied to a system-on-chip. The system-on-chip is connected to a control unit, and the method includes step S41.

[0136] Step S41: After each power-on of the system-on-chip, the system-on-chip sends the current version data to the control unit. The control unit is configured to receive the current version data sent by the system-on-chip after each power-on, monitor the heartbeat status of the system-on-chip after each power-on, and associate and store the heartbeat abnormal data with the corresponding current version data when the heartbeat status of the system-on-chip is abnormal after each power-on.

[0137] Further, after sending the current version data to the control unit, the system-on-chip receives the current version data and the corresponding heartbeat abnormal data sent by the control unit and stores them locally in the system-on-chip.

[0138] Further, the system-on-chip is connected to a remote diagnosis unit. After each power-on of the system-on-chip, the system-on-chip receives and responds to a data request instruction sent by the remote diagnosis unit, and the system-on-chip returns the current version data and the corresponding heartbeat abnormal data stored locally in the system-on-chip to the remote diagnosis unit.

[0139] Further, the system-on-chip receives and responds to a restart instruction sent by the control unit.

[0140] Further, after a version change occurs in the system-on-chip, the system-on-chip updates the current version data. After the next power-on of the system-on-chip, the system-on-chip sends the updated current version data to the control unit. The version change includes version upgrade and version rollback.

[0141] It should be noted that if the system-on-chip needs to perform a version change, the process is as follows:

[0142] The control unit powers on the system-on-chip. At this time, the system-on-chip sends the current version data of the old version (the version number of the old version is BD) to the control unit, and then the system-on-chip starts to upgrade. The upgraded version is called the new version (the version number of the new version is BE). After the upgrade is completed, it restarts.

[0143] Restarting also means that the control unit powers on the system-on-chip again. At this time, the system-on-chip sends the current version data BE of the new version to the control unit.

[0144] If the system-on-chip upgrade is successful, then until the next version change of the system-on-chip occurs, the current version data of the system-on-chip is BE.

[0145] However, if the system - on - chip upgrade fails, the system - on - chip will roll back to the old version BD, and then restart again, which means that the control unit powers on the system - on - chip again. At this time, the system - on - chip sends the current version data BD of the old version to the control unit.

[0146] That is to say, even if the upgrade of the new version BE fails, the BE and its heartbeat abnormal data will be stored in the control unit.

[0147] Furthermore, when the system - on - chip recognizes that any of the heartbeat abnormal data reaches the preset limit value, it generates an error alarm prompt.

[0148] Figure 2 The figure is a schematic flowchart of the interaction among a control unit, a system - on - chip, and a remote diagnosis unit provided by an embodiment of the present application. Now, in combination with Figure 2 , the foregoing method for recording heartbeat abnormal data provided by the embodiment of the present application will be further described. As can be seen from Figure 2 , the MCU, the SOC, and the tester / remote diagnosis unit (Residual Voltage Differential Check, abbreviated as RVDC) are connected in sequence. The embodiment of the present application is described only by taking the RVDC as an example.

[0149] The MCU powers on the SOC, and the MCU starts the timer T0. If the MCU receives the heartbeat signal sent by the SOC within the T0 time, it means that the SOC is powered on normally. The MCU and the SOC establish RPC communication, and the SOC actively sends RPC data containing the SOC version number to the MCU. After receiving the SOC version number, the MCU returns RPC data containing heartbeat monitoring data (that is, each version number and its corresponding heartbeat abnormal data) to the SOC. After receiving each version number and its corresponding heartbeat abnormal data, the SOC records them in the LOG log. Then the SOC normally sends a heartbeat signal to the MCU. The MCU starts the heartbeat timer T1. If the MCU receives the heartbeat signal sent by the SOC within the T1 time, it resets T1. If the MCU does not receive the heartbeat signal sent by the SOC within the T1 time, the heartbeat loss counter counter is incremented by 1. And the MCU controls the SOC to restart. Restarting means that the MCU powers on the SOC again, and so on in a loop.

[0150] When the RVDC or the tester sends a data request instruction containing a diagnostic identifier (Diagnostic Identifier, abbreviated as DID), the SOC sends each version number and its corresponding heartbeat abnormal data stored locally to the RVDC or the tester for the RVDC or the tester to perform relevant analysis of heartbeat abnormalities.

[0151] It should be noted that each time the SOC receives the various version numbers sent by the MCU and their corresponding heartbeat anomaly data, it will store them on the basis of overwriting the previously stored various version numbers and their corresponding heartbeat anomaly data, avoiding data duplication and redundancy in the SOC and reducing the storage space occupied by the SOC.

[0152] It can be seen that through the RPC protocol data exchange method, the embodiments of the present application can effectively count and report the number of heartbeat losses of different software versions, and provide a remote diagnosis function to help engineers conduct a preliminary analysis of the heartbeat loss situation of different software versions, solving the problem of the lack of heartbeat loss statistics and effective diagnosis in the prior art.

[0153] The embodiments of the present application provide a remote diagnosis function, enabling the performance group to conveniently obtain the number of heartbeat losses of each software version. Through the RPC protocol or DID request, the remote diagnosis unit can obtain the heartbeat loss data in real time, and promptly discover and handle fault problems.

[0154] The embodiments of the present application have clear statistics on heartbeat losses, and can count and analyze the number of heartbeat losses of different software versions. The embodiments of the present application have strong abnormal scenario handling capabilities and can handle complex situations such as software version rollback and version upgrade. The remote diagnosis of the embodiments of the present application is convenient. Through the cooperation of the RPC protocol and the remote diagnosis tool, it is convenient for the performance group to conduct fault analysis and processing. The embodiments of the present application guarantee data persistence, using the push-down overwrite storage method to maximize the guarantee of data persistent storage.

[0155] The solution provided by the embodiments of the present application can effectively help performance group engineers understand the heartbeat loss situation of different software versions, provide guarantee for the stability of the hardware, and achieve rapid fault troubleshooting through the remote diagnosis function. This method can be widely applied to the heartbeat monitoring and fault diagnosis system between the MCU and the SOC.

[0156] Based on the same inventive concept, the embodiments of the present application provide a control system, including a control unit and a system on chip. The control unit is connected to the system on chip. The control unit is used to execute to implement a method for recording heartbeat anomaly data of an application in the control unit as provided above, and the system on chip is used to execute to implement a method for recording heartbeat anomaly data of an application in the system on chip as provided above.

[0157] Based on the same inventive concept, the embodiments of the present application provide as Figure 3 shown a device for recording heartbeat anomaly data, which is applied to a control unit. The control unit is connected to a system on chip. The device includes:

[0158] A version receiving module 31, configured to receive the current version data sent by the system-on-chip after each power-on;

[0159] A heartbeat monitoring module 32, configured to monitor the heartbeat status of the system-on-chip after each power-on;

[0160] A heartbeat anomaly storage module 33, configured to associatively store the heartbeat anomaly data indicating an abnormal heartbeat status of the system-on-chip after each power-on with the corresponding current version data.

[0161] Further, the heartbeat anomaly storage module 33 is further configured to:

[0162] After receiving the current version data sent by the system-on-chip after each power-on, determine whether the current version data sent by the system-on-chip after the current power-on matches the current version data sent by the system-on-chip after the previous power-on;

[0163] If the current version data corresponding to the current power-on and the previous power-on of the system-on-chip match, based on the heartbeat anomaly data and the corresponding current version data stored by the control unit after the previous power-on of the system-on-chip, accumulate the heartbeat anomaly data that appears after the current power-on of the system-on-chip, and associatively store the accumulated heartbeat anomaly data and the corresponding current version data.

[0164] Further, the heartbeat anomaly storage module 33 is further configured to:

[0165] If the current version data corresponding to the current power-on and the previous power-on of the system-on-chip do not match, assign an initial value to the heartbeat anomaly data corresponding to the current version data after the current power-on of the system-on-chip;

[0166] Based on the initial value, accumulate the heartbeat anomaly data that appears after the current power-on of the system-on-chip, and associatively store the accumulated heartbeat anomaly data and the corresponding current version data.

[0167] Further, the heartbeat anomaly storage module 33 is further configured to:

[0168] If the current version data corresponding to the current power-on and the previous power-on of the system-on-chip do not match, determine whether the total number of versions corresponding to the current version data already stored by the control unit is greater than or equal to a preset quantity threshold;

[0169] When the total number of versions corresponding to the current version data already stored in the control unit exceeds the preset quantity threshold, delete the earliest stored current version data in the control unit and the corresponding heartbeat anomaly data.

[0170] Associate and store the heartbeat anomaly data indicating that the heartbeat status of the system-on-chip is abnormal after the system-on-chip is powered on this time with the corresponding current version data.

[0171] Further, the heartbeat anomaly storage module 33 is further configured to:

[0172] When the total number of versions corresponding to the current version data already stored in the control unit does not exceed the preset quantity threshold, on the basis of retaining the current version data already stored in the system-on-chip before this power-on and the corresponding heartbeat anomaly data, associate and store the heartbeat anomaly data indicating that the heartbeat status of the system-on-chip is abnormal after the system-on-chip is powered on this time with the corresponding current version data.

[0173] Further, the heartbeat sending module is configured to:

[0174] After receiving the current version data sent by the system-on-chip after each power-on, send each piece of current version data and the corresponding heartbeat anomaly data locally stored in the control unit to the system-on-chip for storage by the system-on-chip.

[0175] Further, the control unit is connected to a remote diagnosis unit, and the device further includes a data request response module configured to:

[0176] Receive and respond to a data request instruction sent by the remote diagnosis unit, and return each piece of current version data and the corresponding heartbeat anomaly data locally stored in the control unit to the remote diagnosis unit.

[0177] Based on the same inventive concept, an embodiment of the present application provides a heartbeat anomaly data recording device applied to a system-on-chip, where the system-on-chip is connected to a control unit, and the device includes:

[0178] A version sending module, configured to send current version data to the control unit after each power-on of the system-on-chip; the control unit is configured to receive the current version data sent by the system-on-chip after each power-on, monitor the heartbeat status of the system-on-chip after each power-on, and associate and store the heartbeat anomaly data indicating that the heartbeat status of the system-on-chip is abnormal after each power-on with the corresponding current version data.

[0179] Further, a receiving and storing module is configured to:

[0180] After sending the current version data to the control unit, receive each piece of the current version data and the corresponding heartbeat anomaly data sent by the control unit, and store them locally in the system-on-chip.

[0181] Further, the system-on-chip is connected to a remote diagnosis unit, and the device further includes a data response module for:

[0182] After each power-on of the system-on-chip, receive and respond to a data request instruction sent by the remote diagnosis unit, and return to the remote diagnosis unit each piece of the current version data and the corresponding heartbeat anomaly data stored locally in the system-on-chip.

[0183] Further, the device further includes a version update module for:

[0184] After a version change occurs in the system-on-chip, update the current version data; the version change includes version upgrade and version rollback;

[0185] After the next power-on of the system-on-chip, send the updated current version data to the control unit.

[0186] Based on the same inventive concept, the present application provides a non-transitory computer-readable storage medium, which when the instructions in the storage medium are executed by a processor of an electronic device, enables the electronic device to execute a method for recording heartbeat anomaly data of an application in a control unit as provided above, or enables the electronic device to execute a method for recording heartbeat anomaly data of an application in a system-on-chip as provided above.

[0187] Based on the same inventive concept, the application provides a computer program product including computer instructions, where the computer instructions are executed by a processor to implement a method for recording heartbeat anomaly data of an application executed in a control unit as provided above, or the computer instructions are executed by a processor to implement a method for recording heartbeat anomaly data of an application executed in a system-on-chip as provided above.

[0188] Since the electronic device introduced in this embodiment is the electronic device used to implement the information processing method in the embodiments of the present application, based on the information processing method introduced in the embodiments of the present application, those skilled in the art can understand the specific implementation manners and various variations of the electronic device in this embodiment. Therefore, the specific implementation of how this electronic device implements the method in the embodiments of the present application will not be described in detail here. As long as the electronic device used by those skilled in the art to implement the information processing method in the embodiments of the present application belongs to the scope protected by the present application.

[0189] Those skilled in the art should understand that the embodiments of the present invention can be provided as a method, a system, or a computer program product. Therefore, the present invention can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Moreover, the present invention can take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk memory, CD-ROM, optical memory, etc.) that contain computer-usable program code.

[0190] The present invention is described with reference to the flowcharts and / or block diagrams of methods, apparatuses (systems), and computer program products according to embodiments of the present invention. It should be understood that each flow and / or block in the flowcharts and / or block diagrams, as well as the combination of flows and / or blocks in the flowcharts and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to the processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing devices to generate a machine, such that the instructions executed by the processor of the computer or other programmable data processing devices generate means for implementing the functions specified in Figure 1 one flow or multiple flows and / or blocks Figure 1 one block or multiple blocks.

[0191] These computer program instructions can also be stored in a computer-readable memory that can direct a computer or other programmable data processing devices to work in a specific manner, such that the instructions stored in the computer-readable memory generate a manufactured article including instruction means that implement the functions specified in Figure 1 one flow or multiple flows and / or blocks Figure 1 one block or multiple blocks.

[0192] These computer program instructions can also be loaded onto a computer or other programmable data processing devices, such that a series of operation steps are executed on the computer or other programmable devices to generate a computer-implemented process, so that the instructions executed on the computer or other programmable devices provide steps for implementing the functions specified in Figure 1 one flow or multiple flows and / or blocks Figure 1 one block or multiple blocks.

[0193] Although the preferred embodiments of the present invention have been described, those skilled in the art can make additional changes and modifications once they learn the basic creative concepts. Therefore, the appended claims are intended to be construed to include the preferred embodiments as well as all changes and modifications that fall within the scope of the present invention.

[0194] Obviously, those skilled in the art can make various modifications and variations to the present invention without departing from the spirit and scope of the present invention. Thus, if these modifications and variations of the present invention fall within the scope of the claims of the present invention and their equivalent technologies, the present invention is also intended to include these modifications and variations.

Claims

1. A method for recording abnormal heartbeat data, characterized in that: Applied to a control unit, the control unit is connected to a system on chip, the method comprises: receiving current version data sent by the system on chip after each power-on; Monitoring the heartbeat status of the system on chip after each power-on; The abnormal heartbeat data of the abnormal heartbeat state after each power-on of the system on chip is associated with the corresponding current version data and stored.

2. The method according to claim 1, characterized in that After receiving the current version data sent by the system on chip after each power-on, the method further includes: Determining whether the current version data sent by the system on chip after the current power-on matches the current version data sent by the system on chip after the last power-on; If the current version data corresponding to the last power-on of the system on chip matches the current power-on data, the abnormal heartbeat data of the abnormal heartbeat state of the system on chip after each power-on is associated with the corresponding current version data and stored, including: Based on the corresponding abnormal heartbeat data and the corresponding current version data stored by the control unit after the system on chip was last powered on, the abnormal heartbeat data that appears after the system on chip is powered on this time is accumulated, and the accumulated abnormal heartbeat data and the corresponding current version data are associated and stored.

3. The method according to claim 2, characterized in that If the current version data corresponding to the current power-on of the system on chip does not match the current version data corresponding to the last power-on of the system on chip, the abnormal heartbeat data of the abnormal heartbeat state after each power-on of the system on chip is associated and stored with the corresponding current version data, including: Assigning an initial value to the abnormal heartbeat data corresponding to the current version data of the system on chip after the current power-on; On the basis of the initial value, the abnormal heartbeat data occurring after the system on chip is powered on this time is accumulated, and the accumulated abnormal heartbeat data and the corresponding current version data are associated and stored.

4. The method according to claim 2, characterized in that If the current version data corresponding to the current power-on of the system on chip does not match the current version data corresponding to the last power-on of the system on chip, the abnormal heartbeat data of the abnormal heartbeat state after each power-on of the system on chip is associated and stored with the corresponding current version data, including: Determine whether the total number of versions corresponding to the current version data stored in the control unit is greater than or equal to a preset number threshold; When the total number of versions corresponding to the current version data stored in the control unit exceeds the preset number threshold, the earliest stored current version data and the corresponding abnormal heartbeat data in the control unit are deleted; The abnormal heartbeat data of the abnormal heartbeat state of the system on chip after the current power-on is associated with the corresponding current version data and stored.

5. The method according to claim 4, characterized in that In a case where the total number of versions corresponding to the current version data stored in the control unit does not exceed the preset number threshold, the method further includes: On the basis of retaining the current version data and the corresponding abnormal heartbeat data stored before the system on chip is powered on, the abnormal heartbeat data of the abnormal heartbeat state of the system on chip after the power-on is associated with the corresponding current version data and stored.

6. The method according to claim 1, characterized in that After receiving the current version data sent by the system on chip after each power-on, the method further includes: Each of the current version data and the corresponding abnormal heartbeat data stored locally by the control unit is sent to the system on chip for storage by the system on chip.

7. The method according to claim 1, characterized in that The control unit is connected to a remote diagnosis unit, and the method further comprises: The control unit receives and responds to a data request instruction sent by the remote diagnosis unit, and returns each of the current version data and the corresponding abnormal heartbeat data stored locally by the control unit to the remote diagnosis unit.

8. A method for recording abnormal heartbeat data, characterized in that: Applied to a system on chip, the system on chip is connected to a control unit, and the method comprises: After each power-on of the system on chip, the current version data is sent to the control unit; the control unit is used to receive the current version data sent by the system on chip after each power-on, monitor the heartbeat status of the system on chip after each power-on, and associate and store the abnormal heartbeat data of the abnormal heartbeat status of the system on chip after each power-on with the corresponding current version data.

9. The method according to claim 8, characterized in that After sending the current version data to the control unit, the method further includes: The current version data and the corresponding abnormal heartbeat data sent by the control unit are received and stored locally in the system on chip.

10. The method according to claim 9, characterized in that The system on chip is connected to a remote diagnosis unit, and after the system on chip is powered on each time, the method further comprises: The system receives and responds to a data request instruction sent by the remote diagnosis unit, and returns each of the current version data and the corresponding abnormal heartbeat data stored locally in the system on chip to the remote diagnosis unit.

11. The method according to claim 8, characterized in that The method further comprises: After a version change occurs to the system on chip, updating the current version data; the version change includes version upgrade and version rollback; After the system on chip is powered on next time, the updated current version data is sent to the control unit.

12. A control system, characterized in that: The control system includes a control unit and a system on chip, the control unit is connected to the system on chip, the control unit is used to execute to implement a method for recording abnormal heartbeat data as described in any one of claims 1 to 7, and the system on chip is used to execute to implement a method for recording abnormal heartbeat data as described in any one of claims 8 to 11.

13. A device for recording abnormal heartbeat data, characterized in that: Applied to a control unit, the control unit is connected to a system on chip, the device comprises: A version receiving module, used for receiving current version data sent by the system on chip after each power-on; A heartbeat monitoring module, used to monitor the heartbeat status of the system on chip after each power-on; The heartbeat abnormality storage module is used to associate and store the heartbeat abnormality data of the abnormal heartbeat state after each power-on of the on-chip system with the corresponding current version data.

14. A device for recording abnormal heartbeat data, characterized in that: Applied to a system on chip, the system on chip is connected to a control unit, and the device comprises: A version sending module is used to send the current version data to the control unit after each power-on of the system on chip; the control unit is used to receive the current version data sent by the system on chip after each power-on, monitor the heartbeat status of the system on chip after each power-on, and associate and store the abnormal heartbeat data of the abnormal heartbeat status of the system on chip after each power-on with the corresponding current version data.

15. A non-transitory computer-readable storage medium, characterized in that: When the instructions in the storage medium are executed by a processor of an electronic device, the electronic device is enabled to execute a method for recording abnormal heartbeat data as described in any one of claims 1 to 7, or the electronic device is enabled to execute a method for recording abnormal heartbeat data as described in any one of claims 8 to 11.

16. A computer program product, characterized in that The method comprises computer instructions, wherein the computer instructions are executed by a processor to implement a method for recording abnormal heartbeat data as claimed in any one of claims 1 to 7, or the computer instructions are executed by a processor to implement a method for recording abnormal heartbeat data as claimed in any one of claims 8 to 11.

Images