Vehicle diagnostic methods, electronic equipment and vehicles
By introducing vehicle configuration words to dynamically calculate diagnostic links and start mirroring at fault nodes, the adaptability and flexibility issues of the in-vehicle Ethernet mirroring scheme are solved, achieving efficient fault location and diagnostic processing.
Patent Information
- Application Number
- CN202611286437.5
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-08-24
- Publication Date
- 2026-11-17
AI Technical Summary
Current in-vehicle Ethernet routing mirroring solutions cannot adapt to different architectures, making platform reuse difficult. Furthermore, traditional mirroring solutions lack flexibility and precise traffic filtering, resulting in high bandwidth consumption, increased gateway load, and impact on normal communication and fault location efficiency.
By introducing vehicle configuration words as the basis for link selection, the target diagnostic link is dynamically calculated, the mirroring function is activated only at faulty nodes, and only fault-related messages are forwarded. A multi-layer filtering mechanism is adopted to ensure accurate data transmission.
It enables the same image software to be adapted to multiple vehicle models, eliminating the need for repeated development, reducing bus bandwidth and gateway load, and improving fault location efficiency and diagnostic accuracy.
Smart Images

Figure CN123113808A_ABST
Abstract
Description
Technical Field
[0001] This disclosure relates to the field of vehicle data processing technology, and in particular to a vehicle diagnostic method, electronic equipment, and vehicle. Background Technology
[0002] With the large-scale deployment of automotive Ethernet in intelligent connected vehicles, the vehicle network architecture is rapidly evolving towards high-speed interconnection and multi-domain centralized control. Against this backdrop, Ethernet routing mirroring has become a fundamental technical means for capturing bus messages, reproducing fault scenarios, and monitoring communication behavior, spanning the entire vehicle lifecycle.
[0003] Current in-vehicle Ethernet routing mirroring solutions cannot adapt to different architectures such as high-end and low-end models. Faced with new architectures, the mirroring solution needs to be redesigned, making platform reuse difficult. Summary of the Invention
[0004] In view of this, the purpose of this disclosure is to propose a vehicle diagnostic method, electronic device and vehicle, which dynamically calculates the target link from the fault node to the diagnostic device by introducing vehicle configuration words as the basis for link selection, so that the same set of image software can be adapted to multiple architectures without the need for redevelopment for each new vehicle model, thus realizing platform reuse.
[0005] To achieve the above objectives, a first aspect of this disclosure provides a vehicle diagnostic method, the method comprising:
[0006] In response to the detection of a fault in a vehicle node, the faulty node is used as the target node, and the vehicle mirroring function is activated. Obtain the vehicle configuration word, and determine the target diagnostic link based on the vehicle configuration word, wherein the target diagnostic link is the transmission link from the target node to the diagnostic device; The target message output by the target node is determined, and the target message is sent to the diagnostic device via the target diagnostic link. The diagnostic device is then used to perform diagnostic processing on the target message.
[0007] Based on the same inventive concept, a second aspect of this disclosure provides a vehicle diagnostic device, comprising: The function activation module is configured to activate the vehicle mirroring function in response to the detection of a fault in a vehicle node, using the faulty node as the target node. The data acquisition module is configured to acquire vehicle configuration words and determine the target diagnostic link based on the vehicle configuration words, wherein the target diagnostic link is a transmission link from the target node to the diagnostic device; The vehicle diagnostic module is configured to determine the target message output by the target node, send the target message to the diagnostic device via the target diagnostic link, and use the diagnostic device to perform diagnostic processing on the target message.
[0008] Based on the same inventive concept, a third aspect of this disclosure proposes an electronic device including a memory, a processor, and a computer program stored in the memory and executable by the processor, wherein the processor, when executing the computer program, implements the vehicle diagnostic method as described above.
[0009] Based on the same inventive concept, a fourth aspect of this disclosure provides a non-transitory computer-readable storage medium storing computer instructions for causing a computer to perform the vehicle diagnostic method as described above.
[0010] Based on the same inventive concept, a fifth aspect of this disclosure provides a vehicle including the vehicle diagnostic device described in the second aspect, the electronic device described in the third aspect, or the storage medium described in the fourth aspect.
[0011] As can be seen from the above, this disclosure proposes a vehicle diagnostic method, electronic device, and vehicle. In response to the detection of a fault in a vehicle node, the faulty node is selected as the target node, and a vehicle mirroring function is initiated. Using the occurrence of a fault as the core triggering event provides greater flexibility compared to passive, continuous mirroring. The vehicle configuration word is obtained, and a target diagnostic link is determined based on the vehicle configuration word. This target diagnostic link is the transmission link from the target node to the diagnostic device. By introducing the vehicle configuration word as the basis for link selection, the target diagnostic link from the faulty node to the diagnostic device is dynamically calculated, allowing the same mirroring software to adapt to multiple architectures without needing to redevelop for each new vehicle model, achieving platform reuse. The target message output by the target node is determined, and the target message is sent to the diagnostic device via the target diagnostic link. The diagnostic device then performs diagnostic processing on the target message. By initiating mirroring only when a vehicle node is faulty and only forwarding messages output by the faulty node, the bus bandwidth and gateway load are significantly reduced because only valid data related to the fault is captured. This protects normal business communication and ensures that the captured messages are few and precise, greatly improving fault location efficiency. Attached Figure Description
[0012] To more clearly illustrate the technical solutions in this disclosure or related technologies, the accompanying drawings used in the description of the embodiments or related technologies will be briefly introduced below. Obviously, the accompanying drawings described below are only embodiments of this disclosure. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.
[0013] Figure 1 This is a schematic diagram of a scenario according to an embodiment of the present disclosure; Figure 2 This is a flowchart of a vehicle diagnostic method according to an embodiment of the present disclosure; Figure 3 This is a first schematic diagram of message transmission in this embodiment; Figure 4 This is a second schematic diagram of message transmission in this embodiment; Figure 5 This is a third schematic diagram of message transmission in this embodiment; Figure 6 This is the fourth schematic diagram of message transmission in this embodiment; Figure 7 This is a schematic flowchart of a vehicle diagnostic method according to another embodiment of the present disclosure; Figure 8 This is a structural block diagram of a vehicle diagnostic device according to an embodiment of the present disclosure; Figure 9 This is a schematic diagram of the structure of an electronic device according to an embodiment of the present disclosure. Detailed Implementation
[0014] To make the objectives, technical solutions, and advantages of this disclosure clearer, the following detailed description is provided in conjunction with specific embodiments and the accompanying drawings.
[0015] It should be noted that, unless otherwise defined, the technical or scientific terms used in the embodiments of this disclosure should have the ordinary meaning understood by one of ordinary skill in the art to which this disclosure pertains. The terms "first," "second," and similar terms used in the embodiments of this disclosure do not indicate any order, quantity, or importance, but are merely used to distinguish different components. Terms such as "comprising" or "including" mean that the element or object preceding the word encompasses the elements or objects listed following the word and their equivalents, without excluding other elements or objects. Terms such as "connected" or "linked" are not limited to physical or mechanical connections, but can include electrical connections, whether direct or indirect. Terms such as "upper," "lower," "left," and "right" are used only to indicate relative positional relationships; when the absolute position of the described object changes, the relative positional relationship may also change accordingly.
[0016] The following are definitions of terms used in this disclosure: ECU: Electronic Control Unit (ECU) is the core brain of an automotive electronic system. It is responsible for receiving various sensor signals, executing control algorithms, and driving actuators to achieve key functions such as engine management, transmission control, and anti-lock braking.
[0017] ZCU: The Zone Control Unit (ZCU) is the core control node at the vehicle-mounted regional level. Its primary responsibility is not traditional power distribution and actuator driving, but rather to act as the network data hub within the region. It is specifically responsible for efficiently routing and forwarding Ethernet and CAN messages between different communication protocols, thereby realizing the aggregation and distribution of signals from various sensors, actuators, and sub-nodes within the region, significantly reducing the communication load on the central computing platform and improving the real-time performance of data transmission.
[0018] FR: Forward Radar (FR) usually refers to millimeter-wave radar installed behind the front bumper or grille of a vehicle, which uses high-frequency electromagnetic waves to detect the distance, relative speed and angle of objects in front.
[0019] ADC: The vehicle diagnostic console (ADC) is a dedicated hardware device or software platform that communicates with the vehicle's Controller Area Network (CAN) and various electronic control units (ECUs) through the vehicle's standard diagnostic interface (such as OBDI), acting as an intelligent interaction hub between technicians or engineers and the vehicle's underlying electronic systems.
[0020] HUT: The Host Under Test (HUT) is a key gateway node in the vehicle communication test environment, undertaking core routing and mirroring forwarding functions. It can accurately copy and forward the data flow on a specified port or link in the vehicle mirror link to the analysis device, backup node, or diagnostic interface, while ensuring the correctness of data flow and time synchronization accuracy. It is an indispensable core middleware for vehicle network debugging, fault injection, and data monitoring.
[0021] OBD: On-Board Diagnostics (OBD) is a self-diagnostic and monitoring system built into the vehicle's electronic control unit. It continuously monitors the operating status of the engine, emission system, sensors, and actuators. Once a fault is detected, it stores the corresponding diagnostic fault code (DTC) and illuminates the fault indicator light on the instrument panel.
[0022] TBOX: Telematics Box (TBOX) is an in-vehicle communication gateway that connects the vehicle to cloud services. It has a built-in 4G / 5G cellular module, GNSS positioning unit and encryption chip. It can collect vehicle status data in real time and upload it to the car manufacturer's cloud platform, while also receiving remote commands issued by the user's mobile APP.
[0023] PDC: Parking Distance Control (PDC) works by using ultrasonic sensors mounted on the vehicle's bumper. These sensors continuously emit ultrasonic signals, and when the signals hit an obstacle and reflect back, the system calculates the time difference between the signal transmission and reception to determine the distance between the obstacle and the vehicle.
[0024] With the large-scale deployment of automotive Ethernet in intelligent connected vehicles, the vehicle network architecture is rapidly evolving towards high-speed interconnection and centralized multi-domain control. Internal vehicle nodes such as domain controllers, gateways, actuators, and sensors commonly utilize Ethernet for high-bandwidth interconnection, supporting critical scenarios such as vehicle testing, production line inspection, after-sales diagnostics, and remote data acquisition. Against this backdrop, Ethernet routing mirroring has become a fundamental technical means for capturing bus messages, reproducing fault scenarios, and monitoring communication behavior, spanning the entire vehicle lifecycle.
[0025] In the process of vehicle Ethernet testing and diagnostics, the mirroring function undertakes several core tasks, including cross-segment and cross-domain controller packet pass-through and capture, realizing unified collection of multi-node communication data; end-to-end communication link integrity verification on the production line, ensuring the network connection quality of vehicles off the production line; diagnostic packet routing between the diagnostic instrument and vehicle gateways and domain controllers, supporting fault code reading and online calibration; and retrospective analysis of abnormal packets and fault communication data, assisting in problem localization and regression verification. These application scenarios place high demands on the flexibility, coverage, and performance of the mirroring solution.
[0026] Current automotive Ethernet routing mirroring generally adopts a single-layer, fixed-link design, supporting only unidirectional fixed paths, such as the path from external diagnostic equipment to the tested host to the diagnostic port. The link layer and forwarding nodes are not adjustable. This rigid architecture reveals significant limitations in adaptability when facing complex deployments of current multi-domain controller architectures, such as a central computing platform coupled with a regional controller (ZCU). On one hand, it cannot be compatible with the differentiated network topologies between high- and low-end vehicle models, exhibiting weak vehicle model adaptability. On the other hand, new mirroring solutions must be developed for new architectures, lacking evolutionary flexibility and resulting in high repetitive development costs. Furthermore, cross-project and cross-platform migration is difficult, and platform reusability is poor, making it difficult to effectively amortize development and adaptation investments.
[0027] The limited range of mirroring triggering methods further exacerbates the aforementioned problems. Existing solutions rely heavily on a limited number of triggering methods, making them unsuitable for traditional diagnostic devices that only support CAN triggering. This hinders the flexible start-up or shutdown of mirroring in dynamic testing environments such as production lines and test benches, and also fails to meet the needs of multi-mode, multi-channel diagnostic triggering, thus limiting the automation and parallelization of the diagnostic process. This limitation at the triggering level, along with the rigidity at the architectural level, constitutes the two major shortcomings of current mirroring solutions.
[0028] More importantly, traditional mirroring solutions often employ a full-volume pass-through mode, lacking a precise traffic filtering mechanism. This results in a large number of irrelevant packets, broadcast packets, and non-target data being forwarded simultaneously. This triggers a series of negative chain reactions: Ethernet bandwidth is excessively consumed, crowding out normal communication traffic; the load on gateways and domain controllers increases significantly, affecting the real-time performance of critical control tasks; normal vehicle business communication is interfered with, potentially introducing additional latency or packet loss risks; packet capture results have extremely high redundancy, with massive amounts of invalid data overwhelming critical information, which is extremely detrimental to rapid fault location. Furthermore, the lack of optimization strategies in multi-level routing scenarios severely limits scalability, making it difficult to support more complex network cascading requirements.
[0029] In summary, current in-vehicle Ethernet mirroring solutions have significant shortcomings in terms of architectural flexibility, trigger flexibility, and traffic management capabilities, and are no longer able to meet the testing and diagnostic needs of the continuously evolving intelligent connected vehicles.
[0030] To address or partially address the aforementioned issues, this disclosure proposes a vehicle diagnostic method. By introducing vehicle configuration words as the basis for link selection, the target diagnostic link from the faulty node to the diagnostic device is dynamically calculated. This allows the same image software to adapt to multiple architectures without requiring redevelopment for each new vehicle model, achieving platform reuse. Furthermore, by only activating the image when a vehicle node is faulty and only forwarding packets output by that faulty node, bus bandwidth and gateway load are significantly reduced because only valid data related to the fault is captured. This protects normal business communication while ensuring fewer and more precise captured packets, greatly improving fault location efficiency.
[0031] To make the objectives, technical solutions, and advantages of the present invention clearer, specific embodiments will be described below in conjunction with the accompanying drawings.
[0032] refer to Figure 1 , Figure 1 A schematic diagram of a scenario provided according to an embodiment of this application is shown, in which the devices involved include a controller 101 and a diagnostic device 102.
[0033] In this process, controller 101 detects a fault in the target node and initiates the vehicle mirroring function. It obtains the vehicle configuration word and determines the target diagnostic link based on it. This target diagnostic link is the transmission link from the target node to the diagnostic device. It then determines the target message output by the target node and sends it to the diagnostic device via the target diagnostic link. The diagnostic device 102 then performs diagnostic processing on the target message.
[0034] The above scheme introduces vehicle configuration words as the basis for link selection, dynamically calculating the target diagnostic link from the faulty node to the diagnostic device. This allows the same image software to adapt to multiple architectures without needing to be redeveloped for each new vehicle model, achieving platform reuse. Furthermore, by only activating the image when a vehicle node is faulty and only forwarding messages from that faulty node, bus bandwidth and gateway load are significantly reduced because only valid data related to the fault is captured. This protects normal business communication while ensuring fewer and more precise captured messages, greatly improving fault location efficiency.
[0035] refer to Figure 2 , Figure 2 This diagram illustrates a flowchart of the vehicle diagnostic method in this embodiment, the method comprising: Step 101: In response to the detection of a fault in a vehicle node, the faulty node is used as the target node, and the vehicle mirroring function is started.
[0036] In practice, each node in the vehicle is detected. In response to the detection of a fault in a vehicle node, the faulty node is used as the target node, and the vehicle mirroring function is then activated.
[0037] In this embodiment, the vehicle node refers to each module in the vehicle and its subordinate nodes. It is a collection of electronic control units deployed in the vehicle Ethernet, with independent network communication capabilities and addressable, and is the message source and routing starting point of the diagnostic mirroring function.
[0038] Specifically, the vehicle node includes a root node and subordinate edge nodes. The root node refers to a high-computing-power unit responsible for central computing, network communication, or regional control, such as an ADC, TBOX, or ZCU. The subordinate edge nodes refer to subordinate units mounted below the main control node, performing specific physical functions or sensing tasks, including various intelligent sensors, drive-by-wire actuators, and sub-gateways. Intelligent sensors include cameras, LiDAR, and millimeter-wave radar, while drive-by-wire actuators include steering, braking, and suspension controllers.
[0039] In this embodiment, the root node is typically located in the upper or backbone layer of the network topology, possessing multi-port routing and protocol conversion capabilities, and serves as the entry point for the entire diagnostic link. Downlink edge nodes are typically located at the edge layer of the network topology, interconnected with the upper-layer domain controller via Ethernet links; the raw data or status messages they generate are the core targets for troubleshooting.
[0040] In this embodiment, the vehicle mirroring function is a technical means to completely copy the communication data of a specified port or link in the vehicle network and forward it to the monitoring port. Its core function is to provide a parallel real-time data copy for diagnostic equipment without interrupting or interfering with the original network communication of the vehicle, thereby realizing non-intrusive monitoring of the vehicle's Ethernet communication status. Based on this function, external diagnostic equipment can quickly obtain the packet data of the vehicle's target network segment, and then perform network routing anomaly location analysis.
[0041] Step 102: Obtain the vehicle configuration word and determine the target diagnostic link based on the vehicle configuration word, wherein the target diagnostic link is the transmission link from the target node to the diagnostic device.
[0042] In practice, a vehicle configuration word is obtained, which carries differentiated information such as vehicle model, network topology, and number of domain controllers. A target diagnostic link is determined based on the vehicle configuration word, whereby the target diagnostic link is the transmission link of messages from the target node to the diagnostic device.
[0043] Step 103: Determine the target message output by the target node, send the target message to the diagnostic device via the target diagnostic link, and use the diagnostic device to perform diagnostic processing on the target message.
[0044] In specific implementation, the target message output by the target node is determined, and the target message is sent from the target node to the diagnostic device along the target diagnostic link. Then, after receiving the target message, the diagnostic device performs diagnostic processing on the target message.
[0045] For example, the target node is the FR node, and the target diagnostic link is from the FR node to the ADC node, to the HUT node, to the ZCU node, and to the OBD node. Therefore, the target message output by the FR node passes sequentially from the FR node through the ADC node, the HUT node, and the ZCU node, and finally reaches the OBD node, and is output from the OBD port to the diagnostic device.
[0046] In this embodiment, after receiving the target message, the diagnostic device first parses and verifies the message header according to the protocol specifications to confirm that its encapsulation format is correct and that it is a valid diagnostic message. Then, it establishes a connection and activates the route via a socket, and after security authentication, switches the socket to a registered state. Based on this, the diagnostic device parses the message, extracts the service identifier and parameters, and verifies whether the message format and length conform to the specifications. Afterwards, it calls the corresponding diagnostic service processing logic, such as reading fault codes (DTCs), data reading, input / output control, secure access, or ECU remapping, etc. After completing the diagnostic processing, it generates a positive or negative response message and sends the response message back to the target node or directly to the diagnostic instrument through the established diagnostic channel, thereby completing the diagnostic interaction.
[0047] The above scheme, in response to the detection of a fault in a vehicle node, designates the faulty node as the target node and initiates the vehicle mirroring function. Using the occurrence of a fault as the core trigger event provides greater flexibility compared to passive, continuous mirroring. The vehicle configuration word is obtained, and the target diagnostic link is determined based on this word. This target diagnostic link is the transmission link from the target node to the diagnostic device. By introducing the vehicle configuration word as the basis for link selection, the target diagnostic link from the faulty node to the diagnostic device is dynamically calculated, allowing the same mirroring software to adapt to multiple architectures without needing to redevelop for each new vehicle model, achieving platform reuse. The target message output by the target node is determined, and the target message is sent to the diagnostic device via the target diagnostic link, where the diagnostic device performs diagnostic processing on the target message. By initiating mirroring only when a vehicle node is faulty and only forwarding messages output by the faulty node, bus bandwidth and gateway load are significantly reduced because only valid data related to the fault is captured. This protects normal business communication while ensuring fewer and more precise captured messages, greatly improving fault location efficiency.
[0048] In some embodiments, when determining the target diagnostic link based on the vehicle configuration word, a corresponding vehicle network topology can be determined based on the vehicle configuration word, and then the target diagnostic link can be determined from the vehicle network topology based on the target node. That is, determining the target diagnostic link based on the vehicle configuration word in step 102 specifically includes: Step 1021: Determine the target topology graph corresponding to the vehicle configuration word based on the vehicle configuration word, wherein the target topology graph contains the connection relationships of all nodes in the vehicle; Step 1022: Determine the target diagnostic link based on the target node and the target topology map.
[0049] In specific implementation, the database is searched according to the vehicle configuration word to determine the target topology map corresponding to the vehicle configuration word. The target topology map is the network topology of the vehicle corresponding to the vehicle configuration word, and the target topology map contains the connection relationship of all nodes in the vehicle.
[0050] By using the target topology graph, the logic of mirror routing is decoupled from the physical hardware. When the vehicle model is changed or vehicle nodes are added or removed, only the configuration words and network topology graph need to be updated, without rewriting the routing and forwarding kernel code. This allows the same mirror middleware to be directly adapted to multiple vehicle platforms, thereby reducing related development costs.
[0051] After determining the target topology, the target diagnostic link is determined based on the target node and the target topology. Specifically, the link originating from the target node and ending at the diagnostic device is selected as the target diagnostic link. By determining the target topology, the determined target diagnostic link is guaranteed to be physically reachable and logically correct. In multi-level routing scenarios, it can automatically avoid disconnected branches and select the path with the fewest hops or lightest load, avoiding the problem of traditional solutions failing to obtain target node packets and thus failing to diagnose due to fixed links.
[0052] The above scheme determines the corresponding network topology based on vehicle configuration words and calculates the target diagnostic link from it based on the target node. By abstracting the differences in physical hardware into a software-defined graphical model, hardware and software decoupling is achieved. This allows the same set of image code to be adapted to multiple vehicle models without repeated development. Furthermore, graph theory algorithms can automatically avoid disconnected branches and select the optimal or specified path from a global perspective, strictly limiting the forwarding of fault messages to the calculated links. This fundamentally eliminates broadcast flooding and irrelevant traffic interference, significantly saving bandwidth and reducing gateway load. At the same time, the transparency of the link selection process greatly enhances the system's observability, providing low-cost, highly reliable, and easy-to-maintain flexible adaptation capabilities for production lines, after-sales service, and remote diagnostic scenarios.
[0053] In some embodiments, because the target node outputs a large number of packets, mirroring and forwarding all of them would result in significant network resource consumption. Therefore, it is necessary to filter the initial packets output by the target node, obtain the target packets, and then send only the target packets to the diagnostic device. Specifically, step 103, which involves determining the target packets output by the target node and sending them to the diagnostic device via the target diagnostic link, includes: Step 1031: Receive the initial message output by the target node, filter the initial message to obtain the target message; Step 1032: Determine the node connection order corresponding to the target diagnostic link, and send the target message from the target node to the diagnostic device according to the node connection order.
[0054] In practice, an initial message output by the target node is received, wherein the initial message is the raw data stream sent by the target node. The initial message is filtered based on preset rules to obtain the target message.
[0055] Determine the node connection order corresponding to the target diagnostic link, and send the target message from the target node to the diagnostic device according to the node connection order, that is, forward the target message from the target node to the diagnostic device along the specified path.
[0056] For example, such as Figure 3 As shown, Figure 3 This is the first schematic diagram of message transmission in this embodiment. The target diagnostic link is from TBOX to ZCU to OBD, where TBOX is the target node and ZCU is the mirror destination switch. That is, the initial message output by TBOX starts from TBOX, is filtered by ZCU to obtain the target message, and the target message is output from the OBD port to the diagnostic device.
[0057] Another example, such as Figure 4 As shown, Figure 4 This is a second schematic diagram of message transmission in this embodiment. The target diagnostic link is from ILD_F to ADC to ZCU to OBD, where ILD_F is the target node, ADC is the mirror source switch, and ZCU is the mirror destination switch. That is, the initial message output from ILD_F starts from ILD_F, is filtered by ADC and ZCU to obtain the target message, and the target message is output from the OBD port to the diagnostic device.
[0058] Another example, such as Figure 5 As shown, Figure 5 This is the third schematic diagram of message transmission in this embodiment. The target diagnostic link is from PDC to ADC to TBOX to HUT to ZCU to OBD. PDC is the target node, ADC is the mirror source switch, TBOX is the first mirror intermediate switch, HUT is the second mirror intermediate switch, and ZCU is the mirror destination switch. That is, the initial message output by PDC starts from PDC, is filtered by ADC, TBOX, HUT, and ZCU to obtain the target message, and the target message is output from the OBD port to the diagnostic device.
[0059] In this embodiment, if the target diagnostic link contains multiple nodes, filtering can be performed at each node in the target diagnostic link when filtering the initial packet. After obtaining the final target packet, it is sent to the diagnostic device. Meanwhile, the filtered packets are output from other ports and do not enter the diagnostic forwarding queue.
[0060] For example, such as Figure 6 As shown, Figure 6This is the fourth schematic diagram of message transmission in this embodiment. The target diagnostic link is FR to ADC to HUT to ZCU to OBD, where FR is the target node, ADC is the mirror source switch, HUT is the mirror intermediate switch, and ZCU is the mirror destination switch. After receiving the initial message output by FR, the ADC filters it to obtain the first message, such as... Figure 6 As shown by the black dashed line, the first message is forwarded to HUT, as follows. Figure 6 As shown by the solid black line in the middle. Filtered packets are output from other ports, such as... Figure 6 As shown by the solid gray line. After receiving the first message, the HUT filters it to obtain the second message and forwards it to the ZCU. After receiving the second message, the ZCU filters it to obtain the third message and forwards it to the OBD. The third message is the target message, which is then output to the diagnostic device through the OBD port.
[0061] Understandably, the filtered packets are not physically deleted, but rather they are not copied to the diagnostic port and are still forwarded from other service ports according to the normal routing table to ensure that basic communication is not interrupted.
[0062] By forwarding only the target packets, the above solution frees up Ethernet bandwidth and significantly reduces the CPU load on routing and forwarding for gateways and domain controllers. Simultaneously, it prevents the uncontrolled replication of unprocessed raw traffic, thus avoiding time delays or packet loss interference from diagnostic operations on normal service control flows.
[0063] In some embodiments, when filtering the initial packets output by the target node, filtering is performed based on a three-layer rule validation. That is, the initial packets are filtered in step 1031 to obtain the target packets. Specifically, for each initial packet, the filtering process includes: Step 10311: Determine the target traffic direction, target virtual LAN tag, and target hardware address of the initial message; Step 10312: Obtain the preset traffic direction, preset LAN label, and preset address set. In response to the target traffic direction being the same as the preset traffic direction, the target LAN label being the same as the preset LAN label, and the target hardware address belonging to the preset address set, the initial packet is used as the target packet.
[0064] In specific implementation, the target traffic direction, target virtual LAN label, and target hardware address of the initial message are determined, and a preset traffic direction, preset LAN label, and preset address set are obtained.
[0065] It is understood that the preset traffic direction, preset LAN label, and preset address set are associated with the vehicle configuration word; that is, the preset traffic direction, preset LAN label, and preset address set corresponding to different vehicle configuration words can be the same or different. By flexibly adjusting based on the configuration word, it can adapt to different vehicle models' high and low configuration architectures and multi-domain controller topology changes without the need to redevelop image software, significantly improving platform reusability and adaptation efficiency for diverse testing scenarios such as production lines and test benches.
[0066] If the target traffic direction is the same as the preset traffic direction, the target virtual LAN label is the same as the preset LAN label, and the target hardware address belongs to the preset address set, then the initial packet is used as the target packet.
[0067] Specifically, the flow direction is used to define the transmission direction of packets on the switching node. The flow direction includes inbound, outbound, and bidirectional directions. Inbound refers to the direction in which packets flow from external nodes into the current switching device port, suitable for capturing uplink data sent by fault sources. Outbound refers to the direction in which packets flow from the current switching device port to external nodes, suitable for monitoring downlink responses to diagnostic commands or replies to specific control messages. Bidirectional directions cover both inbound and outbound directions, used in scenarios where a complete record of the request-response interaction process is required.
[0068] For example, in a TBOX failure scenario, if only abnormal messages sent from the TBOX to the ZCU are of interest, then inbound filtering is set up. All acknowledgment packets or configuration commands sent from the ZCU to the TBOX will be automatically excluded from the diagnostic forwarding queue, thereby ensuring that the messages received by the diagnostic device are consistent with the fault reporting direction and avoiding interference information introduced by direction confusion.
[0069] The Virtual Local Area Network (VLAN) tag is a specific field embedded in the Ethernet frame header used to identify the VLAN domain to which the packet belongs. In vehicular networks, the VLAN tag typically contains a 12-bit VLAN ID, with different IDs corresponding to different functional domains. For example, VLAN 100 can be designated as a dedicated diagnostic channel, VLAN 10 for the in-vehicle entertainment system, and VLAN 20 for chassis control signals. During packet filtering, switching nodes such as the ZCU determine whether a packet belongs to a network segment allowed to enter the diagnostic link by accurately matching the VLAN ID in the packet with the preset target VLAN tag.
[0070] For example, taking a TBOX failure scenario, if the preset target VLAN ID is 100, only packets carrying this tag can pass through the second-level filter and enter the OBD diagnostic tool. However, entertainment domain packets carrying VLAN 10 or control domain packets carrying VLAN 20, even if they originate from the same failed TBOX node, will be filtered out due to VLAN mismatch and will be output normally from other service ports.
[0071] The hardware address (source MAC address) is a 48-bit hardware identifier embedded in the network interface card (NIC) of the network device, used to uniquely identify the source node of a packet at the data link layer. In automotive Ethernet, each electronic control unit (ECU) with network communication capabilities has a unique MAC address, serving as its physical identity within the local area network. In the third-level matching of mirror filtering, switching nodes such as the ZCU (Zero Control Unit) manage the source address by establishing MAC address whitelists or blacklists.
[0072] Specifically, in whitelist mode, a packet is only considered a trusted source and marked as a target packet to enter the diagnostic link if its source MAC address belongs to a preset set of allowed addresses. Conversely, in blacklist mode, packets with source MAC addresses that match the blacklist are directly intercepted to prevent unknown or illegal nodes from impersonating fault sources and injecting into the diagnostic channel.
[0073] For example, taking the target diagnostic link as TBOX to ZCU to OBD, the TBOX's dedicated MAC address is pre-configured in the preset whitelist. Therefore, fault packets sent by TBOX can pass source MAC verification. At the same time, even if a camera node sends a packet carrying VLAN 100 in the inbound direction, the packet will be rejected from the diagnostic link because its MAC address is not in the whitelist, ensuring that every packet received by the diagnostic device is traceable and reliable.
[0074] Through the above scheme, traffic direction filtering ensures that the diagnostic link only carries packets related to the fault source, avoiding the mixing of reverse responses or irrelevant control commands. This compresses the forwarded data volume from a full flood to a fault-related subset, effectively freeing up Ethernet bandwidth and reducing the load on the domain controller. Secondly, precise matching of VLAN tags achieves logical isolation between diagnostic traffic and service traffic such as entertainment and vehicle control. Broadcast packets from different VLAN domains do not interfere with each other, ensuring both the real-time and deterministic nature of normal communication services and preventing the spread of abnormal broadcasts from faulty nodes during cross-domain forwarding. Finally, hardware address filtering fundamentally prevents interference data from unknown or illegal nodes from entering the diagnostic equipment, significantly improving the purity and reliability of fault field data.
[0075] In some embodiments, when a fault is detected in the target node, the diagnostic device sends a mirroring start command, which is then sent to the target node so that the target node can forward the initial message upon receiving the command. Specifically, step 101, in response to the detection of a fault in a vehicle node, designates the faulty node as the target node and starts the vehicle mirroring function, which includes: Step 1011: In response to the detection of a fault in a vehicle node, the diagnostic device sends a mirror start command with the faulty node as the target node. Step 1012: Determine the target instruction corresponding to the mirror start instruction, send the target instruction to the target node, and start the vehicle mirror function.
[0076] In practice, if a fault is detected in a vehicle node, the faulty node is used as the target node, and the diagnostic device sends a mirror startup command to ensure that the mirror function is only enabled when necessary, thus avoiding the unnecessary resource overhead caused by long-term operation.
[0077] The target instruction corresponding to the mirroring start command is determined, wherein the target instruction is an instruction adapted to the node message type of the target node. The target instruction is then sent to the target node to start the vehicle mirroring function.
[0078] Specifically, the process of determining the target instruction corresponding to the image boot instruction includes: Step 10121: Obtain the node message type corresponding to the target node and the actual message type corresponding to the image startup command; Step 10122: In response to the fact that the actual message type is the same as the node message type, the mirror startup instruction is used as the target instruction; or, Step 10123: In response to the difference between the actual message type and the node message type, the image startup instruction is format-converted to obtain a target instruction, wherein the message type of the target instruction is the node message type.
[0079] In specific implementation, the node message type corresponding to the target node and the actual message type corresponding to the image startup command are obtained. The node message type and the actual message type are either CAN or DoIP. CAN is a controller area network (CAN) employing a multi-master bus structure, allowing any node to actively send information to the network at any time. Bus arbitration is performed using message identifiers, with smaller identifier values indicating higher priority. DoIP is an IP-based diagnostic protocol that transmits unified diagnostic service data over an IP network.
[0080] The actual message type is compared with the node message type. If the actual message type is the same as the node message type, it means that the target node can directly receive and identify the image startup command, and then use the image startup command as the target command.
[0081] If the actual message type is different from the node message type, it means that the target node cannot directly receive and recognize the mirror startup command. In this case, the mirror startup command needs to be formatted to obtain a command that the target node can recognize, i.e., the target command. The message type of the target command is the same as the node message type.
[0082] In this embodiment, if the mirroring startup command is a DoIP command and the node message type is CAN, the gateway will strip the standard Ethernet header and extract the internal application layer UDS diagnostic request. Subsequently, the routing module will look up the routing table based on the target node address and hand the diagnostic request over to the transport layer CANTP for processing according to the standard protocol. For long messages with a payload exceeding 7 bytes, the transport layer CANTP will segment them into a first frame, a flow control frame, and consecutive frames before sending them to the target CAN node via the CAN interface.
[0083] In this embodiment, if the mirror startup command is a CAN command and the node message type is DoIP, the fragmented CAN frames are reassembled into a complete application layer UDS diagnostic message, and a DoIP header is re-encapsulated. Finally, the message is sent back to the diagnostic device via a TCP / IP connection. The DoIP header includes fields such as protocol version, payload type, and length.
[0084] In this embodiment, when performing format conversion, it is necessary to process the mapping between CAN ID and DoIP source and destination addresses, as well as the recalculation and byte order conversion of the CAN message length field and DoIP payload length, so as to ensure that the instructions are transmitted between the two heterogeneous networks without loss and accurately.
[0085] The above solution converts the mirroring startup command format when it cannot be directly recognized by the target node, enabling bidirectional translation between CAN and DoIP protocols. This completely breaks the traditional mirroring function's dependence on a single trigger protocol, allowing diagnostic equipment to seamlessly start the Ethernet node's mirroring function regardless of the bus interface it uses. This not only effectively protects existing CAN diagnostic equipment assets and eliminates protocol barriers between production lines and R&D scenarios, but also significantly reduces the manual configuration burden on test personnel. Furthermore, it provides crucial compatibility layer support for the smooth evolution of the vehicle network from a traditional bus to a pure Ethernet architecture, ultimately significantly improving the usability and deployment flexibility of the vehicle mirroring solution in actual diagnostic, testing, and after-sales scenarios.
[0086] In some embodiments, before performing mirror diagnostics, it is necessary to ensure that the vehicle speed is zero to avoid the problem of mirror traffic competing for bandwidth with critical driving traffic when performing diagnostics under driving conditions, which would increase the risk of vehicle driving failure. Specifically, step 101, in response to detecting a fault in a vehicle node, designates the faulty node as the target node and initiates the vehicle mirroring function, which includes: Step 101A: Obtain vehicle speed; Step 101B: In response to the vehicle speed being less than or equal to a preset speed threshold and a fault being detected in a vehicle node, the faulty node is used as the target node, and the vehicle mirroring function is activated.
[0087] In practice, the vehicle speed is acquired and compared with a preset speed threshold. In this embodiment, the preset speed threshold is zero. If the vehicle speed is greater than the preset speed threshold, it indicates that the vehicle is in motion. If the vehicle mirroring function is enabled at this time, the target node's target packets will be superimposed on the high-load real-time data stream for routing mirroring, which can easily trigger the switch buffer queue overflow, causing normal service packets to be passively dropped. Therefore, the vehicle mirroring function is not enabled when the vehicle speed is greater than the preset speed threshold.
[0088] If the vehicle speed is less than or equal to a preset speed threshold and a fault is detected in a vehicle node (indicating zero vehicle speed and a faulty node), the faulty node can be used as the target node to initiate vehicle mirroring. This ensures that mirroring operations are performed only during periods of network idle time. This avoids bandwidth contention between mirroring traffic and critical driving traffic, effectively maintaining low latency and high determinism of the vehicular network during operation and preventing secondary failures caused by network congestion.
[0089] By employing the above solution, in a static parking state with zero vehicle speed, and combining the node fault-triggered mirroring function, interference from mirrored traffic on critical communications for driving safety is fundamentally avoided, ensuring the real-time performance and integrity of chassis and power domain control commands. Simultaneously, the network load is low and packet characteristics are stable in a stationary vehicle environment, effectively filtering out noise variables such as speed and vibration during dynamic driving, significantly improving the signal-to-noise ratio and diagnostic accuracy of captured data, and preventing mirrored traffic from competing for bandwidth with normal services. This allows for accurate, efficient collection and reliable location of fault messages while ensuring the absolute safety of personnel and vehicles.
[0090] In some embodiments, the vehicle mirroring function can be disabled via a mirroring disable command, thereby restoring network traffic to its state before the vehicle mirroring function was enabled after the vehicle mirroring function is disabled. Specifically, after step 103, the following steps are also included: Step 10A: In response to receiving a mirroring shutdown command, the vehicle mirroring function is turned off; Step 10B: Obtain the actual network traffic and control the actual network traffic to decrease to a preset traffic threshold.
[0091] In practice, if a mirroring shutdown command is received, the vehicle mirroring function is turned off, the actual network traffic is obtained, and the actual network traffic is controlled to be reduced to a preset traffic threshold, wherein the preset traffic threshold is the network traffic value before the vehicle mirroring function is turned on.
[0092] By accurately restoring network traffic to the state before mirroring is enabled, the disturbances caused by diagnostic actions to the vehicle network are completely eliminated. The system will not experience state drift or logical anomalies due to the start and stop of diagnostic functions, ensuring the consistency of perception and decision-making of high-level autonomous driving or drive-by-wire actuators before and after diagnosis, and reducing the safety risks of malfunctions caused by network disturbances.
[0093] Simultaneously, after the mirroring shutdown command is executed, the gateway, domain controller, and switches immediately cease copying and forwarding the target packets. This instantly releases the significant bandwidth occupied by the diagnostics, and the CPU interrupt processing load drops significantly. This ensures that after the diagnostics are completed, critical vehicle control signals immediately return to the highest priority transmission channel, avoiding the risk of communication delays or jitter caused by mirroring residue.
[0094] By constructing a closed-loop management capability for mirror diagnostics, which enables on-demand activation and deactivation after use, the occupied bandwidth and computing resources are immediately released via commands after the diagnostic task is completed. This eliminates the continuous pollution of the bus environment by redundant messages, restoring network communication to a clean business mode. This not only ensures the real-time performance and functional safety level of critical control signals, but also simplifies production line and after-sales processes and reduces hardware power consumption. As a result, the mirror function is transformed from a traditional invasive interference operation into a minimally invasive diagnostic method that leaves no trace.
[0095] Based on the same inventive concept, another embodiment of this disclosure provides a vehicle diagnostic method, taking a three-node, first-level mirror model as an example. Figure 7 As shown, Figure 7 This is a schematic flowchart of a vehicle diagnostic method according to another embodiment of the present disclosure. Figure 7 In the diagram, the solid gray line represents the command issuance path. The solid black line represents the mirror data transmission path, i.e., the message transmission path of the in-vehicle nodes. The dashed black line represents the alternative transmission path for mirror data, i.e., the alternative transmission path for messages of the in-vehicle nodes. Specifically, the method includes: If a fault is detected in an in-vehicle node, the faulty in-vehicle node is designated as the target node, and the diagnostic device issues a mirror start command. After receiving the mirror start command, the DB module in the edge node determines the target topology based on the vehicle configuration words, and then determines the target diagnostic link based on the target node and the target topology.
[0096] The DB module in the edge node obtains the node message type corresponding to the target node and the actual message type corresponding to the image startup command. The DB module in the edge node determines whether the actual message type and the node message type are the same. If they are the same, the image startup command is used as the target command. If they are different, the image startup command is format-converted to obtain the target command, and the DB module in the edge node sends the target command to the target node. The message type of the target command is the same as the node message type.
[0097] After receiving the target instruction, the target node sends an initial message to the edge node. Upon receiving the initial message, the DA module in the edge node determines the target filtering rules based on the vehicle configuration word, filters the initial message according to the target filtering rules to obtain the target message, and then sends the target message to the diagnostic device.
[0098] In this embodiment, the target filtering rule is a three-layer combination of filtering based on traffic direction, virtual LAN tag, and hardware address, i.e., ACL filtering. Only necessary packets are mirrored, suppressing redundant traffic to the greatest extent and achieving low-intrusion mirroring in vehicle scenarios.
[0099] The above solution supports dynamic selection of high and low configuration domain control architectures, completely breaking the limitations of fixed links and achieving true platform-based reuse. Simultaneously, it overcomes the limitations of traditional CAN-triggered systems by adding DoIP triggering and supporting bidirectional conversion, comprehensively covering automotive diagnostic scenarios and adapting to more diagnostic devices and testing environments. The traffic minimization design significantly reduces network load without affecting the communication quality and real-time performance of critical services such as vehicle control, intelligent driving, and cockpit applications.
[0100] It should be noted that the method of this disclosure embodiment can be executed by a single device, such as a computer or server. The method of this embodiment can also be applied to a distributed scenario, where multiple devices cooperate to complete the task. In such a distributed scenario, one of these devices may execute only one or more steps of the method of this disclosure embodiment, and the multiple devices will interact with each other to complete the method described.
[0101] It should be noted that the above description describes some embodiments of this disclosure. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recorded in the claims can be performed in a different order than that shown in the above embodiments and still achieve the desired result. Furthermore, the processes depicted in the drawings do not necessarily require a specific or sequential order to achieve the desired result. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.
[0102] Based on the same inventive concept, corresponding to any of the above-described embodiments, this disclosure also provides a vehicle diagnostic device.
[0103] refer to Figure 8 , Figure 8 The vehicle diagnostic device of the embodiment includes: The function activation module 801 is configured to activate the vehicle mirroring function in response to detecting a fault in a vehicle node, using the faulty node as the target node. The data acquisition module 802 is configured to acquire vehicle configuration words and determine a target diagnostic link based on the vehicle configuration words, wherein the target diagnostic link is a transmission link from the target node to the diagnostic device; The vehicle diagnostic module 803 is configured to determine the target message output by the target node, send the target message to the diagnostic device via the target diagnostic link, and use the diagnostic device to perform diagnostic processing on the target message.
[0104] In some embodiments, the data acquisition module 802 is specifically configured as follows: Based on the vehicle configuration word, a target topology graph corresponding to the vehicle configuration word is determined, wherein the target topology graph contains the connection relationships of all nodes in the vehicle; The target diagnostic link is determined based on the target node and the target topology map.
[0105] In some embodiments, the vehicle diagnostic module 803 is specifically configured as follows: Receive the initial message output by the target node, filter the initial message to obtain the target message; Determine the node connection order corresponding to the target diagnostic link, and send the target message from the target node to the diagnostic device according to the node connection order.
[0106] In some embodiments, the data acquisition module 802 is specifically configured as follows: For each initial message: Determine the target traffic direction, target virtual LAN label, and target hardware address of the initial message; Obtain a preset traffic direction, a preset LAN label, and a preset address set. In response to the target traffic direction being the same as the preset traffic direction, the target LAN label being the same as the preset LAN label, and the target hardware address belonging to the preset address set, use the initial packet as the target packet.
[0107] In some embodiments, the function activation module 801 is specifically configured as follows: In response to the detection of a fault in a vehicle node, the diagnostic device sends a mirror start command, with the faulty node as the target node. The target instruction corresponding to the mirror start instruction is determined, and the target instruction is sent to the target node to start the vehicle mirror function.
[0108] In some embodiments, the function activation module 801 is specifically configured as follows: Obtain the node message type corresponding to the target node, and the actual message type corresponding to the image startup command; In response to the actual message type being the same as the node message type, the image startup command is used as the target command; or, In response to the difference between the actual message type and the node message type, the image startup command is format-converted to obtain a target command, wherein the message type of the target command is the node message type.
[0109] In some embodiments, the function activation module 801 is specifically configured as follows: Get vehicle speed; In response to the vehicle speed being less than or equal to a preset speed threshold and a fault being detected in a vehicle node, the faulty node is used as the target node, and the vehicle mirroring function is activated.
[0110] In some embodiments, the device further includes a function shutdown module, which is specifically configured to: In response to receiving a mirroring shutdown command, the vehicle mirroring function is disabled; Obtain actual network traffic and control the actual network traffic to decrease to a preset traffic threshold.
[0111] For ease of description, the above apparatus is described in terms of its functions, divided into various modules. Of course, in implementing this disclosure, the functions of each module can be implemented in one or more software and / or hardware.
[0112] The apparatus of the above embodiments is used to implement the corresponding vehicle diagnostic method in any of the foregoing embodiments, and has the beneficial effects of the corresponding method embodiments, which will not be repeated here.
[0113] Based on the same inventive concept, corresponding to the methods of any of the above embodiments, this disclosure also provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement the vehicle diagnostic method described in any of the above embodiments.
[0114] Figure 9This embodiment illustrates a more specific hardware structure of an electronic device. The device may include a processor 1010, a memory 1020, an input / output interface 1030, a communication interface 1040, and a bus 1050. The processor 1010, memory 1020, input / output interface 1030, and communication interface 1040 are interconnected internally via the bus 1050.
[0115] The processor 1010 can be implemented using a general-purpose CPU (Central Processing Unit), microprocessor, application-specific integrated circuit (ASIC), or one or more integrated circuits, and is used to execute relevant programs to implement the technical solutions provided in the embodiments of this specification.
[0116] The memory 1020 can be implemented in the form of ROM (Read Only Memory), RAM (Random Access Memory), static storage device, dynamic storage device, etc. The memory 1020 can store the operating system and other applications. When the technical solutions provided in the embodiments of this specification are implemented by software or firmware, the relevant program code is stored in the memory 1020 and is called and executed by the processor 1010.
[0117] The input / output interface 1030 is used to connect input / output modules to realize information input and output. Input / output modules can be configured as components within the device (not shown in the figure) or externally connected to the device to provide corresponding functions. Input devices may include keyboards, mice, touchscreens, microphones, various sensors, etc., while output devices may include displays, speakers, vibrators, indicator lights, etc.
[0118] The communication interface 1040 is used to connect a communication module (not shown in the figure) to enable communication between this device and other devices. The communication module can communicate via wired means (such as USB, Ethernet cable, etc.) or wireless means (such as mobile network, WIFI, Bluetooth, etc.).
[0119] Bus 1050 includes a pathway for transmitting information between various components of the device, such as processor 1010, memory 1020, input / output interface 1030, and communication interface 1040.
[0120] It should be noted that although the above-described device only shows the processor 1010, memory 1020, input / output interface 1030, communication interface 1040, and bus 1050, in specific implementations, the device may also include other components necessary for normal operation. Furthermore, those skilled in the art will understand that the above-described device may only include the components necessary for implementing the embodiments of this specification, and not necessarily all the components shown in the figures.
[0121] The electronic devices described above are used to implement the corresponding vehicle diagnostic methods in any of the foregoing embodiments and have the beneficial effects of the corresponding method embodiments, which will not be repeated here.
[0122] Based on the same inventive concept, corresponding to the methods of any of the above embodiments, this disclosure also provides a non-transitory computer-readable storage medium storing computer instructions for causing the computer to perform the vehicle diagnostic method as described in any of the above embodiments.
[0123] The computer-readable medium of this embodiment includes permanent and non-permanent, removable and non-removable media, and information storage can be implemented by any method or technology. Information can be computer-readable instructions, data structures, program modules, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic magnetic disk storage or other magnetic storage devices, or any other non-transfer medium that can be used to store information accessible by a computing device.
[0124] The computer instructions stored in the storage medium of the above embodiments are used to cause the computer to execute the vehicle diagnostic method as described in any of the above embodiments, and have the beneficial effects of the corresponding method embodiments, which will not be repeated here.
[0125] Based on the same inventive concept, corresponding to the methods of any of the above embodiments, this application also provides a vehicle, including the vehicle diagnostic device in the above embodiments, the electronic device in the above embodiments, and the computer-readable storage medium in the above embodiments, wherein the vehicle device implements the vehicle diagnostic method described in any of the above embodiments.
[0126] The vehicles described in the above embodiments are used to implement the vehicle diagnostic method described in any of the foregoing embodiments, and have the beneficial effects of the corresponding method embodiments, which will not be repeated here.
[0127] It is understood that before using the technical solutions of the various embodiments in this disclosure, users will be informed of the type, scope of use, and usage scenarios of the personal information involved in an appropriate manner, and user authorization will be obtained.
[0128] For example, upon receiving a user's active request, a prompt message is sent to the user to explicitly inform them that the requested operation will require the acquisition and use of the user's personal information. This allows the user to independently choose, based on the prompt message, whether to provide personal information to the software or hardware such as electronic devices, applications, servers, or storage media performing the operations of this disclosed technical solution.
[0129] As an optional but not limited implementation, in response to a user's active request, sending a prompt message to the user can be done via a pop-up window, where the prompt message can be presented in text format. Furthermore, the pop-up window can also include a selection control allowing the user to choose "agree" or "disagree" to provide personal information to the electronic device.
[0130] It is understood that the above notification and user authorization process are merely illustrative and do not constitute a limitation on the implementation of this disclosure. Other methods that comply with relevant laws and regulations may also be applied to the implementation of this disclosure.
[0131] Those skilled in the art should understand that the discussion of any of the above embodiments is merely exemplary and is not intended to imply that the scope of this disclosure (including the claims) is limited to these examples; within the framework of this disclosure, the technical features of the above embodiments or different embodiments can also be combined, the steps can be implemented in any order, and there are many other variations of different aspects of the embodiments of this disclosure as described above, which are not provided in detail for the sake of brevity.
[0132] Additionally, to simplify the description and discussion, and to avoid obscuring the embodiments of this disclosure, the provided drawings may or may not show well-known power / ground connections to integrated circuit (IC) chips and other components. Furthermore, the apparatus may be shown in block diagram form to avoid obscuring the embodiments of this disclosure, and this also takes into account the fact that the details of implementation of these block diagram apparatuses are highly dependent on the platform on which the embodiments of this disclosure will be implemented (i.e., these details should be fully understood by those skilled in the art). While specific details (e.g., circuits) have been set forth to describe exemplary embodiments of this disclosure, it will be apparent to those skilled in the art that the embodiments of this disclosure can be implemented without these specific details or with variations thereof. Therefore, these descriptions should be considered illustrative rather than restrictive.
[0133] Although this disclosure has been described in conjunction with specific embodiments thereof, many substitutions, modifications, and variations of these embodiments will be apparent to those skilled in the art from the foregoing description. For example, other memory architectures (e.g., dynamic RAM (DRAM)) may be used with the embodiments discussed.
[0134] This disclosure is intended to cover all such substitutions, modifications, and variations that fall within the broad scope of the appended claims. Therefore, any omissions, modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this disclosure should be included within the scope of protection of this disclosure.
Claims
1. A vehicle diagnostic method, characterized in that, include: In response to the detection of a fault in a vehicle node, the faulty node is used as the target node, and the vehicle mirroring function is activated. Obtain the vehicle configuration word, and determine the target diagnostic link based on the vehicle configuration word, wherein the target diagnostic link is the transmission link from the target node to the diagnostic device; The target message output by the target node is determined, and the target message is sent to the diagnostic device via the target diagnostic link. The diagnostic device is then used to perform diagnostic processing on the target message.
2. The method according to claim 1, characterized in that, The step of determining the target diagnostic link based on the vehicle configuration word includes: Based on the vehicle configuration word, a target topology graph corresponding to the vehicle configuration word is determined, wherein the target topology graph contains the connection relationships of all nodes in the vehicle; The target diagnostic link is determined based on the target node and the target topology map.
3. The method according to claim 1, characterized in that, The step of determining the target message output by the target node and sending the target message to the diagnostic device via the target diagnostic link includes: Receive the initial message output by the target node, filter the initial message to obtain the target message; Determine the node connection order corresponding to the target diagnostic link, and send the target message from the target node to the diagnostic device according to the node connection order.
4. The method according to claim 3, characterized in that, The filtering process of the initial message to obtain the target message includes: For each initial message: Determine the target traffic direction, target virtual LAN label, and target hardware address of the initial message; Obtain a preset traffic direction, a preset LAN label, and a preset address set. In response to the target traffic direction being the same as the preset traffic direction, the target LAN label being the same as the preset LAN label, and the target hardware address belonging to the preset address set, use the initial packet as the target packet.
5. The method according to claim 1, characterized in that, The step of responding to the detection of a fault in a vehicle node, using the faulty node as the target node, and activating the vehicle mirroring function includes: In response to the detection of a fault in a vehicle node, the diagnostic device sends a mirror start command, with the faulty node as the target node. The target instruction corresponding to the mirror start instruction is determined, and the target instruction is sent to the target node to start the vehicle mirror function.
6. The method according to claim 5, characterized in that, The step of determining the target instruction corresponding to the image boot instruction includes: Obtain the node message type corresponding to the target node, and the actual message type corresponding to the image startup command; In response to the actual message type being the same as the node message type, the image startup command is used as the target command; or, In response to the difference between the actual message type and the node message type, the image startup command is format-converted to obtain a target command, wherein the message type of the target command is the node message type.
7. The method according to claim 1, characterized in that, The step of responding to the detection of a fault in a vehicle node, using the faulty node as the target node, and activating the vehicle mirroring function includes: Get vehicle speed; In response to the vehicle speed being less than or equal to a preset speed threshold and a fault being detected in a vehicle node, the faulty node is used as the target node, and the vehicle mirroring function is activated.
8. The method according to claim 1, characterized in that, After performing diagnostic processing on the target message using the diagnostic device, the method further includes: In response to receiving a mirroring shutdown command, the vehicle mirroring function is disabled; Obtain actual network traffic and control the actual network traffic to decrease to a preset traffic threshold.
9. An electronic 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 program, implements the method as claimed in any one of claims 1 to 8.
10. A vehicle, characterized in that, Includes the electronic device as described in claim 9.
