Virtual diagnosis method compatible with multiple buses, interface layer architecture system and electronic equipment

Abstract

The invention relates to an automobile bus diagnosis technology, in particular to a virtual diagnosis method compatible with multiple buses, a virtual diagnosis interface layer architecture system and electronic equipment, and the virtual diagnosis method compatible with multiple buses comprises the following steps: creating an abstract interface layer between a diagnosis service layer and a data transmission layer, wherein the abstract interface layer comprises a universal interface module used for transmitting diagnosis service data irrelevant to a bus type and an auxiliary interface module used for transmitting auxiliary data strongly relevant to the bus type; and the diagnosis service layer calls the universal interface module or the universal interface module and the auxiliary interface module according to the bus type so as to transmit and receive diagnosis service data or diagnosis service data and auxiliary data to and from the data transmission layer.

Description

[0001] This application is based upon and claims the benefit of priority from Chinese patent application No. 2024104896021, filed on April 23, 2024. The entire contents of the above application are incorporated herein by reference. Technical Field

[0002] The present invention relates to automobile bus diagnosis technology, and in particular to a virtual diagnosis method compatible with multiple buses, a virtual diagnosis interface layer architecture system, and electronic equipment. Background Art

[0003] Diagnosis is one of the most commonly used technologies in automotive applications. Similar to diagnosing medical conditions in humans, vehicles also require diagnostic services to query their operating status. Currently, mainstream in-vehicle network communications include CAN / CANFD, LIN, Flexray, and in-vehicle Ethernet buses. Each bus has its own corresponding diagnostic service, including UDS on CAN, UDS on LIN, UDS on Flexray, and UDS on Ethernet. Each bus has its own independent physical layer and data transmission layer. Currently, in most user scenarios, users still develop diagnostic service systems based on the bus type of the current controller.

[0004] With existing solutions, developers often have to develop a data transmission layer tailored to the bus type used by the controller under test during R&D, production, and after-sales service. They then develop a diagnostic service layer based on this data transmission layer. Consequently, diagnostic service programs developed under this current development model cannot be reused across different bus types, resulting in significant waste of development resources, unmanageable development time, and increased management and learning costs.

[0005] Therefore, the existing technology has a technical problem that the data transmission layer of different vehicle buses (CAN / LIN / Flexray / Ethernet) is strongly coupled with the diagnostic service layer, resulting in the inability to reuse the diagnostic service layer.

[0006] It should be noted that the above information disclosed in this background technology section is only used to understand the background technology of the present application concept, and therefore, the above description is not considered to constitute information of the prior art. Summary of the Invention

[0007] The purpose of the present invention is to provide a virtual diagnosis method and a virtual diagnosis interface layer architecture system compatible with multiple buses.

[0008] In order to solve the above technical problems, the present invention provides a multi-bus compatible virtual diagnosis method, comprising:

[0009] An abstract interface layer is created between the diagnostic service layer and the data transmission layer, wherein the abstract interface layer includes: a general interface module for transmitting diagnostic service data that is independent of the bus type and an auxiliary interface module for transmitting auxiliary data that is strongly related to the bus type;

[0010] The diagnostic service layer calls the general interface module, or the general interface module and the auxiliary interface module according to the bus type, to send and receive diagnostic service data, or diagnostic service data and auxiliary data to the data transmission layer.

[0011] In another aspect, the present invention further provides a multi-bus compatible virtual diagnostic interface layer architecture system, comprising a computer device, wherein the computer device is configured to include:

[0012] Diagnostic service layer;

[0013] Data transmission layer;

[0014] The abstract interface layer is configured to be located between the diagnostic service layer and the data transmission layer, and includes: a general interface module for transmitting diagnostic service data that is independent of the bus type and an auxiliary interface module for transmitting auxiliary data that is strongly related to the bus type; and

[0015] The diagnostic service layer is configured to call the universal interface module, or the universal interface module and the auxiliary interface module according to the bus type, to send and receive diagnostic service data, or diagnostic service data and auxiliary data to the data transmission layer.

[0016] In a third aspect, the present invention further provides an electronic device, comprising:

[0017] Processor, readable storage medium, communication bus and communication interface; wherein

[0018] The processor, the readable storage medium and the communication interface communicate with each other via the communication bus;

[0019] The readable storage medium is used to store a program for executing the aforementioned multi-bus compatible virtual diagnosis method, and the program enables the processor to execute operations corresponding to the aforementioned multi-bus compatible virtual diagnosis method.

[0020] In a fourth aspect, the present invention further provides a computer-readable storage medium storing computer-readable instructions, which, when executed by at least one processor, enables the multi-bus compatible virtual diagnosis method as described above to be executed.

[0021] In a fifth aspect, the present invention further provides a computer program product, comprising a program or instructions, wherein when the program or instructions are executed on a computer, the multi-bus compatible virtual diagnostic method as described above is executed.

[0022] In a sixth aspect, the present invention further provides a vehicle diagnostic system, comprising: a bus adapter for communicating with a vehicle, and the electronic device as described above, which is electrically connected to the bus adapter to obtain vehicle bus data.

[0023] The beneficial effect of the present invention is that the multi-bus compatible virtual diagnostic method of the present invention provides a unified universal interface module for the upper diagnostic service layer according to the commonality of data transmission compatible with different bus types, and provides a targeted auxiliary interface module for the upper diagnostic service layer according to the unique data transmission requirements of each bus type, thereby realizing the decoupling of the diagnostic service layer and the bus type, so that the diagnostic service layer can be reused for different vehicle bus types. For a vehicle platform, this reusable feature is very meaningful. In the network architecture of a vehicle platform, there are often networks such as CAN / CANFD / LIN / Ethernet, and some OEM manufacturers' architectures also have bus types such as Flexray. With a unified virtual interface as support, the diagnostic operator only needs to do a set of diagnosis and flash related development to meet the diagnostic needs of the entire vehicle platform, instead of repeatedly developing multiple versions. This significantly saves development resources and reduces development costs and difficulty.

[0024] Other features and advantages of the present invention will be described in the following description, and in part will become apparent from the description, or understood by practicing the present invention. The purpose and other advantages of the present invention are realized and obtained by the structures particularly pointed out in the description and the drawings.

[0025] In order to make the above-mentioned objects, features and advantages of the present invention more obvious and easy to understand, preferred embodiments are given below and described in detail with reference to the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0026] In order to more clearly illustrate the specific embodiments of the present invention or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the specific embodiments or the description of the prior art. Obviously, the drawings described below are some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0027] Figure 1 A diagram showing the steps of a multi-bus compatible virtual diagnostic method according to some embodiments;

[0028] Figure 2 A principle block diagram of a multi-bus compatible virtual diagnostic interface layer architecture system according to some embodiments is shown;

[0029] Figure 3A functional block diagram of an electronic device involved in some embodiments is shown. DETAILED DESCRIPTION

[0030] To make the objectives, technical solutions, and advantages of the embodiments of the present invention more clear, the technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the embodiments described are only part of the embodiments of the present invention, not all of them. All other embodiments obtained by ordinary technicians in this field based on the embodiments of the present invention without making any creative efforts shall fall within the scope of protection of the present invention.

[0031] The abbreviations and key terms involved in this embodiment are defined as follows:

[0032] UDS, Unified Diagnostic Server: unified diagnostic service.

[0033] UDS on CAN / CANFD: Diagnostics based on CAN / CANFD networks.

[0034] UDS on LIN: Diagnostics based on LIN network.

[0035] UDS on Flexray: Diagnostics based on Flexray networks.

[0036] DOIP, Diagnostic on Internet Protocol: Diagnostic service based on IP network.

[0037] Transport Layer: Transport layer.

[0038] Write Data By Identifier: Write data by data identifier.

[0039] SID, Service Identifier: Service identifier.

[0040] DID, Data Identifier: Data identifier.

[0041] ECU: Electronic Control Unit.

[0042] Bootloader: Bootloader.

[0043] With existing solutions, developers often have to develop a data transmission layer tailored to the bus type used by the controller under test during R&D, production, and after-sales service. They then develop a diagnostic service layer based on this data transmission layer. Consequently, diagnostic service programs developed under this current development model cannot be reused across different bus types, resulting in significant waste of development resources, unmanageable development time, and increased management and learning costs.

[0044] Therefore, at least one embodiment provides a multi-bus compatible virtual diagnosis method, including:

[0045] An abstract interface layer is created between the diagnostic service layer and the data transmission layer, wherein the abstract interface layer includes: a general interface module for transmitting diagnostic service data that is independent of the bus type and an auxiliary interface module for transmitting auxiliary data that is strongly related to the bus type;

[0046] The diagnostic service layer calls the general interface module, or the general interface module and the auxiliary interface module according to the bus type, to send and receive diagnostic service data, or diagnostic service data and auxiliary data to the data transmission layer.

[0047] This multi-bus compatible virtual diagnostic method provides a unified universal interface module for the upper diagnostic service layer based on the commonality of data transmission compatible with different bus types, and provides targeted auxiliary interface modules for the upper diagnostic service layer based on the unique data transmission requirements of each bus type. This decouples the diagnostic service layer from the bus type, allowing the diagnostic service layer to be reused for different vehicle bus types. That is, the diagnostic service layer can flexibly select the corresponding universal interface module, or the universal interface module and the auxiliary interface module, according to the bus type, to point to the corresponding bus transmission layer in the data transmission layer for corresponding data transmission.

[0048] Various non-limiting implementations of the embodiments of the present disclosure are described in detail below with reference to the accompanying drawings.

[0049] like Figure 1 As shown, some embodiments provide a multi-bus compatible virtual diagnosis method, characterized by including:

[0050] Step S101: creating an abstract interface layer between the diagnostic service layer and the data transmission layer, wherein the abstract interface layer includes: a general interface module for transmitting diagnostic service data that is independent of the bus type and an auxiliary interface module for transmitting auxiliary data that is strongly related to the bus type; and

[0051] In step S102 , the diagnostic service layer calls the general interface module, or the general interface module and the auxiliary interface module according to the bus type, to send and receive diagnostic service data, or diagnostic service data and auxiliary data to the data transmission layer.

[0052] Specifically, the abstract interface layer provides abstracted interface modules for the diagnostic service layer. These interface modules consist of two parts: a general diagnostic interface module, which provides a bus-independent diagnostic service data transceiver interface. This module is public and serves as the core support layer for diagnostic transmission. The other part is an auxiliary interface module, which provides auxiliary data transceiver interfaces that are strongly related to the bus type. For example, Ethernet diagnostics require an IP connection to be established before initiating, and these interfaces are not required for other bus types.

[0053] The diagnostic service layer, defined in ISO 14229, is the diagnostic logic layer used to run diagnostic services, including, but not limited to, setting the ECU mode, reading data based on an ID, and writing data based on an ID. For diagnostic operators, running diagnostic services involves translating them into an array and then invoking the data transmission layer to send this array to the ECU. Upon receiving this data, the ECU returns the corresponding results.

[0054] The diagnostic service layer does not directly call the data transmission layer, but calls the general interface module, or the general interface module and the auxiliary interface module in the abstract layer according to the bus type selected by the diagnostic operator, thereby achieving decoupling from the data transmission layer of the specific bus type.

[0055] The data transmission layer is a modular layer used for data packetization and unpacking, enabling data block transmission. For example, CAN / CANFD implements the transport layer based on the transport layer protocol defined in 15765-2. The LIN specification also defines its own transport layer specification. Ethernet implements the transport layer directly based on the network transmission protocol.

[0056] This multi-bus compatible virtual diagnostic method provides a unified universal interface module for the upper diagnostic service layer based on the commonality of data transmission compatible with different bus types, and provides targeted auxiliary interface modules for the upper diagnostic service layer based on the unique data transmission requirements of each bus type. It decouples the diagnostic service layer from the bus type, so that the diagnostic service layer can be reused for different vehicle bus types. This reusability is very meaningful for a vehicle platform. The network architecture of a vehicle platform often has networks such as CAN / CANFD / LIN / Ethernet. Some OEM manufacturers' architectures also have bus types such as Flexray. With the support of a unified virtual interface, diagnostic operators only need to perform a set of diagnoses and flash related development to meet the diagnostic needs of the entire vehicle platform, rather than repeatedly developing multiple versions. This significantly saves development resources and reduces development costs and difficulty.

[0057] In some embodiments, the universal interface module provides a diagnostic service data transceiver interface that is independent of the bus type. The method for creating the universal interface module includes: setting

[0058] The tstp_request_and_get_response general interface function is used to send the data packet of the request ID and obtain the return result; set the tstp_request_and_get_response_functional general interface function to send the data packet of the functional ID and obtain the return result; set the tstp_send_request general interface function to send the data packet of the request ID; set the tstp_send_functional general interface function for the data packet of the functional ID.

[0059] Specifically, the diagnostic service layer is suitable for calling the tstp_request_and_get_response general interface function to send a data packet with a request ID to the data transmission layer and obtain a return result from the data transmission layer; the diagnostic service layer is suitable for calling the tstp_request_and_get_response_functional general interface function to send a data packet with a function ID to the data transmission layer and obtain a return result from the data transmission layer; the diagnostic service layer is suitable for calling the tstp_send_request general interface function to send a data packet with a request ID to the data transmission layer; and the diagnostic service layer is suitable for calling the tstp_send_functional general interface function to send a data packet with a function ID to the data transmission layer.

[0060] Specifically, these common interface functions are virtual function interfaces that run between the diagnostic service layer and the data transport layer. The data transport layer inherits the definitions of these virtual interfaces, meaning that each bus's data transport layer actually implements these virtual interfaces. When the user selects a bus type, the virtual interface points to the data transport layer of that specific bus type.

[0061] Specifically, the above interface functions are independent of bus type and are used to provide a data transfer channel for the upper diagnostic service layer. For example, when the interface function points to the CAN transport layer, data packets are unpacked and assembled based on 15765-2; when the interface function points to the DOIP input module, data packets are unpacked and assembled based on the TCP / IP transport layer.

[0062] Taking the completion of a "write data based on ID" service as an example, the application scenario assumes that the diagnostic device needs to write 20 bytes to the car ECU at ID = 0xFF01 through the 0x2E service (in the UDS protocol, 0x2E is the service identifier SID of the data identifier write service. Its core function is to write data to the specific address 0xFF01 of the car ECU through the specified data identifier DID). A total of 23 bytes need to be written, that is, the data array that needs to be written through the diagnostic is as follows:

[0063] char DatasToWrite

[23] ={0x2E, 0xFF, 0x01, 0xX01..0xX20};

[0064] The diagnostic service layer calls the universal interface module to send the write data request to the vehicle ECU through the data transmission layer and the physical interface layer to complete the write in the ECU and obtain the result return value after the ECU completes the write. The code for the diagnostic service layer to call the tstp_request_and_get_response universal interface function is as follows:

[0065] char Res

[10] ;

[0066] int resize = 10;

[0067] tstp_request_and_get_response(DatasToWrite,23,Res,@&resize);

[0068] Because it is implemented based on a universal interface module, the diagnostic service layer code above can be used to diagnose any bus type among CAN / CANFD / LIN / Flexray / DOIP, and the diagnostic service layer code call does not need to be modified due to the change of bus type.

[0069] When the universal interface module points to the traditional CAN transport layer, the transport layer receives 23 bytes at a time. However, since the CAN transport layer can transmit a maximum of 7 bytes at a time, it enters a multi-frame transmission process: first, the first frame is sent to request the start of multi-frame transmission; then, the flow control frame of the vehicle ECU is received, and the multi-frame transmission parameters such as STMin and Blocksize are obtained. Finally, the sending of continuous frames is started. Through the above multi-frame transmission process, the transmission of the above-mentioned diagnostic service data can be realized.

[0070] When the universal interface module points to the DOIP transport layer, since the number of bytes that can be transmitted by the TCP / UDP transport module exceeds 1000 bytes, only one TCP data packet or UDP data packet is needed to complete the transmission of the above diagnostic service data.

[0071] The above-mentioned interface functions can meet the transmission requirements during the diagnostic process. However, for some bus types, additional configuration is required during the transmission process. These behaviors are not common, so an auxiliary interface module is also provided. The method for creating the auxiliary interface module includes: setting the tstp_doip_connect auxiliary interface function to complete the TCP / IP connection between the diagnostic service layer and the ECU under test; setting the tstp_lin_set_run_with_normal_schedule_table auxiliary interface function to set the diagnostic schedule table and the normal schedule table in the LIN driver to run simultaneously; and setting the tstp_lin_tp_para auxiliary interface function to adjust the parameters of the LIN data transmission layer during the diagnostic process.

[0072] Specifically, the auxiliary interface module is strongly related to the bus type and cooperates with the general interface module to achieve complete decoupling of the diagnostic service layer and the data transmission layer.

[0073] Specifically, taking the aforementioned "write data based on ID" service as an example, the diagnostic device needs to write 20 bytes to the vehicle ECU at ID = 0xFF01 via the 0x2E service. If the diagnostic operator selects the CAN bus, meaning the universal interface module points to the CAN transport layer, the diagnostic service layer simply calls the tstp_request_and_get_response universal interface function to send and receive diagnostic service data. If the diagnostic operator selects the Ethernet bus, meaning the universal interface module points to the DOIP transport layer, the diagnostic service layer must first call the tstp_doip_connect auxiliary interface function to establish a TCP service connection with the vehicle ECU before calling the corresponding universal interface function; otherwise, the universal interface function will not take effect. This shows that auxiliary interface functions are strongly dependent on the bus type, while universal interface functions are independent of bus type.

[0074] Specifically, the diagnostic device in the case refers to a device including the multi-bus compatible virtual diagnostic interface layer architecture system involved in some embodiments.

[0075] In some embodiments, the data transmission layer packages and unpacks the received data according to the bus type to achieve transmission of the corresponding data; the bus type includes: one or more of CAN / CANFD bus, LIN bus, Flexray bus, and Ethernet bus.

[0076] Specifically, the data transmission layer includes: one or more of: CAN / CANFD transmission layer, LIN transmission layer, Flexray transmission layer, and DOIP transmission layer.

[0077] It should be noted that the transport layer is not limited to the CAN / CANFD transport layer, the LIN transport layer, the Flexray transport layer, and the DOIP transport layer, and the transport layer of the corresponding type of bus can be set according to actual needs.

[0078] As shown in Figure 2, some embodiments also provide a virtual diagnostic interface layer architecture system compatible with multiple buses, including a computer device, wherein the computer device is configured to include: a diagnostic service layer; a data transmission layer; an abstract interface layer, configured to be located between the diagnostic service layer and the data transmission layer, and including: a general interface module for transmitting diagnostic service data that is independent of the bus type and an auxiliary interface module for transmitting auxiliary data that is strongly related to the bus type; and the diagnostic service layer is configured to call the general interface module, or the general interface module and the auxiliary interface module according to the bus type, to send and receive diagnostic service data, or diagnostic service data and auxiliary data to the data transmission layer.

[0079] In some embodiments, the universal interface module provides a diagnostic service data transceiver interface that is independent of bus type, including: tstp_request_and_get_response universal interface function;

[0080] tstp_request_and_get_response_functional general interface function; tstp_send_request general interface function; tstp_send_functional general interface function; and the diagnostic service layer is suitable for calling the tstp_request_and_get_response general interface function to send a data packet with a request ID to the data transmission layer and obtain a return result from the data transmission layer; the diagnostic service layer is suitable for calling the tstp_request_and_get_response_functional general interface function to send a data packet with a function ID to the data transmission layer and obtain a return result from the data transmission layer; the diagnostic service layer is suitable for calling the tstp_send_request general interface function to send a data packet with a request ID to the data transmission layer; and the diagnostic service layer is suitable for calling the tstp_send_functional general interface function to send a data packet with a function ID to the data transmission layer.

[0081] In some embodiments, the auxiliary interface module provides an auxiliary data transceiver interface that is strongly related to the bus type, including: a tstp_doip_connect auxiliary interface function;

[0082] tstp_lin_set_run_with_normal_schedule_table auxiliary interface function; and tstp_lin_tp_para auxiliary interface function; and the diagnostic service layer is suitable for calling tstp_doip_connect auxiliary interface function to complete the TCP / IP connection; the diagnostic service layer is suitable for calling

[0083] The tstp_lin_set_run_with_normal_schedule_table auxiliary interface function is used to set the diagnostic schedule table and the normal schedule table in the LIN driver to run simultaneously; the diagnostic service layer is suitable for calling the tstp_lin_tp_para auxiliary interface function to adjust the parameters of the LIN transport layer during the diagnostic process.

[0084] In some embodiments, the data transmission layer includes: one or more of: CAN / CANFD transmission layer, LIN transmission layer, Flexray transmission layer, and DOIP transmission layer.

[0085] In some embodiments, the virtual diagnostic interface layer architecture system further includes: a physical interface layer.

[0086] Specifically, the physical interface layer refers to the physical layer interface of the vehicle bus such as CAN / CANFD / LIN / Flexray / Ethernet.

[0087] The specific implementation functions of the diagnostic service layer, abstract interface layer and data transmission layer are implemented in a computer device. For details, please refer to the aforementioned multi-bus compatible virtual diagnostic method, which will not be repeated here.

[0088] Based on the multi-bus compatible virtual diagnostic interface layer architecture system of this embodiment, user-developed diagnostic service layer applications such as diagnostic test scripts and bootloaders for flashing only need to be developed once to cover the needs of the entire vehicle platform.

[0089] The electronic device in the embodiment of the present disclosure is described below from the perspective of hardware processing:

[0090] The embodiments of the present disclosure do not limit the specific implementation of the electronic device.

[0091] like Figure 3 As shown, some embodiments also provide an electronic device, comprising: a processor, a readable storage medium, a communication bus and a communication interface; wherein the processor, the readable storage medium and the communication interface communicate with each other through the communication bus; the readable storage medium is used to store a program for executing the multi-bus compatible virtual diagnostic method, and the program enables the processor to execute operations corresponding to the multi-bus compatible virtual diagnostic method.

[0092] In some embodiments, a computer device or an industrial computer can also be used as a type of electronic device.

[0093] Figure 3 The structure shown does not limit the electronic device and may include fewer or more components than shown in the figure, or combine some components, or arrange the components differently.

[0094] In some embodiments, the communication interface may be an RS232, RS485, USB port, or TYPE port, which may be connected to an external bus adapter. It may also include a wired or wireless network interface. The network interface may optionally include a wired interface and / or a wireless interface (such as a WI-FI interface, a Bluetooth interface, etc.), which is typically used to establish a communication connection between the computer device and other electronic devices.

[0095] In some embodiments, the readable storage medium or computer-readable storage medium includes at least one type of memory, including flash memory, hard disk, multimedia card, card-type memory (such as SD memory, etc.), magnetic memory, magnetic disk, optical disk, etc. In some embodiments, it can be an internal storage unit of a computer device, such as the hard disk of the computer device. In other embodiments, the memory can also be an external storage device of the computer device, such as a plug-in hard disk equipped on the computer device, a smart memory card (Smart Media Card, SMC), a secure digital (Secure Digital, SD) card, a flash card (Flash Card), etc. Furthermore, the memory can also include both an internal storage unit of the computer device and an external storage device. The memory can be used not only to store application software and various types of data installed in the computer device, such as computer program code, but also to temporarily store data that has been output or is to be output.

[0096] In some embodiments, the processor may be a central processing unit (CPU), a controller, a microcontroller, a microprocessor, or other data processing chip, used to run program codes stored in a memory or process data, such as executing a computer program.

[0097] In some embodiments, the communication bus may also be an input / output bus, which may be a Peripheral Component Interconnect (PCI) bus or an Enhanced Industry Standard Architecture (EISA) bus, etc. The bus may be divided into an address bus, a data bus, a control bus, etc.

[0098] Optionally, the computer device may further include a user interface, which may include a display and an input unit such as a keyboard. Optionally, the user interface may also include a standard wired interface or a wireless interface. Optionally, in some embodiments, the display may be an LED display, a liquid crystal display, a touch-sensitive liquid crystal display, or an OLED (Organic Light-Emitting Diode) touchscreen. The display may also be appropriately referred to as a display screen or a display unit, and is used to display information processed by the computer device and to display web pages.

[0099] When the processor executes the program, the above Figure 1 The steps in the embodiment of the remote deployment method of the software platform user interface shown are, for example Figure 1Alternatively, when the processor executes the computer program, the functions of the modules or units in the above-mentioned device embodiments are realized.

[0100] Some embodiments further provide a vehicle diagnostic system, comprising: a bus adapter communicating with a vehicle, and the aforementioned electronic device electrically connected to the bus adapter to obtain vehicle bus data.

[0101] Some embodiments also provide a readable storage medium storing computer-readable instructions, which, when executed by at least one processor, enables a virtual diagnostic method compatible with multiple buses to be executed; the virtual diagnostic method compatible with multiple buses includes: creating an abstract interface layer between a diagnostic service layer and a data transmission layer, wherein the abstract interface layer includes: a general interface module for transmitting diagnostic service data that is independent of the bus type and an auxiliary interface module for transmitting auxiliary data that is strongly related to the bus type; the diagnostic service layer calls the general interface module, or the general interface module and the auxiliary interface module according to the bus type, to send and receive diagnostic service data, or diagnostic service data and auxiliary data to the data transmission layer.

[0102] Some embodiments further provide a computer-readable storage medium storing computer-readable instructions, which, when executed by at least one processor, enable the aforementioned multi-bus compatible virtual diagnostic method to be executed, specifically:

[0103] An abstract interface layer is created between the diagnostic service layer and the data transmission layer, wherein the abstract interface layer includes: a general interface module for transmitting diagnostic service data that is independent of the bus type and an auxiliary interface module for transmitting auxiliary data that is strongly related to the bus type;

[0104] The diagnostic service layer calls the general interface module, or the general interface module and the auxiliary interface module according to the bus type, to send and receive diagnostic service data, or diagnostic service data and auxiliary data to the data transmission layer.

[0105] Please refer to the detailed description of the multi-bus compatible virtual diagnosis method, which will not be repeated here.

[0106] Some embodiments further provide a computer program product, including a program or instructions, wherein when the program or instructions are executed on a computer, a multi-bus compatible virtual diagnostic method is performed; the multi-bus compatible virtual diagnostic method includes:

[0107] An abstract interface layer is created between the diagnostic service layer and the data transmission layer, wherein the abstract interface layer includes: a general interface module for transmitting diagnostic service data that is independent of the bus type and an auxiliary interface module for transmitting auxiliary data that is strongly related to the bus type;

[0108] The diagnostic service layer calls the general interface module, or the general interface module and the auxiliary interface module according to the bus type, to send and receive diagnostic service data, or diagnostic service data and auxiliary data to the data transmission layer.

[0109] Some embodiments further provide a computer program product including a readable storage medium having readable program code stored thereon, the readable program code including instructions that cause at least one processor (one or more computer devices) to perform the following operations:

[0110] An abstract interface layer is created between the diagnostic service layer and the data transmission layer, wherein the abstract interface layer includes: a general interface module for transmitting diagnostic service data that is independent of the bus type and an auxiliary interface module for transmitting auxiliary data that is strongly related to the bus type;

[0111] The diagnostic service layer calls the general interface module, or the general interface module and the auxiliary interface module according to the bus type, to send and receive diagnostic service data, or diagnostic service data and auxiliary data to the data transmission layer.

[0112] In some embodiments, it should be understood that the disclosed devices and methods can also be implemented in other ways. The device embodiments described above are merely schematic. For example, the flowcharts and block diagrams in the accompanying drawings show the possible architectures, functions, and operations of the devices, methods, and embedded program products according to multiple embodiments of the present invention. In this regard, each box in the flowchart or block diagram can represent a module, program segment, or part of a code, and the module, program segment, or part of the code contains one or more executable instructions for implementing the specified logical functions. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in an order different from that marked in the accompanying drawings. For example, two consecutive boxes can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram and / or flowchart, and the combination of boxes in the block diagram and / or flowchart, can be implemented using a dedicated hardware-based system that performs the specified function or action.

[0113] In addition, the functional modules in the various embodiments of the present invention may be integrated together to form an independent part, or each module may exist independently, or two or more modules may be integrated to form an independent part.

[0114] If the functions are implemented as software modules and sold or used as independent products, they can be stored in a readable storage medium. Based on this understanding, the technical solution of the present invention, or the portion that contributes to the prior art, or part of the technical solution, can be embodied in the form of a software product. This embedded software product, stored in a storage medium, executes all or part of the steps of the methods described in various embodiments of the present invention.

[0115] With the above-described preferred embodiments of the present invention as a guide, and with reference to the above description, relevant personnel are fully capable of making various changes and modifications without departing from the technical scope of this invention. The technical scope of this invention is not limited to the contents of the specification and must be determined according to the scope of the claims.

Claims

1. A multi-bus compatible virtual diagnostic method, characterized in that: include: An abstract interface layer is created between the diagnostic service layer and the data transmission layer, wherein the abstract interface layer includes: a general interface module for transmitting diagnostic service data that is independent of the bus type and an auxiliary interface module for transmitting auxiliary data that is strongly related to the bus type; The diagnostic service layer calls the general interface module, or the general interface module and the auxiliary interface module according to the bus type, to send and receive diagnostic service data, or diagnostic service data and auxiliary data to the data transmission layer.

2. The multi-bus compatible virtual diagnosis method according to claim 1, characterized in that: The universal interface module provides a diagnostic service data transceiver interface that is independent of bus type. The method for creating the universal interface module includes: Set up the tstp_request_and_get_response general interface function; Set up the tstp_request_and_get_response_functional general interface function; Set up the tstp_send_request general interface function; and Set the tstp_send_functional general interface function.

3. The multi-bus compatible virtual diagnosis method according to claim 2, characterized in that: The diagnostic service layer is adapted to call the tstp_request_and_get_response general interface function to send a data packet of the request ID to the data transmission layer and obtain a return result from the data transmission layer; The diagnostic service layer is adapted to call the tstp_request_and_get_response_functional universal interface function to send a data packet of a function ID to the data transmission layer and obtain a return result from the data transmission layer; The diagnostic service layer is adapted to call the tstp_send_request general interface function to send a data packet of the request ID to the data transmission layer; as well as The diagnostic service layer is adapted to call the tstp_send_functional general interface function to send a data packet with a functional ID to the data transmission layer.

4. The multi-bus compatible virtual diagnosis method according to claim 3, characterized in that: The auxiliary interface module provides an auxiliary data transceiver interface that is strongly related to the bus type. The method for creating the auxiliary interface module includes: Set up the tstp_doip_connect auxiliary interface function; Set the tstp_lin_set_run_with_normal_schedule_table auxiliary interface function; and Set the tstp_lin_tp_para auxiliary interface function.

5. The multi-bus compatible virtual diagnosis method according to claim 4, characterized in that: The diagnostic service layer is adapted to call the tstp_doip_connect auxiliary interface function to complete the TCP / IP connection between it and the ECU under test; The diagnostic service layer is adapted to call the tstp_lin_set_run_with_normal_schedule_table auxiliary interface function to set the diagnostic schedule table and the normal schedule table in the LIN driver to run simultaneously; The diagnostic service layer is adapted to call the tstp_lin_tp_para auxiliary interface function to adjust the parameters of the LIN transport layer during the diagnostic process.

6. The multi-bus compatible virtual diagnosis method according to claim 5, characterized in that: The data transmission layer packages and unpacks the received data according to the bus type to achieve transmission of the corresponding data; The bus type includes: one or more of CAN / CANFD bus, LIN bus, Flexray bus, and Ethernet bus.

7. A multi-bus compatible virtual diagnostic interface layer architecture system, characterized in that: comprising a computer device, the computer device being configured to include: Diagnostic service layer; Data transmission layer; The abstract interface layer is configured to be located between the diagnostic service layer and the data transmission layer, and includes: a general interface module for transmitting diagnostic service data that is independent of the bus type and an auxiliary interface module for transmitting auxiliary data that is strongly related to the bus type; and The diagnostic service layer is configured to call the universal interface module, or the universal interface module and the auxiliary interface module according to the bus type, to send and receive diagnostic service data, or diagnostic service data and auxiliary data to the data transmission layer.

8. The multi-bus compatible virtual diagnostic interface layer architecture system according to claim 7, characterized in that: The universal interface module provides a diagnostic service data transceiver interface that is independent of the bus type, including: tstp_request_and_get_response general interface function; tstp_request_and_get_response_functional general interface function; tstp_send_request general interface function; tstp_send_functional general interface function; and The diagnostic service layer is adapted to call the tstp_request_and_get_response general interface function to send a data packet of the request ID to the data transmission layer and obtain a return result from the data transmission layer; The diagnostic service layer is adapted to call the tstp_request_and_get_response_functional universal interface function to send a data packet of a function ID to the data transmission layer and obtain a return result from the data transmission layer; The diagnostic service layer is adapted to call the tstp_send_request general interface function to send a data packet of the request ID to the data transmission layer; and The diagnostic service layer is adapted to call the tstp_send_functional general interface function to send a data packet with a functional ID to the data transmission layer.

9. The multi-bus compatible virtual diagnostic interface layer architecture system according to claim 8, characterized in that: The auxiliary interface module provides an auxiliary data transceiver interface that is strongly related to the bus type, including: tstp_doip_connect auxiliary interface function; tstp_lin_set_run_with_normal_schedule_table auxiliary interface function; and tstp_lin_tp_para auxiliary interface function; and The diagnostic service layer is adapted to call the tstp_doip_connect auxiliary interface function to complete the TCP / IP connection; The diagnostic service layer is adapted to call the tstp_lin_set_run_with_normal_schedule_table auxiliary interface function to set the diagnostic schedule table and the normal schedule table in the LIN driver to run simultaneously; The diagnostic service layer is adapted to call the tstp_lin_tp_para auxiliary interface function to adjust the parameters of the LIN transport layer during the diagnostic process.

10. The multi-bus compatible virtual diagnostic interface layer architecture system according to claim 9, characterized in that: The data transmission layer includes: one or more of a CAN / CANFD transmission layer, a LIN transmission layer, a Flexray transmission layer, and a DOIP transmission layer.

11. The multi-bus compatible virtual diagnostic interface layer architecture system according to claim 10, characterized in that: The virtual diagnostic interface layer architecture system also includes: a physical interface layer.

12. An electronic device, characterized in that: include: Processor, readable storage medium, communication bus and communication interface; in The processor, the readable storage medium and the communication interface communicate with each other via the communication bus; The readable storage medium is used to store a program for executing the multi-bus compatible virtual diagnosis method according to any one of claims 1 to 6, wherein the program enables the processor to execute operations corresponding to the multi-bus compatible virtual diagnosis method.

13. A computer-readable storage medium storing computer-readable instructions, which, when executed by at least one processor, enables the multi-bus compatible virtual diagnosis method according to any one of claims 1 to 6 to be executed.

14. A computer program product comprising a program or an instruction, wherein when the program or the instruction is executed on a computer, the multi-bus compatible virtual diagnosis method according to any one of claims 1 to 6 is executed.

15. A vehicle diagnostic system, comprising: a bus adapter to communicate with the vehicle, and The electronic device as claimed in claim 12, being electrically connected to the bus adapter to obtain vehicle bus data.

Images