Vehicle communication fault diagnosis method and device, vehicle-mounted terminal and vehicle

Abstract

The invention provides a vehicle communication fault diagnosis method and device, a vehicle-mounted terminal and a vehicle, and the method comprises the steps: monitoring the integrity of a physical layer signal of a vehicle-mounted communication network of the vehicle to obtain a physical layer state, monitoring the communication time sequence of a protocol layer of the vehicle-mounted communication network to obtain a protocol layer state, and performing rationality verification on application layer data of the vehicle-mounted communication network to obtain an application layer state, if any one of the states is a fault state, querying a message receiving and transmitting record corresponding to the central gateway based on a communication event triggering the fault state, and sending a response message to the central gateway based on a response message record of the target controller in the message receiving and transmitting record. And determining whether the local controller has the communication fault or the target controller has the communication fault, and determining the fault level according to the type of the controller with the communication fault, thereby solving the technical problems of inaccurate fault positioning and single safety response during vehicle communication fault diagnosis.

Description

Technical Field

[0001] This invention relates to the field of vehicle communication technology, specifically to a vehicle communication fault diagnosis method, device, vehicle terminal, and vehicle. Background Technology

[0002] With the increasing complexity of automotive electronic and electrical architecture, in-vehicle network systems have become digital nervous systems integrating powertrain, chassis control, body electronics, and advanced driver assistance functions. Their network topology is becoming increasingly complex, with the number of controllers and data exchange volume growing exponentially. The real-time performance, reliability, and security of communication directly determine the functional safety of the entire vehicle.

[0003] In related technologies, various basic diagnostic methods are commonly used to ensure communication reliability. One common approach is timeout detection, which sets a fixed time threshold for critical message responses at the application or protocol layer; if a response times out, communication is considered abnormal. Another typical solution is redundant communication, which uses dual-channel hardware or a retransmission mechanism to switch to a backup channel to maintain basic communication when the primary channel fails. However, these technical solutions have significant drawbacks. They lack a single diagnostic dimension, coordination, and correlation, easily leading to misjudgments of faults or unclear root cause localization and insufficient fault tracing capabilities. Furthermore, the security strategies for responding to faults in these technologies are simplistic, potentially overreacting to low-level faults or underreacting to high-level risks. Summary of the Invention

[0004] This invention provides a vehicle communication fault diagnosis method, device, vehicle terminal, and vehicle to solve the technical problems of inaccurate fault location and limited safety response when performing vehicle communication fault diagnosis in related technologies.

[0005] This invention provides a vehicle communication fault diagnosis method, the method comprising: monitoring the physical layer status, protocol layer status, and application layer status of the vehicle's in-vehicle communication network; if any one of the physical layer status, protocol layer status, and application layer status is in a fault state, querying the message transmission and reception records corresponding to the central gateway of the in-vehicle communication network based on the communication event that triggered the fault state, wherein the vehicle controller sending the communication message in the message transmission and reception records is the local controller, and the vehicle controller receiving the communication message is the target controller; determining whether the local controller or the target controller has a communication fault based on the response message record of the target controller in the message transmission and reception records; and determining the fault level according to the type of controller with a communication fault.

[0006] In one embodiment of the present invention, determining whether the local controller communication or the target controller communication has a communication failure based on the response message record of the target controller in the message transmission and reception record includes: if no response message record of the target controller is found in the message transmission and reception record, then the target controller has a communication failure; if a response message record of the target controller is found in the message transmission and reception record, then the local controller has a communication failure.

[0007] In one embodiment of the present invention, determining the fault level based on the type of controller with communication failure includes: if the controller with communication failure is a preset first type of controller, the fault level is determined to be high; if the controller with communication failure is a preset second type of controller, the fault level is determined to be medium; and if the controller with communication failure is a preset third type of controller, the fault level is determined to be low.

[0008] In one embodiment of the present invention, after determining the fault level according to the controller type with communication failure, the method further includes: if the fault level is high, controlling the vehicle to safely stop based on a preset safe parking strategy; if the fault level is medium, limiting the torque output of the vehicle; if the fault level is low, switching the power supply of the vehicle to a backup power supply.

[0009] In one embodiment of the present invention, monitoring the physical layer status of the vehicle's in-vehicle communication network includes: monitoring the differential voltage of the vehicle's controller local area network bus; if the fluctuation range of the differential voltage exceeds a preset range in a single communication event, the physical layer status is determined to be a fault state; and / or, monitoring the error frame rate of the vehicle's Ethernet; if the error frame rate exceeds a preset frame rate threshold in a single communication event, the physical layer status is determined to be a fault state.

[0010] In one embodiment of the present invention, monitoring the protocol layer status of the vehicle's in-vehicle communication network includes: monitoring the response time in the in-vehicle communication network; if the response time exceeds a dynamic response threshold in a communication event, the protocol layer status is determined to be a fault state; wherein the dynamic response threshold is determined based on the current load and historical communication delay of the in-vehicle communication network.

[0011] In one embodiment of the present invention, monitoring the application layer status of the vehicle's in-vehicle communication network includes: acquiring the application layer data transmitted through the in-vehicle communication network; verifying the rationality of the application layer data according to the data identifier of the application layer data; if the rationality verification of the application layer data fails in a communication event, the application layer status is determined to be a fault state.

[0012] This invention also provides a vehicle communication fault diagnosis device, the device comprising: a multi-level monitoring module for monitoring the physical layer signal integrity of the vehicle's in-vehicle communication network to obtain the physical layer status, monitoring the protocol layer communication timing of the in-vehicle communication network to obtain the protocol layer status, and verifying the rationality of the application layer data of the in-vehicle communication network to obtain the application layer status; a message record query module for querying the message transmission and reception records corresponding to the central gateway based on the communication event that triggered the fault status if any one of the physical layer status, protocol layer status, and application layer status is a fault status; a message record parsing module for identifying the vehicle controller that sends the communication message in the message transmission and reception records as the local controller and the vehicle controller that receives the communication message as the target controller; a fault location module for determining whether the local controller or the target controller has a communication fault based on the response message record of the target controller in the message transmission and reception records; and a fault classification module for determining the fault level according to the type of controller with a communication fault.

[0013] The present invention also provides a vehicle-mounted terminal, the vehicle-mounted terminal comprising: one or more processors; and a storage device for storing one or more programs, wherein when the one or more programs are executed by the one or more processors, the vehicle-mounted terminal implements the vehicle communication fault diagnosis method as described in any of the above embodiments.

[0014] The present invention also provides a computer-readable storage medium storing a computer program, which, when executed by a computer processor, causes the computer to perform any of the vehicle communication fault diagnosis methods described in the above embodiments.

[0015] The beneficial effects of this invention are as follows: This invention proposes a vehicle communication fault diagnosis method, device, vehicle terminal, and vehicle. By monitoring the physical layer signal integrity of the vehicle's in-vehicle communication network to obtain the physical layer status, monitoring the protocol layer communication timing of the in-vehicle communication network to obtain the protocol layer status, and verifying the rationality of the application layer data of the in-vehicle communication network to obtain the application layer status, if any of the physical layer status, protocol layer status, or application layer status is a fault state, the message transmission and reception records corresponding to the central gateway are queried based on the communication event that triggered the fault state. The vehicle controller that sent the communication message in the message transmission and reception records is identified as the local controller, and the vehicle controller that received the communication message is identified as the local controller. The system identifies the target controller and determines whether a communication failure exists in the local controller or the target controller based on the target controller's response message records. The failure level is determined according to the type of controller experiencing the communication failure. Through joint monitoring of the physical layer, protocol layer, and application layer, and based on the full message records of the central gateway that triggered the failure, it is determined whether the target controller failed to respond or the local controller experienced a reception failure. This allows for precise location of the root cause of the failure. Different failure levels are determined based on the failure type and the criticality of the controllers involved, and corresponding response measures are implemented. This ensures that high-level failures are handled rigorously and securely while preventing overreactions to low-level failures.

[0016] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and are not intended to limit the invention. Attached Figure Description

[0017] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with the invention and, together with the description, serve to explain the principles of the invention. It is obvious that the drawings described below are merely some embodiments of the invention, and those skilled in the art can obtain other drawings based on these drawings without any inventive effort.

[0018] In the attached diagram:

[0019] Figure 1 This is a schematic diagram illustrating the implementation environment of a vehicle communication fault diagnosis method according to an embodiment of the present invention. Figure 2 This is a flowchart of a vehicle communication fault diagnosis method provided in one embodiment of the present invention; Figure 3 This is a flowchart illustrating a multi-level vehicle communication monitoring method provided in one embodiment of the present invention; Figure 4 This is a flowchart illustrating vehicle communication fault location in one embodiment of the present invention; Figure 5This is a block diagram of a vehicle communication fault diagnosis device provided in one embodiment of the present invention; Figure 6 This is a schematic diagram of a vehicle-mounted terminal provided in one embodiment of the present invention. Detailed Implementation

[0020] The following specific examples illustrate the implementation of the present invention. Those skilled in the art can easily understand other advantages and effects of the present invention from the content disclosed in this specification. The present invention can also be implemented or applied through other different specific embodiments. Various details in this specification can also be modified or changed based on different viewpoints and applications without departing from the spirit of the present invention. In the absence of conflict, the following embodiments and features in the embodiments can be combined with each other.

[0021] It should be noted that the illustrations provided in the following embodiments are only schematic representations of the basic concept of the present invention. The drawings only show the components related to the present invention 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.

[0022] In the following description, numerous details are explored to provide a more thorough explanation of embodiments of the invention. However, it will be apparent to those skilled in the art that embodiments of the invention may be practiced without these specific details. In other embodiments, well-known structures and devices are shown in block diagram form rather than in detail to avoid obscuring embodiments of the invention.

[0023] Please see Figure 1 , Figure 1 This is a schematic diagram illustrating the implementation environment of a vehicle communication fault diagnosis method according to an embodiment of the present invention.

[0024] like Figure 1 As shown, the implementation environment may include a central gateway, a mirror database of the central gateway, a protocol monitoring service for vehicle communication, and a vehicle controller. The protocol monitoring service includes at least a physical layer probe, a protocol parsing engine, and an application layer verifier. The vehicle controller includes at least a BMS (Battery Management System), a VCU (Vehicle Control Unit), an MCU (Motor Control Unit), an OBC (On-Board Charger), and a DCDC (DC-to-DC Converter).

[0025] For example, the central gateway, as the core routing node for vehicle communication, is responsible for packet forwarding, protocol conversion, and data exchange between different network domains (the vehicle's Controller Area Network bus or Ethernet). A mirror database, associated with the central gateway, serves as its mirror image, recording and storing in real-time the raw data, timestamps, and routing information of all communication packets flowing through the central gateway, providing a data foundation for fault tracing and location. A protocol monitoring service performs multi-level monitoring of vehicle communication in real-time. The physical layer probe collects and analyzes physical layer signal quality, the protocol parsing engine monitors dynamic timeouts at the protocol layer, and the application layer verifier verifies the rationality of application layer data, ensuring it remains within a preset reasonable range. Vehicle controllers are interconnected and communicate with each other via the vehicle's Controller Area Network bus or Ethernet.

[0026] Please see Figure 2 , Figure 2 This is a flowchart illustrating a vehicle communication fault diagnosis method according to an embodiment of the present invention. This method can be applied to... Figure 1 The implementation environment shown can also be applied to other exemplary implementation environments and specifically executed by devices in other implementation environments. This embodiment does not limit the implementation environment to which the method is applicable.

[0027] like Figure 2 As shown, in an exemplary embodiment, the vehicle communication fault diagnosis method includes at least steps S210 to S250, which are described in detail below: Step S210: Monitor the physical layer status, protocol layer status, and application layer status of the vehicle's in-vehicle communication network, including: monitoring the physical layer signal integrity of the vehicle's in-vehicle communication network to obtain the physical layer status; monitoring the protocol layer communication timing of the in-vehicle communication network to obtain the protocol layer status; and verifying the rationality of the application layer data of the in-vehicle communication network to obtain the application layer status.

[0028] In one embodiment of the present invention, monitoring the physical layer signal integrity of the vehicle's in-vehicle communication network to obtain the physical layer status includes: monitoring the differential voltage of the vehicle's controller local area network bus; if the fluctuation range of the differential voltage exceeds a preset range in a communication event, the physical layer status is determined to be a fault state; and / or, monitoring the error frame rate of the vehicle's Ethernet; if the error frame rate exceeds a preset frame rate threshold in a communication event, the physical layer status is determined to be a fault state.

[0029] For example, the differential voltage of the controller LAN bus used for communication events between BMS and VCU is collected in real time by physical layer probes. If the fluctuation range of the differential voltage of this communication event is continuously exceeded (if it exceeds the preset time, it is considered to be continuously exceeded; the preset time can be set to 5s, that is, if it exceeds 5s, it is considered to be continuously exceeded) within the preset range (which can be set to [1.5V, 3.5V]), the physical layer status is marked as a fault state.

[0030] For example, the vehicle's Ethernet is monitored for error frame rate. If the error frame rate exceeds a preset frame rate threshold (which can be set to 10-6) in a communication event, the physical layer status is marked as a fault state.

[0031] In one embodiment of the present invention, monitoring the protocol layer communication timing of the vehicle communication network to obtain the protocol layer status includes: monitoring the response time in the vehicle communication network; if the response time exceeds a dynamic response threshold in a communication event, the protocol layer status is obtained as a fault state; wherein, the dynamic response threshold is determined based on the current load and historical communication delay of the vehicle communication network.

[0032] For example, in a BMS-VCU communication event, the communication messages (e.g., status query messages) sent by the BMS are monitored. A timer is started when the communication message is sent, and a dynamic response threshold for this communication event is dynamically calculated based on the current load of the vehicle communication network and the average historical communication delay between the BMS and the VCU. If the VCU's response time exceeds the dynamic response threshold, the protocol layer status is marked as a fault state.

[0033] In one embodiment of the present invention, the rationality verification of application layer data of the vehicle communication network to obtain the application layer status includes: acquiring application layer data transmitted through the vehicle communication network; verifying the rationality of the application layer data according to the data identifier of the application layer data; if the rationality verification of the application layer data fails in a communication event, the application layer status is obtained as a fault state.

[0034] For example, the application layer verifier performs a validity check on the application layer data in the response message received from the VCU. For instance, if the SOC (State of Charge) returned by the VCU is greater than 100%, the validity check fails and the application layer state is marked as a fault state.

[0035] Figure 3 This is a flowchart of a multi-level vehicle communication monitoring method provided in one embodiment of the present invention, such as... Figure 3As shown, vehicle communication is monitored in real time, including physical layer monitoring, protocol layer monitoring, and application layer monitoring. If an abnormal signal is detected at the physical layer, it is marked as a physical layer fault; if a message response timeout is detected at the protocol layer, it is marked as a protocol layer fault; and if invalid data is detected at the application layer, it is marked as an application layer fault. If the physical layer signal is normal, the protocol layer message response is normal, and the application layer data is valid, then vehicle communication is normal.

[0036] Step S220: If any of the physical layer state, protocol layer state, and application layer state is in a fault state, query the message transmission and reception records corresponding to the central gateway of the vehicle communication network based on the communication event that triggered the fault state.

[0037] For example, in multi-level monitoring of communication events for vehicle communication, if the state of any of the monitored physical layer, protocol layer, and application layer is a fault state, the message transmission and reception records corresponding to the central gateway are queried based on the communication event that triggered the fault state, including the message transmission and reception records of the vehicle controller associated with the communication event.

[0038] For example, if a protocol layer status of a communication event between the BMS and VCU is detected as faulty, then all message transmission and reception records between the BMS and VCU within a preset window time are queried in the mirror database of the central gateway.

[0039] Step S230: The vehicle controller that sends the communication message in the message transmission and reception record is identified as the local controller, and the vehicle controller that receives the communication message is identified as the target controller.

[0040] For example, if the BMS sends a communication message to the VCU in the message transmission record, then the BMS is identified as the local controller and the VCU is identified as the target controller.

[0041] Step S240: Based on the response message record in the message transmission and reception record of the target controller, determine whether the local controller or the target controller has a communication failure.

[0042] In one embodiment of the present invention, determining whether the local controller communication or the target controller communication has a communication failure based on the response message record of the target controller in the message transmission and reception record includes: if no response message record of the target controller is found in the message transmission and reception record, then the target controller has a communication failure; if a response message record of the target controller is found in the message transmission and reception record, then the local controller has a communication failure.

[0043] For example, if at least one valid response message record from the target controller is found in the message transmission and reception records, it indicates that the target controller has responded, but the local controller failed to receive it normally, so it is determined that there is a communication failure in the local controller.

[0044] For example, if no valid response message record from the target controller is found in the message transmission and reception record, it indicates that the target controller has not responded to the communication message normally, and it is determined that there is a communication failure in the target controller.

[0045] Figure 4 This is a flowchart illustrating vehicle communication fault location in one embodiment of the present invention, such as... Figure 4 As shown, if the local controller is a BMS, and the BMS does not receive a response from the target controller after sending a communication message, it queries the message transmission and reception records of the BMS and the target controller in the mirror database. If a response message from the target controller is found in the message transmission and reception records, it is determined that there is a local fault in the BMS, and the BMS's communication interface is repaired. If no response message from the target controller is found in the message transmission and reception records, it is determined that the target controller communication is lost, and a hierarchical security response is performed based on the target controller's controller type.

[0046] Step S250: Determine the fault level based on the type of controller with communication failure.

[0047] In one embodiment of this application, determining the fault level based on the type of controller with communication failure includes: if the controller with communication failure is a preset first type controller, the fault level is determined to be high; if the controller with communication failure is a preset second type controller, the fault level is determined to be medium; and if the controller with communication failure is a preset third type controller, the fault level is determined to be low.

[0048] For example, a first-type controller is preset to be a vehicle controller responsible for core vehicle decisions. A communication failure in this first-type controller could lead to the loss of vehicle functionality. For instance, the first-type controller could be a vehicle controller. A second-type controller is preset to be a vehicle controller controlling the drive system. A communication failure in this second-type controller could affect the vehicle's driving capability. For instance, the second-type controller could be a motor controller. A third-type controller is preset to be a controller responsible for vehicle energy conversion or auxiliary power supply. A communication failure in this third-type controller could affect vehicle subsystems or comfort functions. For instance, the third-type controller could be a DC-DC converter or an on-board charger.

[0049] For example, if the target controller has a communication failure, the fault level is determined according to the type of controller with the communication failure, including: if the target controller is a vehicle controller, the fault level is determined to be high; if the target controller is a motor controller, the fault level is determined to be medium; if the target controller is a DC voltage conversion controller, the fault level is determined to be low.

[0050] For example, if a communication failure occurs in the local controller, the failure level is determined based on the controller type of the local controller.

[0051] In one embodiment of the present invention, after determining the fault level according to the controller type with communication failure, the method further includes: performing graded safety response based on the fault level; if the fault level is high, controlling the vehicle to stop safely based on a preset safe parking strategy; if the fault level is medium, limiting the torque output of the vehicle; if the fault level is low, switching the vehicle's power supply to a backup power source.

[0052] For example, if the vehicle controller has a communication failure, and the failure level is high, the vehicle is controlled to park safely based on a preset safe parking strategy, including activating the hazard warning lights and slowly pulling over to the side of the road.

[0053] For example, if the motor controller has a communication failure, with the failure level being medium, the torque output is limited based on a preset safe torque threshold, and navigation prompts to the nearest repair point are planned, causing the vehicle to enter limp mode.

[0054] For example, if there is a communication failure in the DC voltage conversion controller or the on-board charging controller, and the failure level is low, the vehicle's power supply will be switched to the backup power supply, and a prompt message indicating a failure in the charging system or auxiliary power supply will be displayed on the instrument panel to remind the driver to perform maintenance in a timely manner.

[0055] In embodiments of the present invention, by quickly locating the faulty controller, the efficiency of fault diagnosis and the targeted nature of repair are improved, reducing ineffective repairs or component replacements caused by misjudgment.

[0056] In embodiments of the present invention, by determining the fault level of communication failures, the severity of the impact of the failure can be assessed automatically and in a standardized manner, thereby enabling timely and safe responses when the impact of the failure is severe, and ensuring that the normal operation of the vehicle is not affected when the impact of the failure is minor.

[0057] In embodiments of the present invention, by implementing graded safety responses based on fault levels, the user experience is optimized while ensuring safe vehicle operation, thereby preventing a decline in user experience caused by taking emergency stopping strategies in the event of low-level faults.

[0058] In embodiments of the present invention, by comprehensively and hierarchically monitoring the physical layer status, protocol layer status, and application layer status of vehicle passage, a response can be made immediately when a fault occurs in the vehicle communication network, thereby improving the speed of safety response and reducing the number of missed faults.

[0059] Please see Figure 5 , Figure 5 This is a block diagram of a vehicle communication fault diagnosis device provided in one embodiment of the present invention. This device can be applied to... Figure 1 The implementation environment shown can also be applied to other exemplary implementation environments and specifically configured in other devices. This embodiment does not limit the implementation environment to which the device is applicable.

[0060] like Figure 5 As shown, this exemplary vehicle communication fault diagnosis device includes: The multi-level monitoring module 510 is used to monitor the physical layer status, protocol layer status, and application layer status of the vehicle's in-vehicle communication network, including: monitoring the physical layer signal integrity of the vehicle's in-vehicle communication network to obtain the physical layer status; monitoring the protocol layer communication timing of the in-vehicle communication network to obtain the protocol layer status; and verifying the rationality of the application layer data of the in-vehicle communication network to obtain the application layer status. The message record query module 520 is used to query the message sending and receiving records of the central gateway based on the communication event that triggered the fault state, under the condition that any one of the physical layer state, protocol layer state, and application layer state is in a fault state. The message record parsing module 530 is used to identify the vehicle controller that sends the communication message in the message transmission and reception record as the local controller and the vehicle controller that receives the communication message as the target controller. The fault location module 540 is used to determine whether the local controller or the target controller has a communication fault based on the response message record of the target controller in the message transmission and reception record. The fault classification module 550 is used to determine the fault level based on the type of controller with communication failure.

[0061] The multi-level monitoring module 510 monitors the physical layer signal integrity of the vehicle's in-vehicle communication network and obtains the physical layer status, including: monitoring the differential voltage of the vehicle's controller area network bus; if the fluctuation range of the differential voltage exceeds a preset range in a communication event, the physical layer status is determined to be a fault state; and / or monitoring the error frame rate of the vehicle's Ethernet; if the error frame rate exceeds a preset frame rate threshold in a communication event, the physical layer status is determined to be a fault state.

[0062] The multi-level monitoring module 510 monitors the protocol layer communication timing of the vehicle communication network and obtains the protocol layer status, including: monitoring the response time in the vehicle communication network. If the response time exceeds the dynamic response threshold in a communication event, the protocol layer status is determined to be a fault state. The dynamic response threshold is determined based on the current load and historical communication delay of the vehicle communication network.

[0063] The multi-level monitoring module 510 performs rationality verification on the application layer data of the vehicle communication network to obtain the application layer status, including: acquiring the application layer data transmitted through the vehicle communication network; verifying the rationality of the application layer data according to the data identifier of the application layer data; if the rationality verification of the application layer data fails in a communication event, the application layer status is obtained as a fault status.

[0064] The fault location module 540 determines whether there is a communication failure in the local controller or the target controller based on the response message record of the target controller in the message transmission and reception record. This includes: if no response message record of the target controller is found in the message transmission and reception record, it is determined that there is a communication failure in the target controller; if a response message record of the target controller is found in the message transmission and reception record, it is determined that there is a communication failure in the local controller.

[0065] The fault classification module 550 determines the fault level based on the type of controller with communication fault, including: if the controller with communication fault is a preset first type controller, the fault level is determined to be high; if the controller with communication fault is a preset second type controller, the fault level is determined to be medium; if the controller with communication fault is a preset third type controller, the fault level is determined to be low.

[0066] After determining the fault level based on the type of controller with communication failure, the fault classification module 550 further includes: if the fault level is high, controlling the vehicle to stop safely based on a preset safe parking strategy; if the fault level is medium, limiting the torque output; if the fault level is low, switching the vehicle's power supply to a backup power source.

[0067] Through the aforementioned device, joint monitoring of the physical layer, protocol layer, and application layer is achieved. Based on the full message record of the central gateway that triggers the communication event, it is determined whether the target controller is not responding or the local controller is receiving a fault. This allows for precise location of the root cause of the fault. Different fault levels are determined according to the fault type and the criticality of the controllers involved, and corresponding response measures are executed. This ensures that high-level faults are handled strictly and safely while avoiding overreaction to low-level faults.

[0068] It is understood that the vehicle communication fault diagnosis device and the vehicle communication fault diagnosis method provided in the above embodiments belong to the same concept. The specific operation of the vehicle communication fault diagnosis method has been described in detail in the above embodiments and will not be repeated here. In practical applications, the vehicle communication fault diagnosis device provided in the above embodiments can be assigned to different functional modules as needed. That is, the internal structure of the vehicle communication fault diagnosis device can be divided into different functional modules, and then all or part of the functions of the corresponding functional modules can be implemented by the vehicle communication fault diagnosis method described in the above embodiments. No specific limitation is imposed here. For example, the multi-level monitoring module 510 includes steps for executing step S210 and related steps, the message record query module 520 includes steps for executing step S220 and related steps, the message record parsing module 530 includes steps for executing step S230 and related steps, the fault location module 540 includes steps for executing step S240 and related steps, and the fault classification module 550 includes steps for executing step S250 and related steps.

[0069] Figure 6 This is a schematic diagram of a vehicle-mounted terminal provided in one embodiment of the present invention. It should be noted that... Figure 6 The computer system 600 of the vehicle terminal shown is merely an example and should not impose any limitation on the functionality and scope of use of the embodiments of the present invention.

[0070] like Figure 6 As shown, the computer system 600 includes a Central Processing Unit (CPU) 601, which can perform various appropriate actions and processes based on programs stored in Read-Only Memory (ROM) 602 or programs loaded from storage portion 608 into Random Access Memory (RAM) 603, such as performing the methods described in the above embodiments. The RAM 603 also stores various programs and data required for system operation. The CPU 601, ROM 602, and RAM 603 are interconnected via a bus 604. An Input / Output (I / O) interface 605 is also connected to the bus 604.

[0071] The following components are connected to I / O interface 605: an input section 606 including a keyboard, mouse, etc.; an output section 607 including a cathode ray tube (CRT), liquid crystal display (LCD), etc., and speakers, etc.; a storage section 608 including a hard disk, etc.; and a communication section 609 including a network interface card such as a LAN (Local Area Network) card, modem, etc. The communication section 609 performs communication processing via a network such as the Internet. A drive 610 is also connected to I / O interface 605 as needed. A removable medium 611, such as a disk, optical disk, magneto-optical disk, semiconductor memory, etc., is installed on drive 610 as needed so that computer programs read from it can be installed into storage section 608 as needed.

[0072] In particular, according to embodiments of the present invention, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments of the present invention include a computer program product comprising a computer program carried on a computer-readable medium, the computer program containing computer programs for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via communication section 609, and / or installed from removable medium 611. When the computer program is executed by central processing unit (CPU) 601, it performs various functions defined in the system of the present invention.

[0073] It should be noted that the computer-readable medium shown in the embodiments of the present invention can be a computer-readable signal medium or a computer-readable storage medium, or any combination thereof. A computer-readable storage medium can be, for example, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of a computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), flash memory, optical fiber, portable compact disc read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In the present invention, a computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, carrying a computer-readable computer program. Such propagated data signals may take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. Computer-readable signal media can also be any computer-readable medium other than computer-readable storage media, which can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device. The computer program contained on the computer-readable medium can be transmitted using any suitable medium, including but not limited to wireless, wired, etc., or any suitable combination thereof.

[0074] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of the present invention. Each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order. It should also be noted that each block in a block diagram or flowchart, and combinations of blocks in a block diagram or flowchart, may be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0075] The units described in the embodiments of the present invention can be implemented in software or hardware, and the described units can also be located in a processor. The names of these units do not necessarily limit the specific unit itself.

[0076] Another aspect of the present invention provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a computer's processor, causes the computer to perform the vehicle communication fault diagnosis method as described above. This computer-readable storage medium may be included in the vehicle-mounted terminal described in the above embodiments, or it may exist independently and not be installed in the vehicle-mounted terminal.

[0077] Another aspect of the present invention provides a computer program product or computer program including computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the vehicle communication fault diagnosis method provided in the various embodiments described above.

[0078] The above embodiments are merely illustrative of the principles and effects of the present invention and are not intended to limit the invention. Any person skilled in the art can modify or alter the above embodiments without departing from the spirit and scope of the present invention. Therefore, all equivalent modifications or alterations made by those skilled in the art without departing from the spirit and technical concept disclosed in the present invention should still be covered by the claims of the present invention.

Claims

1. A method for diagnosing vehicle communication faults, characterized in that, The method includes: Monitor the physical layer status, protocol layer status, and application layer status of the vehicle's in-vehicle communication network; If any of the physical layer state, the protocol layer state, and the application layer state is in a fault state, then the message transmission and reception records corresponding to the central gateway of the vehicle communication network are queried based on the communication event that triggered the fault state. In the message transmission and reception records, the vehicle controller that sends the communication message is the local controller, and the vehicle controller that receives the communication message is the target controller. Based on the response message record of the target controller in the message transmission and reception record, it is determined that either the local controller or the target controller has a communication failure. The fault level is determined based on the type of controller with the communication failure.

2. The vehicle communication fault diagnosis method according to claim 1, characterized in that, Based on the response message records of the target controller in the message transmission and reception log, determining whether there is a communication failure in the local controller communication or the target controller communication includes: If no response message record of the target controller is found in the message transmission and reception record, it is determined that the target controller has a communication failure; If the response message record of the target controller is found in the message transmission and reception record, it is determined that the local controller has a communication failure.

3. The vehicle communication fault diagnosis method according to claim 1, characterized in that, The fault level is determined based on the type of controller experiencing communication failure, including: If the controller type with communication failure is a preset first type controller, then the failure level is determined to be high. If the controller type with communication failure is a preset second type controller, then the failure level is determined to be medium. If the controller type with communication failure is a preset third type controller, then the failure level is determined to be low.

4. The vehicle communication fault diagnosis method according to claim 3, characterized in that, After determining the fault level based on the type of controller with communication failure, the following steps are also included: If the fault level is high, the vehicle is controlled to safely stop based on a preset safe parking strategy; If the fault level is medium, then the torque output of the vehicle is limited; If the fault level is low, the vehicle's power supply will be switched to the backup power supply.

5. The vehicle communication fault diagnosis method according to any one of claims 1-4, characterized in that, The physical layer status of the vehicle's onboard communication network includes: The differential voltage of the vehicle's controller area network bus is monitored. If the fluctuation range of the differential voltage exceeds a preset range during a communication event, the physical layer state is determined to be a fault state. And / or, The vehicle's Ethernet is monitored for error frame rate. If the error frame rate exceeds a preset frame rate threshold in a single communication event, the physical layer status is determined to be a fault state.

6. The vehicle communication fault diagnosis method according to any one of claims 1-4, characterized in that, The protocol layer status of the vehicle's onboard communication network includes: The response time in the vehicle communication network is monitored. If the response time exceeds the dynamic response threshold in a single communication event, the protocol layer status is determined to be a fault state. The dynamic response threshold is determined based on the current load and historical communication latency of the vehicle communication network.

7. The vehicle communication fault diagnosis method according to any one of claims 1-4, characterized in that, The application layer status of the vehicle's onboard communication network includes: Acquire the application layer data transmitted through the vehicle communication network; The application layer data is validated for reasonableness based on its data identifier. If the validation of the application layer data fails in a communication event, the application layer status is determined to be faulty.

8. A vehicle communication fault diagnosis device, characterized in that, The device includes: A multi-level monitoring module is used to monitor the physical layer status, protocol layer status, and application layer status of the vehicle's in-vehicle communication network. The message record query module is used to query the message sending and receiving records corresponding to the central gateway based on the communication event that triggered the fault state, under the condition that any one of the physical layer state, the protocol layer state, and the application layer state is in a fault state. The message record parsing module is used to identify the vehicle controller that sends the communication message in the message transmission and reception record as the local controller and the vehicle controller that receives the communication message as the target controller. The fault location module is used to determine whether the local controller or the target controller has a communication fault based on the response message record of the target controller in the message transmission and reception record. The fault classification module is used to determine the fault level based on the type of controller with communication failure.

9. A vehicle-mounted terminal, characterized in that, The vehicle-mounted terminal includes: One or more processors; A storage device for storing one or more programs, which, when executed by one or more processors, cause the vehicle terminal to implement the vehicle communication fault diagnosis method as described in any one of claims 1-7.

10. A vehicle, characterized in that, The vehicle is equipped with the vehicle-mounted terminal as described in claim 9.

Images