Diagnostic event management method and device, equipment, medium and vehicle

Abstract

The invention relates to a diagnostic event management method, device and equipment, a medium and a vehicle. The method comprises the following steps: when a diagnosis event is reported, collecting and caching a freezing frame of the diagnosis event; collecting extended data of the diagnosis event, and de-jittering the diagnosis event to obtain a de-jittering result; if the de-jitter result represents that the diagnosis event is a fault phenomenon, performing nonvolatile storage on the frozen frame and the extended data as diagnosis data of the diagnosis event; and if the jitter removal result represents that the diagnosis event is a random phenomenon, deleting the frozen frame and the extended data. According to the invention, when the diagnosis event is reported, the frozen frame of the diagnosis event is collected immediately, so that the vehicle system operation state recorded by the frozen frame is extremely small in change relative to the vehicle system operation state when the diagnosis event occurs; therefore, the collected freezing frame more accurately records the running state of the vehicle system when the diagnosis event occurs, and has higher practical value.

Description

Technical Field

[0001] The present disclosure relates to the field of intelligent driving technology, and in particular to a diagnostic event management method, device, equipment, medium and vehicle. Background Art

[0002] At present, the diagnostic event management based on the Automotive Open System Architecture (AUTOSAR) is that the software components (SWC) and basic software modules (BSW) report the diagnostic events through the event reporting interface provided by the diagnostic event management module (DEM). Then, when processing the diagnostic event, the DEM collects the freeze frame (Freeze Frame, which is used to record the status information of the vehicle-related modules when the diagnostic event occurs) and the extended data of the diagnostic event and stores them in the memory. When dumping the data of the diagnostic event, the data of the diagnostic event belonging to the same type will be stored in a storage block (block) of the non-volatile RAM management module (NVM) for non-volatile storage.

[0003] In practical applications, since it takes a certain amount of time for DEM to process a diagnostic event, when a large number of diagnostic events occur in a car in a short period of time, the diagnostic events reported later cannot be processed in time. There is a large time difference between the reporting and the actual processing of these diagnostic events. During this time difference, the status information of the modules related to the occurrence of the diagnostic event may have undergone a large change (such as vehicle speed, power supply voltage, etc.). For example, in the prior art, after the DEM completes the processing of diagnostic event 1, it will collect the freeze frame of diagnostic event 2 when it starts to process diagnostic event 2. Diagnostic event 2 is an event in which the braking system has an abnormality. The freeze frame of diagnostic event 2 includes the speed of the vehicle when the braking system has diagnostic event 2. After the time difference of processing diagnostic event 1, the speed of the vehicle may have changed significantly. At this time, the collected freeze frame of diagnostic event 2 may not reflect the abnormality of the braking system. This will cause the freeze frame data of the diagnostic events collected and stored by DEM when processing these diagnostic events to be inaccurate and have no practical value, and may even affect the judgment of the cause of the diagnostic event. Summary of the invention

[0004] In order to solve the above technical problems, the present disclosure provides a diagnostic event management method, device, equipment, medium and vehicle.

[0005] In a first aspect, the present disclosure provides a diagnostic event management method, the method comprising:

[0006] When a diagnostic event is reported, a freeze frame of the diagnostic event is collected and cached;

[0007] Collecting extended data of the diagnostic event, and de-jittering the diagnostic event to obtain a de-jittering result;

[0008] If the de-jitter result indicates that the diagnostic event is a fault phenomenon, the frozen frame and the extended data are non-volatilely stored as diagnostic data of the diagnostic event;

[0009] If the de-jitter result indicates that the diagnostic event is a random phenomenon, the frozen frame and the extended data are deleted.

[0010] Optionally, the immediately collecting and caching the freeze frames of the diagnostic event includes:

[0011] Recording snapshot information of the current operating state of the vehicle system where the diagnostic event occurs, and using the snapshot information as a freeze frame of the diagnostic event;

[0012] The frozen frames are stored in a frozen frame list in a diagnostic event buffer area, wherein the frozen frame list is a list for storing frozen frames of diagnostic events and their corresponding relationships with diagnostic events.

[0013] Optionally, the collecting the extended data of the diagnostic event and de-jittering the diagnostic event to obtain a de-jitter result includes:

[0014] The extended data of the diagnostic event is collected in a reporting order, and the diagnostic event is de-jittered to obtain a de-jitter result.

[0015] Optionally, collecting the extended data of the diagnostic event in a reporting order, and de-jittering the diagnostic event to obtain a de-jitter result, includes:

[0016] After the diagnostic event is reported, the diagnostic event is queued in a diagnostic event queue, and the diagnostic event queue is a first-in-first-out queue;

[0017] When the diagnostic event is dequeued from the diagnostic event queue, extended data of the diagnostic event is collected, and the diagnostic event is dejittered to obtain a dejitter result.

[0018] Optionally, de-jittering the diagnostic event to obtain a de-jitter result includes:

[0019] Dejittering the diagnostic event according to the dejitter strategy corresponding to the diagnostic event;

[0020] In response to the diagnostic event debounce being completed, determining that the debounce result is that the diagnostic event is a fault phenomenon;

[0021] In response to the diagnostic event debounce not being completed, determining the debounce result as the diagnostic event being a random phenomenon.

[0022] Optionally, the extended data includes at least one of the number of occurrences, the frequency of occurrence, the duration, and the interval between occurrences of the diagnostic event;

[0023] The debounce strategy includes at least one of the following:

[0024] If the number of occurrences of the diagnostic event is greater than or equal to the preset number, the diagnostic event debounce is completed, otherwise the diagnostic event debounce is not completed;

[0025] If the occurrence frequency of the diagnostic event is greater than or equal to the preset frequency, the diagnostic event debounce is completed, otherwise the diagnostic event debounce is not completed;

[0026] If the duration of the diagnostic event is greater than or equal to the first preset time, the diagnostic event debounce is completed, otherwise the diagnostic event debounce is not completed;

[0027] If the interval between the occurrences of the diagnostic event is less than or equal to the second preset time, the diagnostic event de-jittering is completed, otherwise the diagnostic event de-jittering is not completed. Optionally, the non-volatile storage of the frozen frame and the extended data as the diagnostic data of the diagnostic event includes:

[0028] The frozen frame is read from the frozen frame list, and the frozen frame and the extended data are stored in an NVM module.

[0029] Optionally, storing the frozen frame and the extended data in an NVM module includes:

[0030] Allocating a storage block in an NVM module for the diagnostic event, the storage block only storing diagnostic data of the diagnostic event;

[0031] The frozen frame and the extended data are stored in the storage block.

[0032] In a second aspect, the present disclosure provides a diagnostic event management device, applicable to the AUTOSAR architecture, the device comprising:

[0033] A collecting module, configured to immediately collect and cache frozen frames of a diagnostic event in response to the event reporting interface reporting the diagnostic event;

[0034] A processing module, used for collecting extended data of the diagnostic event, and de-jittering the diagnostic event to obtain a de-jittering result;

[0035] A dump module, configured to store the frozen frame and the extended data as diagnostic data of the diagnostic event in a non-volatile manner when the de-jitter result indicates that the diagnostic event is a fault phenomenon;

[0036] The cleaning module is used to delete the frozen frame and the extended data when the de-jitter result indicates that the diagnostic event is a random phenomenon.

[0037] Optionally, when the collection module immediately collects and caches the freeze frames of the diagnostic event, it is specifically used to record snapshot information of the current operating status of the vehicle system where the diagnostic event occurs, and use the snapshot information as the freeze frame of the diagnostic event; the freeze frame is stored in a freeze frame list in the diagnostic event cache area, and the freeze frame list is a list for storing the freeze frames of the diagnostic event and the correspondence between them and the diagnostic events.

[0038] Optionally, when collecting the extended data of the diagnostic event and de-jittering the diagnostic event to obtain a de-jitter result, the processing module is specifically used to collect the extended data of the diagnostic event in a reporting order and de-jittering the diagnostic event to obtain a de-jitter result.

[0039] Optionally, when the processing module collects extended data of the diagnostic event in the reporting order and de-jitters the diagnostic event to obtain a de-jitter result, it is specifically used to, after the diagnostic event is reported, enqueue the diagnostic event into a diagnostic event queue, where the diagnostic event queue is a first-in-first-out queue; and when the diagnostic event is dequeued from the diagnostic event queue, collect the extended data of the diagnostic event and de-jitter the diagnostic event to obtain a de-jitter result.

[0040] Optionally, when the processing module de-jitters the diagnostic event and obtains a de-jitter result, the processing module is specifically used to de-jitter the diagnostic event according to the de-jitter strategy corresponding to the diagnostic event; in response to the de-jittering of the diagnostic event being completed, determining that the de-jitter result is that the diagnostic event is a fault phenomenon; in response to the de-jittering of the diagnostic event being incomplete, determining that the de-jitter result is that the diagnostic event is a random phenomenon.

[0041] Optionally, the extended data includes at least one of the number of occurrences, the frequency of occurrence, the duration, and the interval between occurrences of the diagnostic event;

[0042] The de-jitter strategy includes at least one of the following: if the number of occurrences of the diagnostic event is greater than or equal to the preset number, the diagnostic event de-jitter is completed, otherwise the diagnostic event de-jitter is not completed; if the occurrence frequency of the diagnostic event is greater than or equal to the preset frequency, the diagnostic event de-jitter is completed, otherwise the diagnostic event de-jitter is not completed; if the duration of the diagnostic event is greater than or equal to the first preset time, the diagnostic event de-jitter is completed, otherwise the diagnostic event de-jitter is not completed; if the interval time between the occurrences of the diagnostic event is less than or equal to the second preset time, the diagnostic event de-jitter is completed, otherwise the diagnostic event de-jitter is not completed.

[0043] Optionally, when the dump module performs non-volatile storage on the frozen frame and the extended data as diagnostic data of the diagnostic event, the dump module is specifically configured to read the frozen frame from the frozen frame list and store the frozen frame and the extended data in an NVM module.

[0044] Optionally, when the dump module stores the frozen frame and the extended data in the NVM module, it is specifically used to allocate a storage block in the NVM module for the diagnostic event, and the storage block only stores the diagnostic data of the diagnostic event; and stores the frozen frame and the extended data in the storage block.

[0045] In a third aspect, the present disclosure provides a computer device, comprising:

[0046] Memory;

[0047] Processor; and

[0048] Computer programs;

[0049] The computer program is stored in the memory and is configured to be executed by the processor to implement the method as described in any one of the first aspects.

[0050] In a fourth aspect, the present disclosure provides a computer-readable storage medium having a computer program stored thereon, wherein the computer program, when executed by a processor, implements the method as described in any one of the first aspects.

[0051] In a fifth aspect, the present disclosure provides a vehicle, comprising the diagnostic event management device as described in the second aspect and / or the computer device as described in the third aspect.

[0052] The diagnostic event management method, device, equipment, and medium provided by the present disclosure collect and cache the freeze frames of the diagnostic event immediately when the diagnostic event is reported, and then collect the extended data of the diagnostic event when processing the diagnostic event and de-jitter the diagnostic event to obtain a de-jitter result. If the de-jitter result indicates that the diagnostic event is a fault phenomenon, the freeze frames and extended data of the diagnostic event are non-volatilely stored so that the diagnostic event can be subsequently traced back to the freeze frames and extended data of the diagnostic event; if the de-jitter result indicates that the diagnostic event is a random phenomenon, the freeze frames and extended data of the diagnostic event are deleted. Since the freeze frames of the diagnostic event are collected immediately when the diagnostic event is reported, the time interval between the time of collecting the freeze frames and the occurrence of the diagnostic event is extremely short, and thus the change in the vehicle system operating state recorded by the freeze frames relative to the vehicle system operating state when the diagnostic event occurs is extremely small. Therefore, the collected freeze frames more accurately record the vehicle system operating state when the diagnostic event occurs, and are more practical. BRIEF DESCRIPTION OF THE DRAWINGS

[0053] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and, together with the description, serve to explain the principles of the present disclosure.

[0054] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

[0055] Figure 1 A flow chart of a diagnostic event management method provided by an embodiment of the present disclosure;

[0056] Figure 2 A schematic diagram of an application scenario provided by an embodiment of the present disclosure;

[0057] Figure 3 A schematic diagram of a dump application scenario provided by an embodiment of the present disclosure;

[0058] Figure 4 A schematic diagram of the structure of a diagnostic event management device provided by an embodiment of the present disclosure;

[0059] Figure 5 A schematic diagram of the structure of an electronic device provided in an embodiment of the present disclosure. DETAILED DESCRIPTION

[0060] In order to more clearly understand the above-mentioned objectives, features and advantages of the present disclosure, the scheme of the present disclosure will be further described below. It should be noted that the embodiments of the present disclosure and the features in the embodiments can be combined with each other without conflict.

[0061] In the following description, many specific details are set forth to facilitate a full understanding of the present disclosure, but the present disclosure may also be implemented in other ways different from those described herein; it is obvious that the embodiments in the specification are only part of the embodiments of the present disclosure, rather than all of the embodiments.

[0062] Figure 1 This is a flow chart of a diagnostic event management method provided by an embodiment of the present disclosure. The method can be executed by a diagnostic event management device. The diagnostic event management device can be implemented in software and / or hardware. The diagnostic event management device can be configured in an electronic device, such as a vehicle computer, a vehicle computer, a domain controller, or other device with data processing capabilities. Figure 1 As shown, the method comprises the following steps:

[0063] S101 . In response to an event reporting interface reporting a diagnosis event, immediately collect and cache freeze frames of the diagnosis event.

[0064] For example, Figure 2 Schematic diagram of an application scenario provided by an embodiment of the present disclosure. The application scenario includes an event detection module 210 composed of software components (SWC) and basic software modules (BSW), a DEM module 220 and an NVM module 230.

[0065] exist Figure 2 In the application scenario shown, the software components and basic software modules of the event detection module 210 monitor various systems of the vehicle, and when a diagnostic event is detected in a certain system, the diagnostic event is reported through the event reporting interface of the DEM module 220. For example, when the voltage output of a certain power supply of the vehicle's power supply system increases abnormally, the event detection module 210 detects that the voltage output of the power supply is too high, that is, it detects that the power supply system has a diagnostic event 1 of too high power output voltage; for example, when the vehicle's braking system is abnormal, the event detection module 210 detects that the actual speed of the vehicle has not been reduced to the speed after the braking system is braked, that is, it detects the diagnostic event 2 of inaccurate braking of the braking system.

[0066] When the event detection module 210 reports a diagnostic event from the event reporting interface, the DEM module 220 immediately collects a freeze frame of the diagnostic event. The freeze frame in the embodiment of the present disclosure refers to the operating status information of the vehicle system where the diagnostic event occurs when the diagnostic event occurs. Since the freeze frame of the diagnostic event is collected immediately after the diagnostic event is reported, the time interval between the time of collecting the freeze frame and the occurrence of the diagnostic event is extremely short. Therefore, the operating status of the vehicle system when the freeze frame is collected is less changed than the operating status of the vehicle system when the diagnostic event occurs. The freeze frame collected in the embodiment of the present disclosure is more accurate than the freeze frame collected when processing a diagnostic event in the prior art.

[0067] For example, when the event detection module 210 uploads diagnostic event 1, diagnostic event 2, ..., diagnostic event n, the DEM module 220 starts to process diagnostic event 1 after diagnostic event 1 is uploaded. Because the embodiment of the present disclosure separates the task of collecting freeze frames of diagnostic events from the task of processing diagnostic events, the DEM module 220 will collect freeze frames of diagnostic event 2 when diagnostic event 2 is reported, and collect freeze frames of diagnostic event 3 when diagnostic event 3 is reported, even when processing diagnostic event 1. Because the freeze frames of diagnostic event 2 are collected immediately when diagnostic event 2 is reported, and the time interval from the occurrence of diagnostic event 2 to the reporting is extremely short, the collected freeze frames are closer to the operating state of the brake system when diagnostic event 2 occurs. In this way, the collection time of freeze frames of other diagnostic events will not be delayed due to the time difference in processing diagnostic events, and a large difference between the operating state information recorded in the collected freeze frames of diagnostic events and the operating state information when the diagnostic events occur can be avoided.

[0068] After the DEM module 220 collects the frozen frames of the diagnostic events, it stores the frozen frames in the diagnostic event buffer area, waiting for subsequent processing of the diagnostic events.

[0069] S102: Collect extended data of the diagnostic event, and de-jitter the diagnostic event to obtain a de-jitter result.

[0070] When processing a diagnostic event, the DEM module 220 collects the extended data (DTCExtendedData) of the diagnostic event and debounces the diagnostic event.

[0071] Extended data is dynamic information related to diagnostic events, such as the number of occurrences of diagnostic events and the time of the most recent occurrence of diagnostic events. Debouncing is used to monitor the maturity of faults in order to avoid false alarms of faults. For example, when the event detection module 210 detects the output voltage of the power supply, there may be interference, resulting in a voltage value that is too high at a certain moment. The event detection module 210 reports the diagnostic event 1 of the power supply output voltage being too high, and the output voltage detected by the event detection module 210 afterwards is normal. The interference of such random factors can be avoided by debouncing. For example, the debouncing strategy can be formulated to detect diagnostic event 1 more than 10 times. When the output voltage of the power supply is too high for 10 consecutive times, it can be determined that diagnostic event 1 is indeed a fault, not a random phenomenon.

[0072] Generally speaking, in addition to the two conventional strategies of collecting extended data and debounce mentioned above, targeted processing strategies may be set for different types of diagnostic events, such as common strategies such as function degradation or function prohibition for diagnostic events. These common strategies are usually safety measures for diagnostic events. Taking diagnostic event 1 as an example, diagnostic event 1 is an event in which the output voltage of the power supply is too high. The corresponding processing strategy for diagnostic event 1 usually includes reducing the output of the power supply.

[0073] S103: If the de-jitter result indicates that the diagnosis event is a fault phenomenon, the frozen frame and the extended data are non-volatilely stored as diagnosis data of the diagnosis event.

[0074] When the diagnostic event debounce is completed, the debounce result of the diagnostic event indicates that the diagnostic event is a vehicle fault rather than a random phenomenon. The DEM module 220 stores the freeze frame and extended data of the diagnostic event as the diagnostic data of the diagnostic event in the non-volatile memory. In the AUTOSAR architecture, the freeze frame and extended data of the diagnostic event are dumped into the NVM module.

[0075] S104: If the de-jitter result indicates that the diagnosis event is a random phenomenon, the frozen frame and the extended data are deleted.

[0076] When the de-jittering of the diagnostic event is not completed, the de-jittering result of the diagnostic event indicates that the diagnostic event is a random phenomenon, that is, the fault detected in the diagnostic event is not mature, and the DEM module 220 will directly delete the frozen frame and the extended data.

[0077] The disclosed embodiment collects and caches the freeze frames of the diagnostic event immediately when the diagnostic event is reported on the event reporting interface, then collects the extended data of the diagnostic event when processing the diagnostic event and de-jitters the diagnostic event to obtain a de-jitter result, if the de-jitter result indicates that the diagnostic event is a fault phenomenon, the freeze frames and extended data of the diagnostic event are non-volatilely stored, if the de-jitter result indicates that the diagnostic event is a fault phenomenon, the freeze frames and extended data of the diagnostic event are non-volatilely stored, so that the diagnostic event can be subsequently traced back to the freeze frames and extended data of the diagnostic event; if the de-jitter result indicates that the diagnostic event is a random phenomenon, the freeze frames and extended data of the diagnostic event are deleted. Since the freeze frames of the diagnostic event are collected immediately when the diagnostic event is reported, the time interval between the time of collecting the freeze frames and the occurrence of the diagnostic event is extremely short, and the change of the vehicle system operating state recorded by the freeze frames relative to the vehicle system operating state when the diagnostic event occurs is extremely small, so the collected freeze frames more accurately record the vehicle system operating state when the diagnostic event occurs, and are more practical.

[0078] In a feasible implementation, freeze frames of diagnostic events are immediately collected and cached, including: recording snapshot information of the current operating state of the vehicle system where the diagnostic event occurs, and using the snapshot information as the freeze frames of the diagnostic event; storing the freeze frames in a freeze frame list in a diagnostic event cache area, the freeze frame list being a list for storing freeze frames of diagnostic events and their correspondence with diagnostic events.

[0079] When the diagnostic event is reported, the DEM module 220 will immediately record the current operating status of the vehicle system where the diagnostic event occurs, and generate snapshot information of the operating status, which is the freeze frame of the diagnostic event. For example, when diagnostic event 1 is reported to the event reporting interface, the DEM module 220 will immediately record a snapshot of the operating status information of the vehicle power supply system as the freeze frame of diagnostic event 1, including the output voltage value of each power supply, the voltage value of each power supply circuit, etc.

[0080] After collecting the freeze frames of the diagnostic events, the DEM module 220 stores the freeze frames in a freeze frame list in the diagnostic event buffer area. The freeze frame list is a list of diagnostic event freeze frames collected immediately in the embodiment of the present disclosure. Since the diagnostic events may not be processed immediately, they need to be cached and retrieved when the diagnostic events are processed.

[0081] The freeze frame list will record the correspondence between each stored freeze frame and the reported diagnostic event, so that the freeze frame can be taken out for dumping after the diagnostic event is fully processed. Figure 2As shown, after collecting the freeze frames of diagnostic event 1, the DEM module 220 stores the freeze frames of diagnostic event 1 in the freeze frame list 222, and records the correspondence between the freeze frames of diagnostic event 1 and diagnostic event 1 in the freeze frame list 222; the collected freeze frames of diagnostic event 2 are stored in the freeze frame list 222, and the correspondence between the freeze frames of diagnostic event 2 and diagnostic event 2 is recorded in the freeze frame list 222, and so on, which will not be elaborated here.

[0082] The disclosed embodiment records snapshot information of the current operating state of the vehicle system where the diagnostic event occurs as snapshot information of the current operating state of the vehicle system where the diagnostic event occurs, and then stores the freeze frame in a freeze frame list in a diagnostic event buffer area so that the freeze frame can be dumped after the diagnostic event processing is completed.

[0083] In some embodiments, collecting extended data of diagnostic events and de-jittering the diagnostic events to obtain de-jitter results include: collecting extended data of diagnostic events in a reporting order, and de-jittering the diagnostic events to obtain de-jitter results.

[0084] For example, refer to Figure 2 , since the event detection module 210 reports diagnostic event 1, diagnostic event 2, ..., diagnostic event n in a short period of time, in order to avoid confusion when processing multiple diagnostic events, the DEM module 220 will process these diagnostic events in the order in which the diagnostic events are reported. The first diagnostic event reported is diagnostic event 1, so the DEM module 220 will process diagnostic event 1 first, and after completing the processing of diagnostic event 1, it will process diagnostic event 2 reported after diagnostic event 1, and so on, processing the reported diagnostic events in sequence.

[0085] In a feasible implementation, extended data of the diagnostic event is collected in the order of reporting, and the diagnostic event is de-jittered to obtain a de-jitter result, including: after the diagnostic event is reported, the diagnostic event is queued into a diagnostic event queue, and the diagnostic event queue is a first-in-first-out queue; when the diagnostic event is de-queued from the diagnostic event queue, the extended data of the diagnostic event is collected, and the diagnostic event is de-jittered to obtain a de-jitter result.

[0086] The DEM module 220 processes diagnostic events in the order of reporting by performing queue entry and dequeue operations on diagnostic events when processing diagnostic events. First, when a diagnostic event is reported to the event reporting interface, the diagnostic event is put into the tail of the diagnostic event queue. The diagnostic event queue is a first-in-first-out storage structure, where the end where data is entered is called the tail, and the end where data is taken out is called the head.

[0087] by Figure 2Taking the scenario shown as an example, after diagnostic event 1 is reported to the event reporting interface, the DEM module 220 performs a queue operation on diagnostic event 1, and puts diagnostic event 1 into the diagnostic event queue 221 from the end of the queue. Since diagnostic event 1 is the first diagnostic event currently entering the diagnostic event queue 221, diagnostic event 1 is at the head of the diagnostic event queue 221, and then diagnostic event 2 is queued into the diagnostic event queue 221 from the end of the queue, and so on. At the same time, the DEM module 220 processes the diagnostic event that is dequeued from the head of the diagnostic event queue 221. After the DEM module 220 takes out diagnostic event 1 from the head of the diagnostic event queue 221 for processing, diagnostic event 2 is at the head of the diagnostic event queue 221. When the processing of diagnostic event 1 is completed, the DEM module 220 takes out the diagnostic event from the head of the diagnostic event queue 221 again for processing, that is, diagnostic event 2 is dequeued from the head of the diagnostic event queue 221, and at this time, diagnostic event 3 is at the head of the diagnostic event queue 221. In this way, the extended data of the diagnostic event is collected and the diagnostic event is de-jittered according to the reporting order of the diagnostic event, and the de-jitter results of the diagnostic event are obtained in sequence.

[0088] The disclosed embodiment performs queueing and dequeueing operations on diagnostic events reported to the event reporting interface. Since the queue is a first-in-first-out storage structure, it can achieve the effect of processing diagnostic events in the order of reporting and avoid confusion when processing multiple diagnostic events.

[0089] In some embodiments, dejittering a diagnostic event to obtain a dejitter result includes: dejittering the diagnostic event according to a dejitter strategy corresponding to the diagnostic event; in response to completion of dejittering of the diagnostic event, determining that the dejitter result is that the diagnostic event is a fault phenomenon; in response to incomplete dejittering of the diagnostic event, determining that the dejitter result is that the diagnostic event is a random phenomenon.

[0090] The DEM module 220 will also debounce the diagnostic event. Each diagnostic event has a corresponding debounce strategy, which is usually formulated by the manufacturer. For example, the diagnostic event of relay open circuit usually detects whether the number of times the relay is open circuit exceeds the preset number of times. For example, the diagnostic event of relay open circuit is detected once every 100ms. If the continuous detection is 10 times (1000ms) and it is open circuit, it means that the relay is indeed open circuit, and the diagnostic event of relay open circuit is debounced. For another example, the diagnostic event of motor overheating continuously monitors the temperature of the motor. If the duration of the motor temperature being too high exceeds the preset time, it means that the motor is indeed faulty, and the diagnostic event of motor overheating is debounced. If the motor temperature is only too high for a short time, that is, the duration of the motor temperature being too high does not exceed the preset time, it means that the motor overheating is just a random phenomenon that occurs occasionally, so the diagnostic event of motor overheating is not debounced. If the diagnostic event debounce is completed, the diagnostic event can be determined as a vehicle fault phenomenon. If the diagnostic event debounce is not completed, the diagnostic event can be determined as a random phenomenon that occurs occasionally in the vehicle.

[0091] In some embodiments, the extended data includes at least one of the number of occurrences, the frequency of occurrences, the duration, and the interval between occurrences of the diagnostic event.

[0092] The extended data is usually dynamic information related to the diagnostic event, such as the number of occurrences of the diagnostic event and the time of the most recent occurrence of the diagnostic event. Exemplarily, the extended data in the embodiment of the present disclosure includes at least one of the following: the number of occurrences of the diagnostic event, the frequency of occurrence of the diagnostic event, the duration of the diagnostic event, and the interval between the occurrences of the diagnostic event. The DEM module 220 will obtain the extended data of the diagnostic event when processing the diagnostic event. The extended data can be recorded by the DEM module itself, or recorded by the SWC and BSW that constitute the event detection module 210.

[0093] The de-jitter strategy in the disclosed embodiment includes at least one of the following: If the number of occurrences of the diagnostic event is greater than or equal to the preset number of times, the de-jitter of the diagnostic event is completed, otherwise the de-jitter of the diagnostic event is not completed. If the frequency of occurrence of the diagnostic event is greater than or equal to the preset frequency, the de-jitter of the diagnostic event is completed, otherwise the de-jitter of the diagnostic event is not completed. If the duration of the diagnostic event is greater than or equal to the first preset time, the de-jitter of the diagnostic event is completed, otherwise the de-jitter of the diagnostic event is not completed. If the interval time between the occurrences of the diagnostic event is less than or equal to the second preset time, the de-jitter of the diagnostic event is completed, otherwise the de-jitter of the diagnostic event is not completed.

[0094] The de-bouncing strategy for diagnostic events can be set according to the characteristics of the diagnostic events. For example, for diagnostic event 1 where the power supply output voltage is too high, because the power supply output voltage is too high and has a significant impact on the occurrence of vehicle accidents, a safer condition can be set for the de-bouncing strategy for diagnostic event 1, such as when the de-bouncing strategy for diagnostic event 1 includes the number of occurrences greater than 3 times, then de-bouncing is completed; the frequency of occurrence within a month is greater than once a day, then de-bouncing is completed; the duration is greater than 1 minute, then de-bouncing is completed; and the interval between two consecutive events is less than 1 hour, then de-bouncing is completed. When the extended data of diagnostic event 1 indicates that it meets the conditions of any of the above four de-bouncing strategies, it is determined that the de-bouncing of diagnostic event 1 is completed.

[0095] The disclosed embodiment obtains extended data of a diagnostic event and de-jitters the diagnostic event according to a corresponding de-jitter strategy. If the de-jitter is completed, the diagnostic event is determined to be a fault phenomenon; if the de-jitter is not completed, the diagnostic event is determined to be a random phenomenon, so that the diagnostic data of the diagnostic event determined to be a fault phenomenon can be subsequently stored in a non-volatile manner.

[0096] In a feasible implementation manner, the frozen frame and the extended data are non-volatilely stored as diagnostic data of the diagnostic event, including: reading the frozen frame from the frozen frame list, and storing the frozen frame and the extended data in an NVM module.

[0097] In the AUTOSAR architecture, after completing the processing of the diagnostic event, the DEM module 220 searches for and reads the freeze frame corresponding to the diagnostic event according to the correspondence between the freeze frame and the diagnostic event stored in the freeze frame list, and then stores the freeze frame and the extended data of the diagnostic event in the NVM module as the diagnostic data of the diagnostic event.

[0098] In some embodiments, storing the frozen frame and the extended data in the NVM module includes: allocating a storage block in the NVM module for the diagnostic event, the storage block only storing diagnostic data of the diagnostic event; and storing the frozen frame and the extended data in the storage block.

[0099] The dump scheme design of AUTOSAR in the prior art is to store data belonging to the same type of diagnostic events in a storage block of NVM for non-volatile storage. Under this scheme, if the total number of diagnostic events supported by the new upgrade software increases, the total memory area of ​​the corresponding DEM module will become larger. At this time, increasing the size of the storage block storing the same type of diagnostic events and then writing all diagnostic events of this type will cause the data in other storage blocks to be polluted, that is, data out of bounds occurs. Figure 3 A schematic diagram of a dump application scenario provided by an embodiment of the present disclosure, such as Figure 3 As shown, before the software upgrade, the memory area 310 of the DEM module is used to store diagnostic event 1, diagnostic event 2, ..., diagnostic event n, and the DEM module writes diagnostic event 1, diagnostic event 2, ..., diagnostic event n into the storage block 1 of the storage area 320 in the NVM module. After the software upgrade, a new diagnostic event n+1 is added to the DEM module, and the memory area is increased to the memory area 330. At this time, the storage block 1 in the NVM module needs to be increased, so that the storage area in the NVM module becomes the storage area 340. It can be seen that the storage block 1 and the storage block 2 in the storage area 340 have a boundary area, which will cause the diagnostic event data stored in the storage block 1 to cross the boundary with the data stored in the storage block 2. If the total number of diagnostic events supported after the software upgrade is reduced, the total memory area of ​​the DEM module will become smaller. At this time, when the data of the diagnostic event is written back from the NVM module storage area to the memory area of ​​the DEM module, some data will be lost.

[0100] The embodiment of the present disclosure allocates a storage block in the NVM module to each diagnostic event, that is, each diagnostic event corresponds to a storage block in the NVM module, such as Figure 2As shown, a storage block 1 in the NVM module 230 is allocated to diagnostic event 1, and the frozen frame and extended data of diagnostic event 1 are stored in storage block 1. A storage block 2 in the NVM module 230 is allocated to diagnostic event 2, and the frozen frame and extended data of diagnostic event 2 are stored in storage block 1. Similarly, a storage block n in the NVM module 230 is allocated to diagnostic event n, and the frozen frame and extended data of diagnostic event n are stored in storage block n. In this way, if a new diagnostic event is added after the software is updated, the newly added storage block can be synchronized in the NVM module 230. If a diagnostic event is abandoned after the software is updated, it will not affect other event data, thereby avoiding data out-of-bounds or data loss problems.

[0101] The disclosed embodiment allocates a storage block in an NVM module to a diagnostic event, and the storage block is only used to store diagnostic data of the diagnostic event, and then stores the freeze frame and extended data of the diagnostic event in the storage block to avoid data out-of-bounds or data loss problems when diagnostic events are added or abandoned after software updates.

[0102] Figure 4 The structure diagram of the diagnostic event management device provided in the embodiment of the present disclosure. The diagnostic event management device may be a terminal as in the above embodiment, or the diagnostic event management device may be a component or assembly in the terminal. The diagnostic event management device provided in the embodiment of the present disclosure may execute the processing flow provided in the diagnostic event management method embodiment, such as Figure 3 As shown, the diagnostic event management device 400 includes: a collection module 401, which is used to collect and cache freeze frames of diagnostic events when diagnostic events are reported; a processing module 402, which is used to collect extended data of diagnostic events and de-jitter the diagnostic events to obtain de-jitter results; a dump module 403, which is used to store the freeze frames and extended data as diagnostic data of the diagnostic events in a non-volatile manner when the de-jitter result indicates that the diagnostic event is a fault phenomenon; and a cleanup module 404, which is used to delete the freeze frames and extended data when the de-jitter result indicates that the diagnostic event is a random phenomenon.

[0103] In some embodiments, when collecting and caching freeze frames of diagnostic events, the collection module 401 is specifically used to record snapshot information of the current operating status of the vehicle system where the diagnostic event occurs, and use the snapshot information as the freeze frame of the diagnostic event; the freeze frame is stored in a freeze frame list in the diagnostic event cache area, and the freeze frame list is a list for storing the freeze frames of the diagnostic event and the correspondence between them and the diagnostic events.

[0104] In some embodiments, when collecting extended data of diagnostic events and de-jittering diagnostic events to obtain de-jittering results, processing module 402 is specifically used to collect extended data of diagnostic events in a reporting order and de-jittering diagnostic events to obtain de-jittering results.

[0105] In some embodiments, when the processing module 402 collects extended data of the diagnostic event in the order of reporting and de-jitters the diagnostic event to obtain a de-jitter result, it is specifically used to, after the diagnostic event is reported, enqueue the diagnostic event into a diagnostic event queue, where the diagnostic event queue is a first-in-first-out queue; when the diagnostic event is dequeued from the diagnostic event queue, collect the extended data of the diagnostic event and de-jitter the diagnostic event to obtain a de-jitter result.

[0106] In some embodiments, when the processing module 402 de-jitters the diagnostic event and obtains a de-jitter result, it is specifically used to de-jitter the diagnostic event according to the de-jitter strategy corresponding to the diagnostic event; in response to the diagnostic event de-jitter being completed, determining the de-jitter result is that the diagnostic event is a fault phenomenon; in response to the diagnostic event de-jitter being incomplete, determining the de-jitter result is that the diagnostic event is a random phenomenon.

[0107] In some embodiments, the extended data includes at least one of the number of occurrences, the frequency of occurrences, the duration, and the interval between occurrences of the diagnostic event;

[0108] The de-jitter strategy includes at least one of the following: if the number of occurrences of the diagnostic event is greater than or equal to the preset number, the de-jitter of the diagnostic event is completed, otherwise the de-jitter of the diagnostic event is not completed; if the occurrence frequency of the diagnostic event is greater than or equal to the preset frequency, the de-jitter of the diagnostic event is completed, otherwise the de-jitter of the diagnostic event is not completed; if the duration of the diagnostic event is greater than or equal to the first preset time, the de-jitter of the diagnostic event is completed, otherwise the de-jitter of the diagnostic event is not completed; if the interval time between the occurrences of the diagnostic event is less than or equal to the second preset time, the de-jitter of the diagnostic event is completed, otherwise the de-jitter of the diagnostic event is not completed.

[0109] In some embodiments, when the dump module 403 stores the frozen frame and the extended data as the diagnostic data of the diagnostic event in a non-volatile manner, it is specifically configured to read the frozen frame from the frozen frame list and store the frozen frame and the extended data in the NVM module.

[0110] In some embodiments, when dump module 403 stores freeze frame and extended data in NVM module, it is specifically used to allocate a storage block in NVM module for diagnostic event, and the storage block only stores diagnostic data of diagnostic event; and stores freeze frame and extended data in the storage block.

[0111] Figure 4 The diagnostic event management device of the illustrated embodiment can be used to execute the technical solution of the above-mentioned method embodiment. Its implementation principle and technical effect are similar and will not be repeated here.

[0112] Figure 5Schematic diagram of the structure of an electronic device provided in an embodiment of the present disclosure. The electronic device may be a server as described in the above embodiment. The electronic device provided in an embodiment of the present disclosure may execute the processing flow provided in an embodiment of the diagnostic event management method, such as Figure 5 As shown, the electronic device 500 includes: a memory 501, a processor 502, a computer program and a communication interface 503; wherein the computer program is stored in the memory 501 and is configured to be executed by the processor 502 to perform the diagnostic event management method as described above. In a specific embodiment, the memory 501 can be a non-volatile solid-state memory. In a specific embodiment, the memory 501 includes a read-only memory ROM (Read-Only Memory). In appropriate cases, the ROM can be a mask-programmed ROM, a programmable ROM (Programmable ROM, PROM), an erasable PROM (Electrical Programmable ROM, EPROM), an electrically erasable PROM (Electrically Erasable Programmable ROM, EEPROM), an electrically alterable ROM (Electrically Alterable ROM, EAROM) or a flash memory, or a combination of two or more of these.

[0113] In addition, the embodiment of the present disclosure further provides a computer-readable storage medium on which a computer program is stored, and the computer program is executed by a processor to implement the diagnostic event management method described in the above embodiment. The storage medium can be a non-volatile / non-temporary computer-readable storage medium, for example, the non-volatile / non-temporary computer-readable storage medium can be a ROM, a random access memory (Random Access Memory, RAM), a compact disc read-only memory (Compact Disc ROM, CD-ROM), a magnetic tape, a floppy disk, and an optical data storage device, etc.

[0114] The present disclosure also provides a vehicle, including: Figure 4 The diagnostic event management device shown and / or Figure 5 Computer equipment shown.

[0115] It should be noted that, in this article, relational terms such as "first" and "second" are only 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 term "comprises" or any other variant thereof is 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. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the existence of other identical elements in the process, method, article or device including the elements.

Claims

1. A diagnostic event management method, characterized in that: The method comprises: When a diagnostic event is reported, a freeze frame of the diagnostic event is collected and cached; Collecting extended data of the diagnostic event, and de-jittering the diagnostic event to obtain a de-jittering result; If the de-jitter result indicates that the diagnostic event is a fault phenomenon, the frozen frame and the extended data are non-volatilely stored as diagnostic data of the diagnostic event; If the de-jitter result indicates that the diagnostic event is a random phenomenon, the frozen frame and the extended data are deleted.

2. The method according to claim 1, characterized in that The collecting and caching the freeze frames of the diagnostic events includes: Recording snapshot information of the current operating state of the vehicle system where the diagnostic event occurs, and using the snapshot information as a freeze frame of the diagnostic event; The frozen frames are stored in a frozen frame list in a diagnostic event buffer area, where the frozen frame list is used to store the frozen frames of the diagnostic event and the corresponding relationship between the frozen frames and the diagnostic event.

3. The method according to claim 1, characterized in that The collecting of the extended data of the diagnostic event and de-jittering the diagnostic event to obtain a de-jittering result includes: The extended data of the diagnostic event is collected in a reporting order, and the diagnostic event is de-jittered to obtain a de-jitter result.

4. The method according to claim 3, characterized in that The collecting the extended data of the diagnostic event in a reporting order, and de-jittering the diagnostic event to obtain a de-jittering result, includes: After the diagnostic event is reported, the diagnostic event is queued in a diagnostic event queue, and the diagnostic event queue is a first-in-first-out queue; When the diagnostic event is dequeued from the diagnostic event queue, extended data of the diagnostic event is collected, and the diagnostic event is dejittered to obtain a dejitter result.

5. The method according to claim 1, characterized in that De-jittering the diagnostic event to obtain a de-jitter result includes: Dejittering the diagnostic event according to the dejitter strategy corresponding to the diagnostic event; In response to the diagnostic event debounce being completed, determining that the debounce result is that the diagnostic event is a fault phenomenon; In response to the diagnostic event debounce not being completed, determining the debounce result as the diagnostic event being a random phenomenon.

6. The method according to claim 5, characterized in that The extended data includes at least one of the number of occurrences, the frequency of occurrence, the duration, and the interval between occurrences of the diagnostic event; The debounce strategy includes at least one of the following: If the number of occurrences of the diagnostic event is greater than or equal to the preset number, the diagnostic event debounce is completed, otherwise the diagnostic event debounce is not completed; If the occurrence frequency of the diagnostic event is greater than or equal to the preset frequency, the diagnostic event debounce is completed, otherwise the diagnostic event debounce is not completed; If the duration of the diagnostic event is greater than or equal to the first preset time, the diagnostic event debounce is completed, otherwise the diagnostic event debounce is not completed; If the interval time between the occurrences of the diagnostic events is less than or equal to the second preset time, the diagnostic event de-jittering is completed; otherwise, the diagnostic event de-jittering is not completed.

7. The method according to claim 2, characterized in that The storing the frozen frame and the extended data as diagnostic data of the diagnostic event in a non-volatile manner includes: The frozen frame is read from the frozen frame list, and the frozen frame and the extended data are stored in an NVM module.

8. The method according to claim 7, characterized in that The storing the frozen frame and the extended data into the NVM module comprises: Allocating a storage block in the NVM module for the diagnostic event, the storage block only storing diagnostic data of the diagnostic event; The frozen frame and the extended data are stored in the storage block.

9. A diagnostic event management device, characterized in that: The device comprises: A collecting module, configured to immediately collect and cache frozen frames of a diagnostic event in response to the event reporting interface reporting the diagnostic event; A processing module, used for collecting extended data of the diagnostic event, and de-jittering the diagnostic event to obtain a de-jittering result; A dump module, configured to store the frozen frame and the extended data as diagnostic data of the diagnostic event in a non-volatile manner when the de-jitter result indicates that the diagnostic event is a fault phenomenon; The cleaning module is used to delete the frozen frame and the extended data when the de-jitter result indicates that the diagnostic event is a random phenomenon.

10. A computer device comprising: Memory; processor; as well as Computer programs; The computer program is stored in the memory and is configured to be executed by the processor to implement the method according to any one of claims 1 to 8.

11. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the method according to any one of claims 1 to 8 is implemented.

12. A vehicle, characterized in that: It comprises the diagnostic event management device as claimed in claim 9 and / or the computer device as claimed in claim 10.

Images