A method, system, device, and medium for in-domain fault diagnosis
By setting up master and slave nodes within the vehicle domain, collecting fault diagnosis information and conducting subscription and publish communication, the shortcomings of in-domain processing in vehicle fault diagnosis in existing technologies are solved, achieving efficient fault handling and security assurance.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- CHONGQING CHANGAN TECH CO LTD
- Filing Date
- 2023-10-13
- Publication Date
- 2026-07-10
AI Technical Summary
Existing vehicle fault diagnosis methods lack in-domain diagnosis and handling, affecting the safety of vehicle applications.
Within the vehicle domain, master and slave nodes are set up. Fault diagnosis information is collected through the master node, and communication with control units within the domain is carried out through subscription and publication to handle faults and generate fault handling results.
It enables efficient fault diagnosis and handling within the vehicle domain, ensuring the safety and stability of application operation.
Smart Images
Figure CN117193262B_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of intelligent vehicle control, and more particularly to a method, system, device and medium for fault diagnosis within the field. Background Technology
[0002] Vehicle fault diagnosis technology is the technique of investigating the condition of a vehicle, identifying the location and cause of the fault, without disassembling or with minimal disassembly. With the development of the automotive industry, the level of electronic integration in vehicles is increasing, enhancing safety and comfort. However, these complex systems also lead to higher failure rates and more complex repairs. Therefore, after a vehicle malfunctions, the rapid collection and diagnosis of fault information, and the coordinated efforts between vehicle system modules to resolve the fault, are particularly important.
[0003] However, existing vehicle-side fault diagnosis lacks domain-specific diagnosis and processing, making it difficult to meet the current needs of vehicle development and application. Summary of the Invention
[0004] In view of the problems existing in the prior art, this application proposes an intra-domain fault diagnosis method, system, device and medium, which mainly solves the problem that the existing vehicle domain controller lacks effective intra-domain fault diagnosis, thus affecting the security of vehicle-side applications.
[0005] To achieve the above and other objectives, the technical solution adopted in this application is as follows.
[0006] This application provides a domain-specific fault diagnosis method, comprising: providing a master node and a slave node, wherein the master node and the slave node belong to different system-level chips in the same vehicle domain; collecting fault diagnosis information of itself and the slave node through the master node; communicating the fault diagnosis information with the domain-specific control unit through the master node via a subscription and publication method to perform domain-specific fault processing based on the fault diagnosis information, and obtaining a fault processing result.
[0007] In one embodiment of this application, the step of collecting fault diagnosis information of itself and the slave node through the master node includes: collecting application information of a preset fault prediction and health management module through the master node and the slave node respectively, wherein the application information is transmitted through a subscription and publication method based on the health diagnosis information of the application; the master node pulls the application information of the slave node and packages it together with its own application information to generate the fault diagnosis information.
[0008] In one embodiment of this application, the master node or the slave node collects the application information by calling the HAL / OSAL interface or a preset chip interface.
[0009] In one embodiment of this application, the step of collecting fault diagnosis information of itself and the slave node through the master node further includes: the master node or the slave node obtaining the health data of the external device through a subscription and publication method, wherein the external device is a device mounted on the same vehicle domain as the master node, and the health data is obtained by data abstraction of the operating data of the external device forwarded by the control unit within the domain; the slave node sends its own health data to the master node so that the master node can package and generate the fault diagnosis information based on the collected data.
[0010] In one embodiment of this application, the method for acquiring the health data includes: the external device sending operating data to the domain control unit via CAN communication; the domain control unit sending the operating data to a preset data abstraction module via Ethernet, so that the data abstraction module can extract data related to device health from the operating data to obtain the health data; and the data abstraction module forwarding the health data to the master node or the slave node via a publish-subscribe approach.
[0011] In one embodiment of this application, before packaging and generating the fault diagnosis information, the method further includes: the master node parses the collected data by calling a preset parsing library to generate a diagnostic code, and packages the diagnostic code to obtain the fault diagnosis information.
[0012] In one embodiment of this application, in-domain fault handling based on the fault diagnosis information includes: when the fault diagnosis information contains a fault diagnosis code, sending an application switching request to a preset service management terminal to invoke the application service to complete the application switching.
[0013] In one embodiment of this application, the fault diagnosis information is communicated with the domain control unit through a subscription and publication method via the master node, including: the master node publishing a topic corresponding to the fault diagnosis information; the domain control unit matching the topic published by the master node with a preset subscription topic, so as to obtain the fault diagnosis information of the master node after the matching is successful.
[0014] This application also provides an intra-domain fault diagnosis system, including: a master node and a slave node, wherein the master node and the slave node belong to different system-on-a-chips in the same vehicle domain; the master node collects fault diagnosis information of itself and the slave node, and communicates the fault diagnosis information with the intra-domain control unit through a subscription and publication method to perform intra-domain fault processing based on the fault diagnosis information and obtain fault processing results.
[0015] This application also provides a computer device, including: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the steps of the intra-domain fault diagnosis method.
[0016] This application also provides a computer-readable storage medium having a computer program stored thereon, wherein the computer program, when executed by a processor, implements the steps of the intra-domain fault diagnosis method.
[0017] As described above, the intra-domain fault diagnosis method, system, device, and medium provided in this application have the following beneficial effects.
[0018] This application sets up master and slave nodes within the same vehicle domain to collect diagnostic information based on the master and slave nodes, and sends the fault diagnosis information to the control unit within the domain through a subscription and publish method. This facilitates interaction between various modules or applications within the domain based on the information received by the control unit within the domain, thereby completing fault handling and ensuring the security of application operation. Attached Figure Description
[0019] Figure 1 This is a flowchart illustrating an intra-domain fault diagnosis method in one embodiment of this application.
[0020] Figure 2 This is a schematic diagram of the overall architecture of fault diagnosis in one embodiment of this application.
[0021] Figure 3 This is a schematic diagram of the architecture of an intra-domain fault diagnosis system in one embodiment of this application.
[0022] Figure 4 This is a schematic diagram of the structural framework of the device in one embodiment of this application. Detailed Implementation
[0023] The following specific examples illustrate the implementation of this application. Those skilled in the art can easily understand other advantages and effects of this application from the content disclosed in this specification. This application can also be implemented or applied through other different specific embodiments, and various details in this specification can also be modified or changed based on different viewpoints and applications without departing from the spirit of this application. It should be noted that, unless otherwise specified, the following embodiments and features in the embodiments can be combined with each other.
[0024] It should be noted that the illustrations provided in the following embodiments are only schematic representations of the basic concept of this application. Therefore, the drawings only show the components related to this application and are not drawn according to the actual number, shape and size of the components in the actual implementation. In the actual implementation, the form, quantity and proportion of each component can be arbitrarily changed, and the layout of the components may also be more complex.
[0025] Please see Figure 1 , Figure 1 This is a flowchart illustrating an intra-domain fault diagnosis method according to one embodiment of this application. In one embodiment, the intra-domain fault diagnosis method includes the following steps:
[0026] Step S100: Provide a master node and a slave node, wherein the master node and the slave node belong to different system-on-a-chips in the same vehicle domain.
[0027] In one embodiment, the vehicle domain may include a powertrain domain, body domain, chassis domain, cockpit domain, and autonomous driving domain. This embodiment takes the autonomous driving domain as an example. Within the autonomous driving domain, two system-on-a-chips (SOCs) SOC_a and SOC_b can be configured for fault diagnosis and processing within the domain. SOC_a can be configured as the master node, and SOC_b as the slave node. A data management module DM_master can be configured on the master node, and a data management module DM_client can be configured on the slave node SOC_b. The DM_master on the master node SOC_a completes the diagnostic collection and distribution processing for both SOCs.
[0028] Step S110: Collect fault diagnosis information of itself and slave nodes through the master node.
[0029] In one embodiment, data transmission between the master node and the slave node can be based on the DOIP (Diagnosis communication over Internet Protocol) protocol. Specifically, UDS (Unified Diagnostic Services) data can be transmitted based on the DOIP protocol, and the UDS service can be implemented on automotive buses such as CAN or Ethernet.
[0030] In one embodiment, the step of collecting fault diagnosis information of itself and slave nodes through the master node includes: collecting application information of the preset fault prediction and health management module through the master node and slave nodes respectively, wherein the application information is transmitted through a subscription and publication method based on the health diagnosis information of the application; the master node pulls the application information of the slave node and packages it together with its own application information to generate fault diagnosis information.
[0031] Please see Figure 2 , Figure 2This is a schematic diagram of the overall architecture of fault diagnosis in one embodiment of this application. Specifically, the application can transmit health diagnosis information to the Prognostics Health Management (PHM) module via a Data Distribution Service (DDS) subscription method. PHM then sends the information to PHM_report via DDS. PHM_report collects system, process, CPU, and other related information and sends it out via DDS. The application's DM_soft can subscribe to the application's health data published by PHM_report. Finally, DM-client or DM-master collects the data and packages it according to the corresponding diagnostic code. The application information may also include monitoring information such as application anomalies and functional groups obtained by general middleware.
[0032] In one embodiment, the master node or slave node collects application information by calling the HAL / OSAL interface or a preset chip interface. Specifically, the DM-client or DM-master module obtains the information by calling the HAL / OSAL interface or an interface provided by the chip vendor.
[0033] In one embodiment, the master node communicates with the slave node via DOIP to collect application data obtained by the slave node. The data obtained by the master node and the data obtained by the slave node are packaged together to obtain fault diagnosis data.
[0034] In one embodiment, the step of collecting fault diagnosis information from the master node and slave nodes further includes: the master node or slave node acquiring health data of external devices through a publish-subscribe mechanism, wherein the external devices are devices mounted on the same vehicle domain as the master node, and the health data is obtained by data abstraction of the operating data of the external devices forwarded by the domain control unit; the slave node sends its own health data to the master node, so that the master node can package and generate fault diagnosis information based on the collected data. Specifically, the vehicle where the master node and slave nodes are located may have multiple external devices. These external devices can send their own operating data to the domain control unit MCU via CAN communication. The domain control unit can forward the operating data of the external devices to the data abstraction module via Ethernet for data abstraction, extract data related to device health, and forward the extracted information to the master node and slave nodes via DDS, and then collect it by the DM-client or DM-master module.
[0035] In one embodiment, before packaging and generating fault diagnosis information, the process further includes: the master node parses the collected data by calling a preset parsing library to generate diagnostic codes, and packages the diagnostic codes to obtain fault diagnosis information. Specifically, DOIP or UDS can be called for parsing. The DM-client on SOC_b calls the DOIP&UDS dynamic library to send the collected diagnostic information of this chip to SOC_a via DOIP. Similarly, the DM-master module on SOC_a calls the DOIP&UDS dynamic library to complete the parsing and simultaneously collect the diagnostic information of this chip.
[0036] Step S120: The master node communicates the fault diagnosis information with the control unit in the domain through a subscription and publication method to perform fault handling in the domain based on the fault diagnosis information and obtain the fault handling result.
[0037] In one embodiment, the fault diagnosis information is communicated with the domain control unit via a subscription and publication method through the master node, including: the master node publishing a topic corresponding to the fault diagnosis information; the domain control unit matching the topic published by the master node with a preset subscription topic, so as to obtain the fault diagnosis information of the master node after a successful match.
[0038] Specifically, the master node, acting as the publisher of fault diagnosis information, can publish topics corresponding to faults based on this information. Domain control units, acting as data readers, subscribe to topics of interest. The master node publishes data by calling the `write` function of the `datawriter`. Domain control units subscribe to data through the `datareader`, and the subscription method can be asynchronous, synchronous, or non-blocking.
[0039] In one embodiment, the master node can interact with the MCU (Microcontroller Unit) within the domain by calling DDS. The DM_master on the master node SOC_a uses DDS subscription and publication to communicate with the MCU within the domain, completing the storage and retrieval of traditional Diagnostic Trouble Codes (DTCs). The DM_master on the master node SOC_a integrates a Service Management (SM) client. The SM client can use DDS subscription and publication to communicate with the Status Management module, handling communication required for function degradation processing after an anomaly occurs during the diagnostic process, or the PHM-report can handle the communication for diagnostic function degradation processing.
[0040] In one embodiment, for situations where a fault code necessitates functional degradation, the safe operation of the application can be ensured by switching applications or starting a backup application. When an anomaly occurs, the SM client sends a functional group switching request signal to the SM according to the logic configured in the SOA (Service-Oriented Architecture) toolchain. The SM and EM (Execution Management) work together to complete the switch, and finally, the PHM (Programmable Execution Manager) provides feedback on the execution result, forming a closed loop.
[0041] Based on the above technical solution of this application, fault information can be better collected and fault diagnosis can be completed based on the domain controller at the vehicle end. When an anomaly occurs, the diagnostic function will be downgraded. This can effectively meet the fault diagnosis and processing needs of various vehicle domains and ensure the stability and security of module interaction within the domain.
[0042] Please see Figure 3 , Figure 3 This is a schematic diagram of the architecture of an intra-domain fault diagnosis system according to one embodiment of this application. This embodiment provides an intra-domain fault diagnosis system for executing the intra-domain fault diagnosis method in the foregoing method embodiments. Since the technical principles of the system embodiment are similar to those of the foregoing method embodiments, the same technical details will not be repeated.
[0043] In one embodiment, an intra-domain fault diagnosis system includes a master node 30 and a slave node 31, wherein the master node 30 and the slave node 31 belong to different system-on-a-chips in the same vehicle domain; the master node 30 collects fault diagnosis information of itself and the slave node 31, and communicates the fault diagnosis information with the intra-domain control unit through a subscription and publication method to perform intra-domain fault processing based on the fault diagnosis information and obtain fault processing results.
[0044] In one embodiment, the step of the master node 30 collecting fault diagnosis information from itself and the slave node 31 includes: collecting application information of the preset fault prediction and health management module through the master node 30 and the slave node 31 respectively, wherein the application information is transmitted through a subscription and publication method based on the health diagnosis information of the application; the master node 30 pulls the application information of the slave node 31 and packages it together with its own application information to generate fault diagnosis information.
[0045] In one embodiment, the master node 30 or the slave node 31 collects application information by calling the HAL / OSAL interface or a preset chip interface.
[0046] In one embodiment, the step of the master node 30 collecting fault diagnosis information of itself and the slave node 31 further includes: the master node 30 or the slave node 31 obtaining the health data of the external device through a subscription and publication method, wherein the external device is a device mounted on the same vehicle domain as the master node 30, and the health data is obtained by data abstraction of the operating data of the external device forwarded by the control unit within the domain; the slave node 31 sends its own health data to the master node 30 so that the master node 30 can package and generate fault diagnosis information based on the collected data.
[0047] In one embodiment, the method for acquiring health data includes: the external device sending operating data to the domain control unit via CAN communication; the domain control unit sending the operating data to a preset data abstraction module via Ethernet, so that the data abstraction module can extract the data related to device health from the operating data to obtain health data; and the data abstraction module forwarding the health data to the master node 30 or the slave node 31 via a publish-subscribe method.
[0048] In one embodiment, the master node 30 parses the collected data by calling a preset parsing library to generate diagnostic codes, and packages the diagnostic codes to obtain fault diagnosis information.
[0049] In one embodiment, handling intra-domain faults based on fault diagnosis information includes: when the fault diagnosis information contains a fault diagnosis code, sending an application switching request to a preset service management terminal to invoke the application service to complete the application switching.
[0050] In one embodiment, the fault diagnosis information is communicated with the domain control unit via a subscription and publication method through the master node, including: the master node publishing a topic corresponding to the fault diagnosis information; the domain control unit matching the topic published by the master node with a preset subscription topic, so as to obtain the fault diagnosis information of the master node after a successful match.
[0051] This application also provides an intra-domain fault diagnosis device, which may include: one or more processors; and one or more machine-readable media storing instructions thereon, which, when executed by the one or more processors, cause the device to perform... Figure 1The method described herein. In practical applications, the device can be used as a terminal device or as a server. Examples of terminal devices may include: ultrasonic scalpel host, smartphone, tablet computer, e-book reader, MP3 (Moving Picture Experts Group Audio Layer III) player, MP4 (Moving Picture Experts Group Audio Layer IV) player, laptop computer, in-vehicle computer, desktop computer, set-top box, smart TV, wearable device, etc. This application does not limit the specific device.
[0052] This application also provides a computer-readable storage medium storing one or more modules (programs) that, when applied to a device, enable the device to execute embodiments of this application. Figure 1 The instructions for the steps included in the fault diagnosis method within the domain. Machine-readable media can be any usable medium that a computer can store, or a data storage device such as a server or data center that integrates one or more usable media. The usable medium can be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., DVDs), or semiconductor media (e.g., solid-state drives (SSDs)).
[0053] See Figure 4 This embodiment provides a device 80, which can be a desktop computer, a portable computer, a smartphone, or other devices. Specifically, the device 80 includes at least a memory 82 and a processor 83 connected via a bus 81. The memory 82 stores a computer program, and the processor 83 executes the computer program stored in the memory 82 to perform all or part of the steps in the aforementioned method embodiments.
[0054] The system bus mentioned above can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. This system bus can be divided into address bus, data bus, control bus, etc. For ease of representation, only one thick line is used in the diagram, but this does not indicate that there is only one bus or one type of bus. The communication interface is used to enable communication between the database access device and other devices (e.g., clients, read-write libraries, and read-only libraries). Memory may include Random Access Memory (RAM) and may also include non-volatile memory, such as at least one disk storage device.
[0055] The processors mentioned above can be general-purpose processors, including central processing units (CPUs), network processors (NPs), etc.; they can also be digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components.
[0056] The above embodiments are merely illustrative of the principles and effects of this application and are not intended to limit this application. Any person skilled in the art can modify or alter the above embodiments without departing from the spirit and scope of this application. Therefore, all equivalent modifications or alterations made by those skilled in the art without departing from the spirit and technical concept disclosed in this application should still be covered by the claims of this application.
Claims
1. A method for intra-domain fault diagnosis, characterized in that, include: Provide a master node and a slave node, wherein the master node and the slave node belong to different system-on-a-chips in the same vehicle domain; The process of collecting fault diagnosis information from the master node and the slave nodes includes: collecting application information of a preset fault prediction and health management module from the master node and the slave node respectively, wherein the application information is transmitted through a subscription and publication method based on the application's health diagnosis information; the master node pulls the application information from the slave node and packages it together with its own application information to generate the fault diagnosis information; before packaging the fault diagnosis information, the process further includes: the master node parses the collected data by calling a preset parsing library to generate a diagnostic code, and packages the diagnostic code to obtain the fault diagnosis information; The master node communicates the fault diagnosis information with the domain control unit through a subscription and publication method to perform domain fault handling based on the fault diagnosis information and obtain the fault handling result; the domain fault handling based on the fault diagnosis information includes: when the fault diagnosis information contains a fault diagnosis code, sending an application switching request to the preset service management terminal to call the application service to complete the application switching.
2. The intra-domain fault diagnosis method according to claim 1, characterized in that, The master node or the slave node collects the application information by calling the HAL / OSAL interface or a preset chip interface.
3. The intra-domain fault diagnosis method according to claim 1, characterized in that, The step of collecting fault diagnosis information of itself and the slave nodes through the master node also includes: The master node or the slave node obtains the health data of the external device through a publish-subscribe method. The external device is a device mounted on the same vehicle domain as the master node. The health data is obtained by data abstraction from the operating data of the external device forwarded by the control unit within the domain. The slave node sends its own health data to the master node, so that the master node can package and generate the fault diagnosis information based on the collected data.
4. The intra-domain fault diagnosis method according to claim 3, characterized in that, The methods for obtaining the health data include: The external device sends operating data to the control unit within the domain via CAN communication; The domain control unit sends the operating data to a preset data abstraction module via Ethernet, so that the data abstraction module can extract the data related to device health from the operating data to obtain the health data; The data abstraction module forwards the health data to the master node or the slave node through a publish-subscribe mechanism.
5. The intra-domain fault diagnosis method according to claim 1, characterized in that, The fault diagnosis information is communicated to the domain control units via a publish-subscribe method through the master node, including: The topic corresponding to the fault diagnosis information published by the master node; The domain control unit matches the preset subscription topics with the topics published by the master node, so as to obtain the fault diagnosis information of the master node after the match is successful.
6. A domain-specific fault diagnosis system, characterized in that, include: Master node and slave node, wherein the master node and the slave node belong to different system-on-chips in the same vehicle domain; The master node collects fault diagnosis information from itself and the slave nodes, including: collecting application information of a preset fault prediction and health management module through the master node and the slave nodes respectively, wherein the application information is transmitted through a subscription and publication method based on the health diagnosis information of the application; the master node pulls the application information of the slave nodes and packages it together with its own application information to generate the fault diagnosis information; before packaging and generating the fault diagnosis information, the master node further includes: parsing the collected data by calling a preset parsing library to generate a diagnostic code, packaging the diagnostic code to obtain the fault diagnosis information, and communicating the fault diagnosis information with the domain control unit through a subscription and publication method to perform domain fault handling based on the fault diagnosis information and obtain the fault handling result; performing domain fault handling based on the fault diagnosis information includes: when the fault diagnosis information contains a fault diagnosis code, sending an application switching request to a preset service management terminal to call the application service to complete the application switching.
7. A computer device, comprising: A memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor, when executing the computer program, implements the steps of the domain fault diagnosis method according to any one of claims 1 to 5.
8. A computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of the domain fault diagnosis method according to any one of claims 1 to 5.