Vehicle diagnosis communication system

Abstract

The invention relates to the technical field of vehicle communication, in particular to a vehicle diagnosis communication system. The system comprises an upper computer device which is provided with a diagnosis port, and the diagnosis port is in communication connection with a gateway; the gateway is used for establishing communication connection with the upper computer equipment and a vehicle end; the vehicle end comprises a plurality of electronic control units, and each electronic control unit is used for executing diagnosis operation according to the diagnosis instruction sent by the upper computer equipment through the gateway; wherein a first type of communication link and a second type of communication link are erected between the diagnosis port and the gateway; a first type of diagnostic communication link, a second type of diagnostic communication link and a third type of diagnostic communication link are set up between the gateway and each of the electronic control units. According to the invention, a plurality of diagnosis communication modes can be provided, and the adaptation flexibility for a plurality of different service requirements is improved.

Description

Technical Field

[0001] This application relates to the field of vehicle communication technology, and more particularly to a vehicle diagnostic communication system. Background Technology

[0002] With the development of intelligent connected vehicles, higher bandwidth vehicle communication technologies are gradually being introduced into the vehicle communication network. Currently, vehicle diagnostics is mainly based on the traditional CAN network, and the diagnostic methods are relatively simple, which is not flexible enough when facing a variety of different needs and diagnostic service scenarios. Summary of the Invention

[0003] To address the aforementioned issues, this application provides a vehicle diagnostic communication system that offers multiple diagnostic communication methods, thereby enhancing adaptability and flexibility in response to diverse service demands.

[0004] According to one aspect of an embodiment of this application, a vehicle diagnostic communication system is proposed, the system comprising: The host computer device is equipped with a diagnostic port, which establishes a communication connection with the gateway. Gateway, the gateway being used to establish communication connections with the host computer device and the vehicle terminal; On the vehicle side, it includes multiple electronic control units, each of which is used to perform diagnostic operations according to diagnostic instructions sent by the host computer device through the gateway; Specifically, a first type of communication link and a second type of communication link are established between the diagnostic port and the gateway; A first type of diagnostic communication link, a second type of diagnostic communication link, and a third type of diagnostic communication link are established between the gateway and each of the electronic control units.

[0005] In the above scheme, the first type is Ethernet communication, the second type is CAN communication, and the third type is CANFD communication.

[0006] In the above scheme, the network routing protocol between the gateway and the electronic control unit is determined by the network support type of the electronic control unit.

[0007] In the above scheme, the network route of the communication link between the diagnostic port and the gateway is determined by determining the network routing protocol between the gateway and the electronic control unit.

[0008] In the above scheme, if the network support type of the electronic control unit is CANFD diagnostic support, then the electronic control unit can respond to CAN diagnostic response messages and / or CANFD diagnostic response messages.

[0009] In the above scheme, the gateway and each of the electronic control units also communicate and interact via DoIP messages.

[0010] In the above scheme, if the electronic control unit sends a DoIP message to the gateway, the network route between the gateway and the diagnostic port of the host computer device is changed from gateway DoIP to DoIP route.

[0011] In the above scheme, if the electronic control unit sends a CANFD message to the gateway, the network route between the gateway and the diagnostic port of the host computer device is changed from the gateway DoIP route to the CANFD route.

[0012] In the above scheme, if the electronic control unit sends a CAN message to the gateway, the network route between the gateway and the diagnostic port of the host computer device is changed from the gateway DoIP route to the CAN route.

[0013] In the above scheme, the length of the CAN diagnostic response message is 8 bytes, and the length of the CANFD diagnostic response message is no more than 64 bytes.

[0014] The beneficial effects of this application are as follows: This application establishes a first type of communication link and a second type of communication link between the diagnostic port and the gateway, allowing the diagnostic port and the gateway to freely choose different types of communication links to achieve communication interaction. Simultaneously, by establishing a first type of diagnostic communication link, a second type of diagnostic communication link, and a third type of diagnostic communication link between the gateway and each of the electronic control units, each electronic control unit can flexibly select different types of diagnostic communication links, thereby solving the problem of insufficient flexibility in diagnostic services in the prior art. Attached Figure Description

[0015] Figure 1 This is an architecture diagram of the vehicle diagnostic communication system provided in the embodiments of this application; Figure 2 This is a schematic diagram of the vehicle diagnostic communication system provided in an embodiment of this application; Figure 3 This is a schematic diagram of the communication link of the vehicle diagnostic communication system provided in the embodiments of this application. Detailed Implementation

[0016] To enable those skilled in the art to better understand the solutions of this application, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0017] It should be noted that while some processes described in the specification, claims, and accompanying drawings include multiple steps appearing in a specific order, it should be clearly understood that these steps may not be performed in the order they appear herein, or may be performed in parallel. The step numbers are merely used to distinguish different steps and do not themselves represent any execution order. Furthermore, descriptions such as "first," "second," or "objective" in this document are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. "Multiple" in this document refers to at least two.

[0018] It is worth noting that in the specific embodiments of this application, data such as messages and diagnostic messages are involved. When the above embodiments of this application are applied to specific products or technologies, permission or consent from the target object is required, and the collection, use, and processing of related data must comply with relevant laws, regulations, and standards. For example, when an embodiment of this application needs to obtain data such as messages and diagnostic messages, separate permission or consent from the target object can be obtained through pop-up windows or redirection to a confirmation page. After obtaining the separate permission or consent from the target object, the necessary data such as messages and diagnostic messages for the normal operation of the embodiment of this application can then be obtained.

[0019] The following provides a detailed description of the specific implementation methods of the embodiments of this application: Please see Figure 1 , Figure 1 This is an architecture diagram of the vehicle diagnostic communication system provided in this application embodiment. The vehicle diagnostic communication system provided in this application embodiment includes: The host computer device is equipped with a diagnostic port, which establishes a communication connection with the gateway. Gateway, the gateway being used to establish communication connections with the host computer device and the vehicle terminal; On the vehicle side, it includes multiple electronic control units, each of which is used to perform diagnostic operations according to diagnostic instructions sent by the host computer device through the gateway; Specifically, a first type of communication link and a second type of communication link are established between the diagnostic port and the gateway; A first type of diagnostic communication link, a second type of diagnostic communication link, and a third type of diagnostic communication link are established between the gateway and each of the electronic control units.

[0020] Specifically, a first type of communication link and a second type of communication link are established between the diagnostic port and the gateway. The diagnostic port and the gateway can freely choose different types of communication links to achieve communication interaction. Simultaneously, a first type of diagnostic communication link, a second type of diagnostic communication link, and a third type of diagnostic communication link are established between the gateway and each of the electronic control units. This allows each electronic control unit to flexibly select different types of diagnostic communication links, thereby solving the problem of insufficient flexibility in diagnostic services in the prior art.

[0021] See also Figure 2 As shown, Figure 2 This is a detailed architecture diagram of the vehicle diagnostic communication system. Figure 2 The host computer diagnostic device mentioned in this application is the host computer, which includes a diagnostic port. The diagnostic port establishes a communication connection with the vehicle-side OBD diagnostic communication and then establishes a communication connection with the gateway. The gateway can establish communication connections with multiple electronic control units, including DoIP routing, CAN routing and CANFD routing.

[0022] In vehicle off-line inspection and after-sales vehicle diagnostic and repair scenarios, Ethernet communication is used between the diagnostic port and the gateway. The off-line inspection equipment and after-sales diagnostic equipment develop programs to send and receive DoIP commands and send DoIP diagnostic requests. The central gateway realizes message conversion between Ethernet, CANFD and CAN protocols, routes to each electronic control unit, each electronic control unit replies with a diagnostic response, and the gateway routes to the off-line inspection equipment and after-sales diagnostic equipment to realize whole vehicle diagnostic communication. 1. DoIP is used between the diagnostic port and the gateway; 2. The program for offline testing equipment and after-sales diagnostic equipment implements the sending and receiving of DoIP messages; 3. The gateway routes DoIP as DoIP, CAN diagnostic messages, and CANFD diagnostic messages; 4. Determine the diagnostic communication scheme for dozens of electronic control units in the vehicle, and design the vehicle-wide diagnostic route: like Figure 3 As shown, Figure 3 Here is another architecture diagram of the vehicle diagnostic communication system. If the electronic controller unit 1 supports DoIP, then the gateway routing will realize DoIP to DoIP, set the DoIP communication ID of the electronic control unit, and the gateway will route to the target electronic control unit accordingly. If the electronic controller unit 2 supports Do CAN, the gateway routes the DoIP to CAN diagnostic message, sets the Do CAN communication ID and specific common CAN of the electronic control unit, and the gateway routes to the target electronic control unit accordingly. If electronic controller unit 3 supports Do CANFD, the gateway routing will convert DoIP to CANFD diagnostic messages. For electronic control units that support CANFD diagnostic communication, CAN diagnostic compatibility will also be implemented. That is, when an electronic control unit receives a CAN diagnostic request message, it will reply with a CAN diagnostic response message. When an electronic control unit receives a CANFD diagnostic request message, it will reply with a CANFD diagnostic response message. The diagnostic communication ID and specific common CAN of the electronic control unit will be set, and the gateway will route to the target electronic control unit accordingly. The CAN diagnostic communication ID and CANFD diagnostic communication ID of the electronic control unit are shared. 5. Each electronic control unit receives a diagnostic request and responds with a diagnostic response; 6. The gateway converts DoIP, CAN diagnostic messages, and CANFD diagnostic messages into DoIP messages and routes them to offline testing equipment and after-sales diagnostic equipment.

[0023] For the traditional CAN network of the vehicle communication network, there are two options: First, the in-vehicle electronic control unit retains the CAN diagnostic solution, and the gateway implements the DoIP and DoCAN message conversion. Second, the gateway retains the traditional CAN diagnostic routing, and the gateway implements the CAN-to-CAN conversion of the request message, routes it to the target electronic control unit, the electronic control unit replies with a diagnostic response message, and the gateway then forwards the CAN message to the host computer device, while also being compatible with the current scenario where the host computer device sends CAN diagnostic messages.

[0024] The diagnostic message includes UDS diagnostic services including, but not limited to, services 10, 11, 14, 19, 27, 22, 28, 2E, 2F, 31, 34, 36, 37, 38, 3E, and 85. The length of the CAN diagnostic message DLC is 8 bytes, and the maximum length of the CANFD diagnostic message DLC is 64 bytes. The length of the CANFD message can vary depending on the actual data transmitted, and can be adaptively 8, 12, 16, 20, 24, 32, 48 or 64 bytes. For electronic control units that support CANFD diagnostics, the APP, Boot, and all UDS services uniformly support CANFD diagnostics and are also compatible with CAN diagnostics. When a CAN diagnostic request message is received, a CAN diagnostic response message is replied to; when a CANFD diagnostic request message is received, a CANFD diagnostic response message is replied to.

[0025] The electronic control unit CANFD is compatible with CAN diagnostics and supports node switching based on the end of the UDS service. For example, if the 10 service of the CANFD message responds normally, the 22 service of the subsequent CAN message can still respond normally. It adapts to the traditional CAN network of the vehicle communication network, and realizes CAN and CANFD diagnostic compatibility for different controllers in the vehicle.

[0026] This application designs a diagnostic system integrating multiple communication technologies such as CAN, CANFD, and Ethernet networks. An Ethernet communication link is established between the diagnostic port and the gateway. Each electronic control unit (ECU) has a diagnostic communication link with the central gateway, using CAN, CANFD, and Ethernet protocols respectively. The central gateway performs signal and message conversion between Ethernet, CANFD, and the CAN protocol. It determines the diagnostic routing scheme for the CAN and CANFD diagnostic communication methods of each ECU. The gateway implements the diagnostic communication routing for each ECU according to the agreed scheme, enabling diagnostic communication functions for each ECU in a complete vehicle configuration. This system is primarily applied to vehicle off-line testing and after-sales vehicle diagnostic and repair scenarios. Ethernet communication is used between the diagnostic port and the gateway to improve diagnostic efficiency in off-line and after-sales scenarios. The gateway retains traditional CAN diagnostic routing, performing CAN-to-CAN conversion of request messages, routing them to the target ECU, receiving a diagnostic response message from the ECU, and then forwarding the CAN message to the host computer device. This also ensures compatibility with existing scenarios where the host computer device sends CAN diagnostic messages.

[0027] It should be understood that in this application, "at least one (item)" means one or more, and "more than" means two or more. "And / or" is used to describe the relationship between related objects, indicating that three relationships can exist. For example, "A and / or B" can represent three cases: only A exists, only B exists, and both A and B exist simultaneously, where A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship. "At least one (item) of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one (item) of a, b, or c can represent: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, and c can be single or multiple.

[0028] It should be understood that in the description of the embodiments of this application, "multiple" means two or more, "greater than", "less than", "exceeding" etc. are understood to exclude the number itself, and "above", "below", "within" etc. are understood to include the number itself.

[0029] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces, or indirect coupling or communication connection between apparatuses or units, and may be electrical, mechanical, or other forms.

[0030] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of the embodiments of this application, depending on actual needs.

[0031] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0032] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0033] It should also be understood that the various implementation methods provided in this application can be combined arbitrarily to achieve different technical effects.

[0034] In the embodiments of this application, the terms "module" or "unit" refer to a computer program or part of a computer program that has a predetermined function and works with other related parts to achieve a predetermined goal, and can be implemented wholly or partially using software, hardware (such as processing circuitry or memory), or a combination thereof. Similarly, a processor (or multiple processors or memory) can be used to implement one or more modules or units. Furthermore, each module or unit can be part of an overall module or unit that includes the functionality of that module or unit.

[0035] The above is a detailed description of the embodiments of this application. However, this application is not limited to the above embodiments. Those skilled in the art can make various equivalent modifications or substitutions without departing from the spirit of this application. All such equivalent modifications or substitutions are included within the scope defined by the claims of this application.

Claims

1. A vehicle diagnostic communication system, characterized in that, The system includes: The host computer device is equipped with a diagnostic port, which establishes a communication connection with the gateway. Gateway, the gateway being used to establish communication connections with the host computer device and the vehicle terminal; On the vehicle side, it includes multiple electronic control units, each of which is used to perform diagnostic operations according to diagnostic instructions sent by the host computer device through the gateway; Specifically, a first type of communication link and a second type of communication link are established between the diagnostic port and the gateway; A first type of diagnostic communication link, a second type of diagnostic communication link, and a third type of diagnostic communication link are established between the gateway and each of the electronic control units.

2. The vehicle diagnostic communication system according to claim 1, characterized in that, The first type is Ethernet communication, the second type is CAN communication, and the third type is CANFD communication.

3. The vehicle diagnostic communication system according to claim 2, characterized in that, The network routing protocol between the gateway and the electronic control unit is determined by the network support type of the electronic control unit.

4. The vehicle diagnostic communication system according to claim 3, characterized in that, The network route of the communication link between the diagnostic port and the gateway is determined by determining the network routing protocol between the gateway and the electronic control unit.

5. The vehicle diagnostic communication system according to claim 3, characterized in that, If the network support type of the electronic control unit is CANFD diagnostic support, then the electronic control unit can respond to CAN diagnostic response messages and / or CANFD diagnostic response messages.

6. The vehicle diagnostic communication system according to claim 5, characterized in that, The gateway and each of the electronic control units also communicate and interact via DoIP messages.

7. The vehicle diagnostic communication system according to claim 6, characterized in that, If the electronic control unit sends a DoIP message to the gateway, the network route between the gateway and the diagnostic port of the host computer device is changed from gateway DoIP to DoIP route.

8. The vehicle diagnostic communication system according to claim 7, characterized in that, If the electronic control unit sends a CANFD message to the gateway, the network route between the gateway and the diagnostic port of the host computer device is changed from the gateway DoIP route to the CANFD route.

9. The vehicle diagnostic communication system according to claim 7, characterized in that, If the electronic control unit sends a CAN message to the gateway, the network route between the gateway and the diagnostic port of the host computer device is changed from the gateway DoIP route to the CAN route.

10. The vehicle diagnostic communication system according to claim 5, characterized in that, The length of the CAN diagnostic response message is 8 bytes, and the length of the CANFD diagnostic response message is no more than 64 bytes.

Images