Configuration extensible automatic driving system fault detection method and system

By adopting heartbeat mechanism and fault level management in the autonomous driving system, the problem of inconsistent fault detection rules and high update and iteration costs of autonomous driving system is solved, efficient and accurate fault detection and disposal is achieved, and complex unmanned operations are adapted to environment.

CN119087965AActive Publication Date: 2024-12-06CHINA FAW CO LTD +1

Patent Information

Application Number
CN202411184800.3
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-08-27
Publication Date
2024-12-06
Estimated Expiration
2044-08-27

AI Technical Summary

Technical Problem

The fault detection methods of existing autonomous driving systems have inconsistent fault detection rules, high update and iteration costs, and relatively single fault handling actions, which cannot effectively deal with complex unmanned operation testing environments.

Method used

The heartbeat mechanism is used to establish a unified node heartbeat mechanism, collect the heartbeat information of each module in real time, including the timestamp of the fault event, component name and fault code, transmit it through the publishing and subscription mode, and store the heartbeat information based on the cache mechanism and real-time drop function. Set and execute fault detection policies, configure and manage fault levels, and implement configurable management of fault levels.

Benefits of technology

It reduces the delay time of fault detection, improves the real-time and accuracy of fault detection, enhances the update and iteration efficiency of fault detection functions, and improves the precision of fault handling.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119087965A_ABST
    Figure CN119087965A_ABST
Patent Text Reader

Abstract

The invention relates to the technical field of vehicles, and discloses a configurable expandable automatic driving system fault detection method and system, electronic equipment, a storage medium and a vehicle, and the method comprises the steps: building a unified node heartbeat mechanism, and collecting the heartbeat information of each module of an automatic driving system in real time; in response to the collected heartbeat information, storing and managing the heartbeat information so as to enable a fault detection strategy to perform data query; setting and executing the fault detection strategy, performing periodic traversal on the stored heartbeat information to complete fault detection, and endowing the detected fault with a specified fault level based on a fault event; and configuring and managing the fault level, performing version management on the fault level, and guiding fault handling based on configuration data of the fault level. According to the invention, the delay time of fault detection can be reduced, and the real-time performance of fault detection is improved; and configurable management of fault levels is realized.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the field of vehicle technology, and in particular to a configurable and expandable automatic driving system fault detection method, system, electronic device, storage medium and vehicle. Background Art

[0002] At present, with the rapid development and application of autonomous driving technology, autonomous driving technology has brought great experience improvement to people. At the same time, the reliability and safety of the autonomous driving system itself are also receiving more and more attention. To ensure the reliability and safety of the autonomous driving system, on the one hand, it is necessary to make safety-related considerations in the design of the autonomous driving system and platform, and on the other hand, it is also necessary to perform real-time fault detection and fault handling of the autonomous driving system. As we all know, the autonomous driving system is a complex system that includes multiple functions such as perception, positioning, planning and control. In unmanned scenarios, how to detect system failures in the system in real time and accurately, and take safety handling actions in a timely manner, is a common problem that the autonomous driving industry needs to solve.

[0003] The fault detection scheme currently commonly adopted in the industry is to collect the process status information of each module, combine it with the internal status information sent by the module, make a simple fault judgment on the status information, and then perform a simple maximum value operation of the fault level to determine the status of each module. On this basis, the state of the system is judged according to the importance of the module itself, and finally it is deduced that the system is in a safe or unsafe state. If it is in a safe state, automatic driving will continue; if it is in an unsafe state, take over. Although this fault detection scheme can complete basic fault detection, fault reminder and fault handling functions, it also has problems such as inconsistent fault detection rules, high update and iteration costs, and relatively single supported fault handling actions. It cannot efficiently cope with complex operation test environments in unmanned scenarios.

[0004] Therefore, the present application provides a configurable and scalable autonomous driving system fault detection method to solve the above-mentioned technical problems. Summary of the invention

[0005] The purpose of the present invention is to provide a configurable and expandable autonomous driving system fault detection method, system, electronic device, storage medium and vehicle to solve the technical problems in the prior art such as inconsistent fault detection rules, high update and iteration costs, relatively simple fault handling actions, and the inability to efficiently cope with complex operating test environments in unmanned scenarios.

[0006] In order to solve the above technical problems, the present invention provides a configurable and scalable automatic driving system fault detection method, comprising:

[0007] The step of establishing a heartbeat mechanism includes establishing a unified node heartbeat mechanism to collect heartbeat information of each module of the autonomous driving system in real time, wherein the heartbeat information includes a timestamp, component name and fault code of an internal fault event of each module;

[0008] A heartbeat information management step, comprising storing and managing the heartbeat information in response to the collected heartbeat information, so that the fault detection strategy can perform data query;

[0009] Executing a fault detection step, including setting and executing the fault detection strategy, periodically traversing the stored heartbeat information, completing fault detection, and assigning a specified fault level to the detected fault based on the fault event;

[0010] The fault level management step includes configuring and managing the fault level, performing version management on the fault level, and guiding fault handling based on configuration data of the fault level.

[0011] In some specific embodiments, the heartbeat mechanism establishment step includes establishing a unified node heartbeat mechanism to collect heartbeat information of each module of the autonomous driving system in real time, wherein the heartbeat information includes the timestamp, component name and fault code of the internal fault event of each module, and further includes:

[0012] Setting a unified heartbeat cycle, and configuring each module to send the heartbeat information according to the heartbeat cycle;

[0013] In the heartbeat information, when the fault event exists inside the module, a complete heartbeat packet including information related to the fault event is sent;

[0014] When the fault event does not exist inside the module, an empty heartbeat packet is sent;

[0015] The heartbeat information is transmitted via a publish-subscribe communication mode.

[0016] In some specific embodiments, the heartbeat information management step includes storing and managing the heartbeat information in response to the collected heartbeat information so that the fault detection strategy performs data query, further comprising:

[0017] Based on a cache mechanism, storing the heartbeat information within a recent period of time, wherein the cache mechanism includes a lock-free ring queue;

[0018] Establish a real-time disk storage function for the heartbeat information to ensure the security and traceability of the heartbeat information;

[0019] Provide a data query interface for the fault detection strategy within the module in the module and time dimensions.

[0020] In some specific embodiments, performing the fault detection step includes setting and executing the fault detection strategy, periodically traversing the stored heartbeat information, completing fault detection, and assigning a specified fault level to the detected fault based on the fault event, further including:

[0021] Based on the characteristics and requirements of the autonomous driving system, the fault detection strategy is configured accordingly, wherein the fault detection strategy includes a heartbeat timeout strategy and a heartbeat information content verification strategy;

[0022] Performing a periodic traversal on all the fault detection strategies, and determining the status of the module according to the strategy logic of the fault detection strategy;

[0023] Based on the determined module status, the fault detection is completed, the detected fault is evaluated for fault level according to preset rules, and the evaluation result is stored in the fault event cache of EventBus.

[0024] In some specific embodiments, the fault level management step includes configuring and managing the fault level, performing version management on the fault level, and guiding fault handling based on the configuration data of the fault level, further including:

[0025] Performing version management on the fault levels, including displaying all current versions of fault levels and newly added fault level versions;

[0026] Calculate the md5 value of the fault level configuration file, and maintain the relationship between the version and the md5 value through the cloud service;

[0027] The configuration file uses a triplet method to represent faults, and rates faults from three dimensions: system impact, operational impact, and parking urgency.

[0028] In some specific embodiments, the method further comprises:

[0029] When fault detection is started, the fault level configuration data is read into the node cache and managed in the form of a hash table to facilitate fault level lookup and assignment, thereby guiding the fault handling of the autonomous driving system.

[0030] Based on the same concept, the present invention also provides a configurable and scalable automatic driving system fault detection system, comprising:

[0031] A heartbeat mechanism establishment module, configured to establish a unified node heartbeat mechanism, and collect heartbeat information of each module of the autonomous driving system in real time, wherein the heartbeat information includes a timestamp, a component name, and a fault code of an internal fault event of each module;

[0032] A heartbeat information management module, configured to store and manage the heartbeat information in response to the collected heartbeat information, so that the fault detection strategy can perform data query;

[0033] An execution fault detection module is configured to set and execute the fault detection strategy, periodically traverse the stored heartbeat information, complete fault detection, and assign a specified fault level to the detected fault based on the fault event;

[0034] The fault level management module is configured to configure and manage the fault level, perform version management on the fault level, and guide fault handling based on configuration data of the fault level.

[0035] Based on the same concept, the present invention also provides an electronic device, including: a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory communicate with each other through the communication bus; a computer program is stored in the memory, and when the computer program is executed by the processor, the processor executes the steps of a configurable and expandable autonomous driving system fault detection method.

[0036] Based on the same concept, the present invention also provides a computer-readable storage medium, which stores a computer program that can be executed by an electronic device. When the computer program runs on the electronic device, the electronic device executes the steps of a configurable and expandable autonomous driving system fault detection method.

[0037] Based on the same concept, the present invention also provides a vehicle, which is provided with the configurable and scalable automatic driving system fault detection system as described above.

[0038] Compared with the prior art, the invention has the following beneficial effects:

[0039] The present invention discloses a configurable and expandable automatic driving system fault detection method, system, electronic device, storage medium and vehicle, which can reduce the delay time of fault detection and improve the real-time performance of fault detection; realize configurable management of fault levels and improve the update and iteration efficiency of fault detection functions; improve the precision and accuracy of fault detection and facilitate further guidance on the implementation of fault handling actions. BRIEF DESCRIPTION OF THE DRAWINGS

[0040] Figure 1 It is a flowchart of a configurable and scalable automatic driving system fault detection method in some specific embodiments of the present invention;

[0041] Figure 2 It is a schematic diagram of the architecture of a configurable and scalable automatic driving system fault detection method in some applications of the present invention;

[0042] Figure 3 It is a schematic diagram of the vehicle-cloud interaction process of a configurable and scalable automatic driving system fault detection method in some applications of the present invention;

[0043] Figure 4 It is a logic block diagram of a configurable and scalable automatic driving system fault detection method in some applications of the present invention;

[0044] Figure 5 It is a structural schematic diagram of a configurable and scalable automatic driving system fault detection system in some specific embodiments of the present invention;

[0045] Figure 6 It is a schematic diagram of the structure of an electronic device in some specific embodiments of the present invention. DETAILED DESCRIPTION

[0046] In order to make the purpose, technical solutions and advantages of the present application clearer, the present application will be further described in detail below in conjunction with the accompanying drawings. Obviously, the described embodiments are only part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present application.

[0047] The terms used in the embodiments of the present application are only for the purpose of describing specific embodiments, and are not intended to limit the present application. The singular forms "a", "said" and "the" used in the embodiments of the present application and the appended claims are also intended to include plural forms, and unless the context clearly indicates other meanings, "multiple" generally includes at least two.

[0048] It should be understood that the term "and / or" used 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 at the same time, and B exists alone. In addition, the character " / " in this article generally indicates that the associated objects before and after are in an "or" relationship.

[0049] It should be understood that although the terms first, second, third, etc. may be used to describe in the embodiments of the present application, these descriptions should not be limited to these terms. These terms are only used to distinguish the descriptions. For example, without departing from the scope of the embodiments of the present application, the first may also be referred to as the second, and similarly, the second may also be referred to as the first.

[0050] As used herein, the words "if" and "if" may be interpreted as "at the time of" or "when" or "in response to determining" or "in response to detecting", depending on the context. Similarly, the phrases "if it is determined" or "if (stated condition or event) is detected" may be interpreted as "when it is determined" or "in response to determining" or "when detecting (stated condition or event)" or "in response to detecting (stated condition or event)", depending on the context.

[0051] It should also be noted that the term "includes", "comprising" or any other variation thereof is intended to cover non-exclusive inclusion, so that a commodity 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 commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprising a ..." do not exclude the existence of other identical elements in the commodity or device including the elements.

[0052] It should be particularly noted that any symbols and / or numbers in the specification that are not marked in the accompanying drawings are not drawing marks.

[0053] Reference Figure 1 , a configurable and scalable automatic driving system fault detection method, comprising:

[0054] S101, a heartbeat mechanism establishment step, including establishing a unified node heartbeat mechanism to collect heartbeat information of each module of the autonomous driving system in real time, wherein the heartbeat information includes a timestamp, component name, and fault code of an internal fault event of each module;

[0055] It is understandable that the heartbeat information contains the following three core fields:

[0056] Timestamp: records the exact time when the module's internal fault event occurs, in the format of year, month, day, hour, minute, second, and millisecond, ensuring the time accuracy to the millisecond level.

[0057] Component name: identifies the specific component or module name where the fault occurred, in string format, such as "radar sensor", "navigation calculation unit", etc., to help quickly locate the source of the problem.

[0058] Fault code: According to the preset fault coding system, a unique identifier is assigned to each possible fault, expressed in hexadecimal or decimal numbers, such as "0x0001" means "sensor data abnormality".

[0059] A heartbeat information collection module is embedded in each key module of the autonomous driving system. This module is responsible for monitoring the module's operating status in real time, and once an internal fault event (such as sensor data anomaly, computing unit overload, etc.) is detected, it immediately generates heartbeat information according to the above specifications.

[0060] For example, in the "Radar Sensor" module, if data transmission interruption is detected, the heartbeat information acquisition module captures the current timestamp (such as "2023-04-01 14:30:05.234"), determines that the component name is "Radar Sensor", and queries the corresponding fault code "0x0002" (assuming it is "data transmission failure"), and then encapsulates this information into a heartbeat information package.

[0061] The heartbeat information of each module is transmitted to the central monitoring unit in real time using an internal communication protocol (such as CAN bus, Ethernet, etc.). The central monitoring unit is designed with a heartbeat information receiving module, which is responsible for receiving and parsing the heartbeat information from each module.

[0062] In some of the applications, the steps for establishing the heartbeat mechanism include establishing a unified node heartbeat mechanism, collecting heartbeat information of each module of the autonomous driving system in real time, the heartbeat information includes the timestamp, component name and fault code of the internal fault event of each module, setting a unified heartbeat period, and configuring each module to send heartbeat information according to the heartbeat period; in the heartbeat information, when there is a fault event inside the module, a complete heartbeat packet including information related to the fault event is sent; when there is no fault event inside the module, an empty heartbeat packet is sent; the heartbeat information is transmitted through a publish-subscribe communication mode.

[0063] It is understandable that a uniform heartbeat period is set according to the operating characteristics and monitoring requirements of the autonomous driving system, for example, the heartbeat period is set to 5 seconds.

[0064] In each system module, the heartbeat sending logic is configured so that it can send heartbeat information according to the set heartbeat period. The content of the heartbeat information varies depending on whether there is a fault event inside the module.

[0065] When a fault occurs inside the module:

[0066] Heartbeat packet content: includes heartbeat header information (such as timestamp, module ID, etc.) and fault event related information (such as fault timestamp, component name, fault code, fault description, etc.).

[0067] Sending logic: When a fault event is detected inside the module, a complete heartbeat packet is generated based on the fault information and sent when the next heartbeat cycle arrives.

[0068] For example, if the camera module detects an image transmission interruption fault at a certain moment, the generated heartbeat packet contains the following information:

[0069] Timestamp: 2023-05-10 12:00:00.000;

[0070] Module ID: Camera_01;

[0071] Failure timestamp: 2023-05-10 12:00:00.000;

[0072] Component name: Image Transmi ss i on Un it;

[0073] Fault code: 0x0010;

[0074] Fault description: Image Transmission Interrupted;

[0075] When there is no fault event inside the module:

[0076] Heartbeat packet content: only contains the heartbeat header information, that is, an empty heartbeat packet or a heartbeat confirmation packet.

[0077] Sending logic: In each heartbeat cycle, if no fault event is detected inside the module, a heartbeat packet containing only basic header information is sent as an existence confirmation.

[0078] The heartbeat information is transmitted in a publish-subscribe communication mode. The central monitoring unit acts as a subscriber and subscribes to the heartbeat information from each module; each module acts as a publisher and publishes the heartbeat information to the central monitoring unit according to the heartbeat cycle. Each module publishes the heartbeat information to the system's message queue or topic according to the set heartbeat cycle. The central monitoring unit continuously monitors these message queues or topics, and parses and processes the heartbeat information when it receives it, including, for empty heartbeat packets, confirming that the module is currently in normal operation and updating the module's online status information. Complete heartbeat packet processing, parsing the fault event information in the complete heartbeat packet, performing fault analysis based on the fault code and fault description, and triggering the corresponding alarm or processing mechanism.

[0079] S102, a heartbeat information management step, comprising storing and managing the heartbeat information in response to the collected heartbeat information, so that the fault detection strategy performs data query;

[0080] In some of the applications, the heartbeat information management step includes storing and managing the heartbeat information in response to the collected heartbeat information so that the fault detection strategy can perform data query, storing the heartbeat information in the recent period based on the cache mechanism, and the cache mechanism includes a lock-free circular queue; establishing a real-time disk function for the heartbeat information to ensure the security and traceability of the heartbeat information; and providing a data query interface for the module's internal fault detection strategy in the module and time dimensions.

[0081] It is understandable that in order to quickly respond to the collection and processing of heartbeat information, a lock-free circular queue is used as the main data structure of the cache. The queue can safely store the heartbeat information in the recent period in a multi-threaded environment, avoiding data competition and lock waiting overhead.

[0082] Parameter setting: Set the capacity of the lock-free ring queue to N heartbeat packets, for example, N=1000, the queue can cache the latest 1000 heartbeat packets (assuming the heartbeat period is 5 seconds, it is about 5000 seconds, that is, about 83 minutes of historical data).

[0083] Heartbeat information queueing and dequeuing: Whenever new heartbeat information is collected, it is encapsulated into a heartbeat packet and tried to be added to the circular queue without lock. If the queue is full, the oldest heartbeat packet is automatically overwritten according to the first-in-first-out principle.

[0084] To ensure the security and long-term traceability of heartbeat information, a real-time disk write function is designed. This function writes the heartbeat information in the cache to a persistent storage medium (such as a hard disk or SSD) periodically or asynchronously.

[0085] Frequency of disk flushing: Set the disk flushing operation to be performed every M heartbeat cycles, for example, M=100, that is, the disk flushing operation is performed every 500 seconds (100 5-second cycles), which balances data security and system write overhead.

[0086] In order to support the flexibility and efficiency of fault detection strategies, a data query interface is provided, allowing refined queries based on module and time dimensions.

[0087] Module dimension query: allows users to specify a module ID or module name and query the heartbeat information of the module within a specified time period. For example, query all heartbeat information of the "radar module" in the past hour.

[0088] Time dimension query: supports query by time range. Users can specify the start time and end time to obtain the heartbeat information of all modules or the heartbeat information of a specific module within the time period. For example, query all heartbeat information from "2023-05-10 10:00:00" to "2023-05-10 12:00:00".

[0089] Interface implementation: Design a RESTful API or internal service interface to provide the above query function. The interface receives query parameters (such as module ID, time range, etc.) and returns a list of heartbeat information that meets the conditions. The list contains the detailed content of the heartbeat packet, such as timestamp, module ID, fault event, etc.

[0090] For example, the "Lidar module" had a "data transmission interruption" fault at "2023-05-10 11:30:00", which was captured as a heartbeat message. The heartbeat message is first added to the lock-free circular queue. If the queue is not full at this time, it is directly stored; if it is full, the oldest heartbeat packet is overwritten. Subsequently, in the next disk drop cycle (assuming that the disk drop time point has not been reached at present), the heartbeat message will be written to the persistent storage together with other heartbeat messages that meet the drop conditions. When the fault detection strategy needs to analyze the fault, you can use the data query interface to specify the module ID as "Lidar module" and the time range as a period of time before and after "2023-05-1011:30:00" to obtain a list of heartbeat messages containing the fault event. The fault detection strategy can perform further analysis and processing based on this information.

[0091] S103, executing a fault detection step, including setting and executing the fault detection strategy, periodically traversing the stored heartbeat information, completing fault detection, and assigning a specified fault level to the detected fault based on the fault event;

[0092] In some of the applications, a fault detection step is performed, including setting and executing a fault detection strategy, periodically traversing the stored heartbeat information, completing fault detection, and assigning a specified fault level to the detected fault based on the fault event. Based on the characteristics and requirements of the autonomous driving system, a fault detection strategy is configured accordingly, and the fault detection strategy includes a heartbeat timeout strategy and a heartbeat information content verification strategy; all fault detection strategies are periodically traversed, and the status of the module is judged according to the strategy logic of the fault detection strategy; based on the judged module status, fault detection is completed, the fault level of the detected fault is assessed according to preset rules, and the assessment results are stored in the fault event cache of EventBus.

[0093] It can be understood that according to the characteristics and requirements of the autonomous driving system, two main types of fault detection strategies are set: heartbeat timeout strategy and heartbeat information content verification strategy.

[0094] Heartbeat timeout strategy: Set a reasonable heartbeat timeout threshold, such as 3 heartbeat cycles (assuming each cycle is 5 seconds, the timeout threshold is 15 seconds). If a module does not send heartbeat information within 3 consecutive heartbeat cycles, it is considered that the module has a heartbeat timeout failure.

[0095] Heartbeat information content verification strategy: Defines the verification rules for the heartbeat information content, such as checking whether the timestamp in the heartbeat packet is continuous, whether the fault code is valid, etc. If the heartbeat information content does not meet expectations, it is considered that the content verification has failed, indicating that there is an abnormality inside the module.

[0096] Perform troubleshooting:

[0097] Periodically traverse heartbeat information: Set a detection period (such as once per minute), and traverse the stored heartbeat information within the period. During the traversal process, the configured fault detection strategies are applied in sequence.

[0098] Policy logic determines module status: For each module, the heartbeat timeout policy and the heartbeat information content verification policy are applied according to its heartbeat information. If any policy determines that the module status is abnormal (such as timeout or content verification failure), the module is marked as a fault state.

[0099] Fault detection and rating:

[0100] Complete fault detection: After the traversal is completed, summarize the information of all modules marked as faulty.

[0101] Fault level assessment: The detected faults are assessed according to preset rules. For example, three fault levels are set: level 1 (serious fault, such as failure of key sensors), level 2 (moderate fault, such as abnormal non-critical components), and level 3 (minor fault, such as temporary communication interruption). The assessment rules can be based on comprehensive considerations of factors such as fault type, impact range, and recovery time.

[0102] For example, if the heartbeat timeout of the "radar sensor" module does not recover for multiple consecutive cycles, it is assessed as a level 1 fault; if the content verification of the "audio playback system" module fails but does not affect the safe driving of the vehicle, it is assessed as a level 3 fault.

[0103] Storage failure events:

[0104] EventBus fault event cache: Encapsulate the assessed fault events and related information (such as fault level, occurrence time, module ID, etc.) into event objects and publish them to the fault event cache of EventBus. As an efficient event publishing / subscribing mechanism, EventBus can ensure that fault events are delivered to relevant processing systems or components in a timely and accurate manner.

[0105] S104, a fault level management step, includes configuring and managing the fault level, performing version management on the fault level, and guiding fault handling based on configuration data of the fault level.

[0106] In some of the applications, the fault level management steps include configuring and managing fault levels, performing version management on fault levels, and guiding fault handling based on fault level configuration data; performing version management on fault levels, including displaying all current versions of fault levels and newly added fault level versions; calculating the md5 value of the fault level configuration file, and maintaining the relationship between the version and the md5 value through cloud services; the configuration file uses a triple to represent faults, and rates faults from three dimensions: system impact, operational impact, and parking urgency.

[0107] It is understandable that the fault level is configured and managed according to the actual situation and business needs of the autonomous driving system. The fault level is used to guide fault handling work.

[0108] Fault level definition: define different levels of faults, such as level 1 (serious fault), level 2 (moderate fault), level 3 (minor fault), etc. Each level corresponds to different system impact, operational impact, and parking urgency.

[0109] Configuration file format: The fault is represented by a triplet, and each fault entry contains three key information: system impact, operational impact, and parking urgency. These three dimensions together determine the level of the fault.

[0110] For example, fault entry 1: {System Impact: "High", Operating Impact: "Medium", Parking Urgency: "High"} is assessed as a Level 1 fault.

[0111] Fault item 2: {System Impact: "Medium", Operating Impact: "Low", Parking Urgency: "Low"}, is assessed as a level 3 fault.

[0112] In order to support flexible adjustment and optimization of fault levels, a version management strategy is implemented.

[0113] Version display: Provides a user interface or API interface to display the fault level configuration of all current versions. Users can view detailed information of each version, including version number, creation time, modification content, etc.

[0114] Add new version: Allows users or system administrators to add new fault level versions. When adding a new version, you need to upload a new configuration file and fill in the version description.

[0115] In order to ensure the consistency and security of the configuration files, the md5 value is used for version control.

[0116] MD5 value calculation: Whenever a new fault level configuration file is uploaded, the MD5 value of the file is automatically calculated. The MD5 value is a unique hash value used to verify the integrity of the file content.

[0117] Cloud service maintenance: Store each version of the configuration file and its corresponding md5 value in the cloud service. The cloud service provides a mapping between the version and the md5 value so that the correctness of the configuration file can be verified when necessary.

[0118] Fault level configuration data is not only used to assess and classify faults, but also to guide subsequent fault handling work.

[0119] Fault assessment: When a fault is detected, the fault level is assessed based on the specific fault information (such as error code, fault phenomenon, etc.) combined with the fault level configuration data.

[0120] Disposal suggestions: Provide corresponding fault disposal suggestions based on the evaluation results. For example, for a level 1 fault, it is recommended to stop the machine immediately and contact technical support; for a level 3 fault, just record it in the log and continue running.

[0121] In some of these applications, the fault level configuration data is read into the node cache when fault detection is started, and managed in the form of a hash table to facilitate fault level lookup and assignment, thereby guiding the fault handling of the autonomous driving system.

[0122] It is understandable that in order to improve data access efficiency, the loaded fault level configuration data is stored in the cache of the system node. The fault level configuration data is organized in the node cache in the form of a hash table. The hash table stores data in the form of a key-value pair, where the key can be a unique identifier of the fault (such as a fault code, module ID, etc.), and the value is the corresponding fault level configuration information (including system impact, operational impact, parking urgency, etc.). During the fault detection process, when a fault is detected, the corresponding fault level configuration is quickly found in the hash table through the unique identifier of the fault (such as a fault code). After finding the corresponding fault level configuration, the fault is rated according to the configuration information, and the rating result is assigned to the fault object or related processing logic. Based on the fault level assignment result, the autonomous driving system can more accurately judge the severity of the fault and formulate a fault handling strategy accordingly.

[0123] Combine the following Figures 2 to 4 The following describes the embodiments of the configurable and extensible automatic driving system fault detection method of the present invention in some applications:

[0124] In this embodiment, a unified node heartbeat mechanism is established to perform real-time and accurate fault detection on each module. By establishing a configurable fault level judgment mechanism, the flexibility of fault level setting can be increased, and a set of fault superposition calculation rules are proposed to perform superposition calculations on multiple faults that occur, and derive the fault level of the entire system to further guide fault handling.

[0125] like Figure 2 As shown in the figure, a heartbeat mechanism is established for each module of the autonomous driving system to collect the status information of each module in real time. Based on the publish-subscribe communication mode, each module is required to send heartbeat information to the fault detection module according to a unified heartbeat cycle (such as 50ms). The heartbeat information can carry information such as the timestamp, component name, and fault code of the fault event inside the module. If there are certain fault events inside the module, the relevant information of the above events is published through the heartbeat. If no fault event occurs inside the module, only an empty information packet is sent.

[0126] The fault detection module organizes the collected heartbeat information of each module according to the timestamp and stores it in the cache (for example, a lock-free circular queue can be used to store the node heartbeat information within the last 20 minutes) for the fault detection strategy within the module to use for data query in the module and time dimensions and support real-time data storage.

[0127] The fault detection module designs and adds fault detection strategies according to actual conditions (for example, the module heartbeat timeout strategy, that is, the number of heartbeat packets of the module in the recent period of time is calculated in the heartbeat cache to see whether it meets the timeout threshold number of times. If it is less than the timeout threshold, the heartbeat timeout and module abnormality are judged, otherwise the heartbeat is normal). The fault detection module performs a periodic traversal of all fault detection strategies to complete fault detection.

[0128] like Figure 3 As shown, by completing the fault level assessment of all faults in advance, a specified fault level is assigned to the detected fault event, and the fault event is stored in the fault event cache of EventBus.

[0129] In order to better guide the downstream modules to handle faults and realize the correspondence between the specified fault level and the handling method, the fault level is assessed according to three dimensions: system impact, operational impact and parking urgency. The system impact refers to the impact on the vehicle control module of the main system, the vehicle control module of the backup system and the auxiliary module. The operational impact refers to the impact on the completion of this order. The parking urgency refers to whether parking is currently required and the parking level requirements.

[0130] After the functional safety personnel complete the fault level assessment, they access the fault management tool through the browser to manage the fault level. The main function of this configuration tool is to manage the fault level version. The fault levels of all current versions are displayed through the page, and new fault level versions can be added. When the fault level configuration is completed, the tool will generate a fault level configuration file and use the MD5 tool to calculate the md5 value of the fault configuration file of this version. The relationship between the cloud service maintenance version and the md5 value. The functional safety personnel confirms the configuration.

[0131] like Figure 4 As shown in the figure, each fault is represented by a triple: {node name, component name, fault code}. Each fault is rated from three different dimensions: system impact, safety and operational impact, and parking urgency, and finally the fault level of the fault is obtained. Each fault on the vehicle is evaluated in three dimensions, and the fault level is finally configured in the fault level configuration file. When the node is started, the fault detection module reads the fault level configuration data into the node cache and manages it in the form of a hash table. This facilitates efficient fault level search and assignment on the vehicle.

[0132] This embodiment is described below in conjunction with application scenarios:

[0133] 1. The functional safety personnel evaluates that the fault level of a certain fault needs to be adjusted (or a new fault is added or deleted). They access the fault management service through a browser, make corresponding fault configurations, and obtain the version number and md5 value of the fault set.

[0134] 2. At this time, the fault management service generates a fault level configuration file and stores it on disk with the md5 value as the file name. At the same time, a new version information of the fault configuration file is added to the database, including the file name, path, and version number, for subsequent query use;

[0135] 3. Functional safety personnel configure the md5 value of the above fault set version into the code of the fault management module. After completing code compilation, the fault detection module is burned on the autonomous driving platform.

[0136] 4. After the fault detection module is started, the fault detection module reads the fault level configuration file on the vehicle side, calculates the md5 value of the configuration file, and compares it with the md5 value in the code. If it is inconsistent, it requests the fault management service through the http protocol for the fault level configuration file corresponding to the md5 value configured in the code;

[0137] 5. The fault management service finds the specified version of the configuration file by querying the md5 value and sends it to the vehicle-side fault detection module via http.

[0138] 6. The vehicle-side detection module stores and reads the configuration file, and puts the fault level information into a hash table, storing it with the fault name as the key and the fault level as the value;

[0139] 7. If a module on the vehicle side crashes, the heartbeat timeout strategy of the fault detection module detects the heartbeat timeout and queries the fault level of the fault in the fault level query hash table;

[0140] 8. After superimposing the fault levels, calculate the fault level of the system and return it.

[0141] This embodiment performs real-time fault detection on each module on the vehicle side through a unified fault level superposition scheme, combines the fault level version management tool on the cloud to complete the fault level configuration, and then realizes efficient management of the fault level through vehicle-cloud interaction and version verification, ultimately realizing an efficient fault detection scheme.

[0142] For the method steps disclosed in the above embodiments, the method steps are described as a series of action combinations for the purpose of simple description, but those skilled in the art should know that the embodiments of the present invention are not limited by the order of the actions described, because according to the embodiments of the present invention, some steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also know that the embodiments described in the specification are all preferred embodiments, and the actions involved are not necessarily required by the embodiments of the present invention.

[0143] like Figure 5 As shown, the present invention also provides a configurable and scalable automatic driving system fault detection system, comprising:

[0144] A heartbeat mechanism establishment module 201 is configured to establish a unified node heartbeat mechanism to collect heartbeat information of each module of the autonomous driving system in real time, wherein the heartbeat information includes a timestamp, component name and fault code of an internal fault event of each module;

[0145] A heartbeat information management module 202, configured to store and manage the heartbeat information in response to the collected heartbeat information, so that the fault detection strategy can perform data query;

[0146] An execution fault detection module 203 is configured to set and execute the fault detection strategy, perform periodic traversal on the stored heartbeat information, complete fault detection, and assign a specified fault level to the detected fault based on the fault event;

[0147] The fault level management module 204 is configured to configure and manage the fault level, perform version management on the fault level, and guide fault handling based on configuration data of the fault level.

[0148] It is worth noting that although only some basic functional modules are disclosed in the embodiments of the present invention, it does not mean that the composition of the present system is limited to the above basic functional modules. On the contrary, what the present embodiment wants to express is that on the basis of the above basic functional modules, those skilled in the art can arbitrarily add one or more functional modules in combination with the prior art to form an infinite number of embodiments or technical solutions. In other words, the present system is open rather than closed. Just because the present embodiment only discloses individual basic functional modules, it cannot be considered that the protection scope of the claims of the present invention is limited to the disclosed basic functional modules. At the same time, for the convenience of description, the above devices are described in terms of functions and are described separately in various units and modules. Of course, when implementing the present invention, the functions of each unit and module can be implemented in the same or one or more software and / or hardware.

[0149] like Figure 6 As shown, the present invention also provides an electronic device, including: a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory communicate with each other through the communication bus; a computer program is stored in the memory, and when the computer program is executed by the processor, the processor executes the steps of a configurable and extensible autonomous driving system fault detection method.

[0150] Figure 6 Schematic diagram of the structure of an electronic device provided by an embodiment of the present invention. Figure 6 The electronic device provided in the embodiment of the present invention includes: one or more processors 710 and a storage device 720; the processor 710 in the electronic device may be one or more, Figure 6 A processor 710 is taken as an example; the storage device 720 is used to store one or more programs; the one or more programs are executed by the one or more processors 710, so that the one or more processors 710 implement a configurable and scalable autonomous driving system fault detection method as described in any one of the embodiments of the present invention.

[0151] The electronic device may further include: an input device 730 and an output device 740 .

[0152] The processor 710, storage device 720, input device 730 and output device 740 in the electronic device can be connected via a bus or other means. Figure 6 The example of connecting through bus is taken in the following.

[0153] The storage device 720 in the electronic device is a computer-readable storage medium that can be used to store one or more programs, which can be software programs, computer executable programs, and modules, such as the program instructions / modules corresponding to the configurable and extensible automatic driving system fault detection method provided in the embodiment of the present invention. The processor 710 executes various functional applications and data processing of the electronic device by running the software programs, instructions, and modules stored in the storage device 720, that is, realizing the configurable and extensible automatic driving system fault detection method in the above method embodiment.

[0154] The storage device 720 may include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application required for at least one function; the data storage area may store data created according to the use of the electronic device, etc. In addition, the storage device 720 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, or other non-volatile solid-state storage device. In some instances, the storage device 720 may further include a memory remotely arranged relative to the processor 710, and these remote memories may be connected to the device via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0155] The input device 730 may be used to receive input digital or character information and generate key signal input related to user settings and function control of the electronic device. The output device 740 may include a display device such as a display screen.

[0156] The present invention also provides a computer-readable storage medium, which stores a computer program that can be executed by an electronic device. When the computer program runs on the electronic device, the electronic device executes the steps of a configurable and expandable autonomous driving system fault detection method.

[0157] Specifically, the computer storage medium of the embodiment of the present invention can adopt any combination of one or more computer-readable media. The computer-readable medium can be a computer-readable signal medium or a computer-readable storage medium. The computer-readable storage medium can be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples (non-exhaustive list) of computer-readable storage media include: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present embodiment, the computer-readable storage medium can be any tangible medium containing or storing a program, which can be used by an instruction execution system, device or device or used in combination with it.

[0158] The present invention also provides a vehicle, which is provided with the configurable and expandable automatic driving system fault detection system as described above.

[0159] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit it. Although the present invention has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or replace some or all of the technical features therein by equivalents. However, these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present invention.

Claims

1. A configurable and scalable automatic driving system fault detection method, characterized in that: include: The step of establishing a heartbeat mechanism includes establishing a unified node heartbeat mechanism to collect heartbeat information of each module of the autonomous driving system in real time, wherein the heartbeat information includes a timestamp, component name and fault code of an internal fault event of each module; A heartbeat information management step, comprising storing and managing the heartbeat information in response to the collected heartbeat information, so that the fault detection strategy can perform data query; Executing a fault detection step, including setting and executing the fault detection strategy, periodically traversing the stored heartbeat information, completing fault detection, and assigning a specified fault level to the detected fault based on the fault event; The fault level management step includes configuring and managing the fault level, performing version management on the fault level, and guiding fault handling based on configuration data of the fault level.

2. The configurable and scalable automatic driving system fault detection method according to claim 1, characterized in that: The heartbeat mechanism establishment step includes establishing a unified node heartbeat mechanism to collect heartbeat information of each module of the autonomous driving system in real time, wherein the heartbeat information includes the timestamp, component name and fault code of the internal fault event of each module, and further includes: Setting a unified heartbeat cycle, and configuring each module to send the heartbeat information according to the heartbeat cycle; In the heartbeat information, when the fault event exists inside the module, a complete heartbeat packet including information related to the fault event is sent; When the fault event does not exist inside the module, an empty heartbeat packet is sent; The heartbeat information is transmitted via a publish-subscribe communication mode.

3. The configurable and scalable automatic driving system fault detection method according to claim 1, characterized in that: The heartbeat information management step includes storing and managing the heartbeat information in response to the collected heartbeat information so that the fault detection strategy can perform data query, and further includes: Based on a cache mechanism, storing the heartbeat information within a recent period of time, wherein the cache mechanism includes a lock-free ring queue; Establish a real-time disk storage function for the heartbeat information to ensure the security and traceability of the heartbeat information; Provide a data query interface for the fault detection strategy within the module in the module and time dimensions.

4. The configurable and scalable automatic driving system fault detection method according to claim 1, characterized in that: The step of performing fault detection includes setting and executing the fault detection strategy, periodically traversing the stored heartbeat information, completing fault detection, and assigning a specified fault level to the detected fault based on the fault event, further including: Based on the characteristics and requirements of the autonomous driving system, the fault detection strategy is configured accordingly, wherein the fault detection strategy includes a heartbeat timeout strategy and a heartbeat information content verification strategy; Performing a periodic traversal on all the fault detection strategies, and determining the status of the module according to the strategy logic of the fault detection strategy; Based on the determined module status, the fault detection is completed, the detected fault is evaluated for fault level according to preset rules, and the evaluation result is stored in the fault event cache of EventBus.

5. The configurable and scalable automatic driving system fault detection method according to claim 1, characterized in that: The fault level management step includes configuring and managing the fault level, performing version management on the fault level, and guiding fault handling based on the configuration data of the fault level, further including: Performing version management on the fault levels, including displaying all current versions of fault levels and newly added fault level versions; Calculate the md5 value of the fault level configuration file, and maintain the relationship between the version and the md5 value through the cloud service; The configuration file uses a triplet method to represent faults, and rates faults from three dimensions: system impact, operational impact, and parking urgency.

6. The configurable and scalable automatic driving system fault detection method according to claim 5, characterized in that: The method further comprises: When fault detection is started, the fault level configuration data is read into the node cache and managed in the form of a hash table to facilitate fault level lookup and assignment, thereby guiding the fault handling of the autonomous driving system.

7. A configurable and scalable automatic driving system fault detection system, characterized in that: include: A heartbeat mechanism establishment module, configured to establish a unified node heartbeat mechanism, and collect heartbeat information of each module of the autonomous driving system in real time, wherein the heartbeat information includes a timestamp, a component name, and a fault code of a fault event within each module; A heartbeat information management module, configured to store and manage the heartbeat information in response to the collected heartbeat information, so that the fault detection strategy can perform data query; An execution fault detection module is configured to set and execute the fault detection strategy, periodically traverse the stored heartbeat information, complete fault detection, and assign a specified fault level to the detected fault based on the fault event; The fault level management module is configured to configure and manage the fault level, perform version management on the fault level, and guide fault handling based on configuration data of the fault level.

8. An electronic device, characterized in that: include: A processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory communicate with each other via the communication bus; a computer program is stored in the memory, and when the computer program is executed by the processor, the processor executes the steps of the method described in any one of claims 1 to 6.

9. A computer-readable storage medium, characterized in that: It stores a computer program executable by an electronic device, and when the computer program runs on the electronic device, the electronic device executes the steps of the method described in any one of claims 1 to 6.

10. A vehicle, characterized in that: The vehicle is provided with a configurable and scalable autonomous driving system fault detection system as described in claim 7.

Citation Information

Patent Citations

  • Abnormality management system of autonomous vehicle and abnormality handling method of autonomous vehicle

    CN110254439A

  • Safety redundancy control method and control system for autonomous vehicle

    CN115257791A

  • Management system of intelligent driving domain controller and related method thereof

    CN116039542A

  • Configuration file synchronization method and computing device

    CN116360840A

  • Method, system and device for fault early warning and fault recovery of message-oriented middleware

    CN116760688A

Cited By

  • Configurable and extensible fault detection method and system for autonomous driving system

    WO2026045531A1