Vehicle diagnostic processing method, apparatus, device, vehicle and storage medium

Abstract

A vehicle diagnostic processing method, an apparatus, a device (50), a vehicle (60) and a storage medium. The method comprises: a diagnostic communication protocol module (51) acquires a diagnostic service request (101), the diagnostic service request comprising a service request event and a service request type; the diagnostic communication protocol module (51) performs filtering and unpacking processing on the diagnostic service request to acquire a processed diagnostic service request (102); according to the service request type in the processed diagnostic service request, a service allocation module (52) uploads the processed diagnostic service request to a diagnostic event management module (53) or a data communication module (54) (103); and upon receiving the processed diagnostic service request, the diagnostic event management module (53) or the data communication module (54) performs corresponding service diagnostic processing according to the service request event (104). The method improves the fault diagnosis efficiency, and reduces the development cost of diagnostic devices and the vehicle maintenance difficulty.

Description

Vehicle diagnostic processing method, device, equipment, vehicle and storage medium

[0001] This application claims priority to the Chinese patent application filed with the China Patent Office on February 23, 2024, with application number 202410200030.0 and application name “A vehicle diagnostic processing method, device, equipment, vehicle and storage medium”, the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of communication technology, and in particular to a vehicle diagnostic processing method, device, equipment, vehicle and storage medium. Background Art

[0003] With the widespread use of vehicles, they have become a primary mode of transportation, bringing great convenience to our lives. However, various vehicle failures may occur during use. To resolve these problems, maintenance personnel can use the middleware in the on-board diagnostics (OBD) system to perform fault diagnosis and determine whether the vehicle is faulty.

[0004] However, in the development process of commonly used on-board self-diagnostic systems, diagnostic services are developed at the same time as applications. Different applications need to write duplicate code to implement their corresponding diagnostic services for the same diagnostic type, resulting in code duplication and a relatively close connection and high coupling between the application and diagnostic service development. Furthermore, if the diagnostic protocol in the diagnostic service changes or is upgraded, the application also needs to be modified and updated accordingly, which will correspondingly extend the development cycle, reduce development efficiency, and increase development costs and maintenance difficulties. Summary of the Invention

[0005] The present application provides a vehicle diagnostic processing method, device, equipment, vehicle and storage medium to solve the technical problems of high repetitiveness of fault diagnostic codes and high development costs and maintenance difficulties.

[0006] In a first aspect, the present application provides a vehicle diagnostic processing method, which is applied to a diagnostic device, wherein the diagnostic device includes: a diagnostic communication protocol module, a service allocation module, a diagnostic event management module, and a data communication module. The method includes:

[0007] The diagnostic communication protocol module obtains a diagnostic service request; wherein the diagnostic service request includes a service request event and a service request type;

[0008] The diagnostic communication protocol module filters and unpacks the diagnostic service request to obtain a processed diagnostic service request;

[0009] The service allocation module uploads the processed diagnostic service request to the diagnostic event management module or the data communication module according to the service request type in the processed diagnostic service request;

[0010] When receiving the processed diagnostic service request, the diagnostic event management module or the data communication module performs corresponding service diagnostic processing according to the service request event.

[0011] Optionally, in the above method, the diagnostic device further includes: a conversation judgment module, and the method further includes:

[0012] If the session determination module determines that the processed diagnostic service request meets the preconfigured filtering condition, the processed diagnostic service request is used as the target diagnostic service request, and the target diagnostic service request is reported to the service allocation module;

[0013] The service allocation module uploads the processed diagnostic service request to the diagnostic event management module or the data communication module according to the service request type in the processed diagnostic service request, including:

[0014] The service allocation module uploads the target diagnostic service request to the diagnostic event management module or the data communication module according to the service request type in the target diagnostic service request.

[0015] Optionally, in the above method, the service allocation module uploads the processed diagnostic service request to the diagnostic event management module or the data communication module according to the service request type in the processed diagnostic service request, including:

[0016] When the service allocation module determines that the service request type is a passive service request type, the service allocation module uploads the processed diagnostic service request to a diagnostic event management module that matches the passive service request type;

[0017] or,

[0018] When the service allocation module determines that the service request type is an active service request type, the service allocation module uploads the processed diagnostic service request to a data communication module that matches the active service request type.

[0019] Optionally, in the above method, when the diagnostic event management module or the data communication module receives the processed diagnostic service request, performing corresponding service diagnostic processing according to the service request event, including:

[0020] When receiving the processed diagnostic service request, the diagnostic event management module reads diagnostic information related to the service request event from the diagnostic event management module according to the service request event, and obtains a fault code corresponding to the diagnostic information.

[0021] Optionally, in the above method, when the diagnostic event management module or the data communication module receives the processed diagnostic service request, performing corresponding service diagnostic processing according to the service request event, including:

[0022] When receiving the processed diagnostic service request, the data communication module determines the working mode corresponding to the diagnostic service request according to the target controller in the processed diagnostic service request;

[0023] When the data communication module determines that the corresponding working mode of the diagnostic service request is the intra-domain working mode, the processed diagnostic service request is sent to the domain controller so that the domain controller can perform diagnostic operations according to the target diagnostic application corresponding to the service request event and obtain diagnostic information.

[0024] Optionally, the method as described above further includes:

[0025] When the data communication module determines that the corresponding working mode of the diagnostic service request is an out-of-domain working mode, the processed diagnostic service request is sent to the out-of-domain controller so that the out-of-domain controller can perform diagnostic operations on the target diagnostic application according to the service request event and obtain diagnostic information.

[0026] In a second aspect, the present application provides a diagnostic device, the diagnostic device comprising a diagnostic communication protocol module, a service allocation module, a diagnostic event management module, and a data communication module;

[0027] Diagnostic communication protocol module, used to obtain diagnostic service requests;

[0028] The diagnostic communication protocol module is further configured to filter and unpack the diagnostic service request to obtain a processed diagnostic service request;

[0029] a service allocation module, configured to upload the processed diagnostic service request to the diagnostic event management module or the data communication module according to the service request type in the processed diagnostic service request;

[0030] The diagnostic event management module is configured to, upon receiving the processed diagnostic service request, perform corresponding service diagnostic processing according to the service request event;

[0031] or,

[0032] The data communication module is configured to perform corresponding service diagnosis processing according to the service request event when receiving the processed diagnosis service request.

[0033] In a third aspect, the present application provides an electronic device, comprising: a processor, and a memory communicatively connected to the processor;

[0034] The memory stores computer-executable instructions;

[0035] The processor executes the computer-executable instructions stored in the memory to implement any vehicle diagnostic method described in the above embodiments.

[0036] In a fourth aspect, the present application provides a vehicle, comprising a domain controller and a diagnostic device provided in each domain controller; wherein the diagnostic device is used to implement any of the vehicle diagnostic methods described in the above embodiments.

[0037] In a fifth aspect, the present application provides a computer-readable storage medium, in which computer-executable instructions are stored. When the computer-executable instructions are executed by a processor, they are used to implement the diagnostic processing method for the vehicle described in any of the above embodiments.

[0038] In a sixth aspect, the present application provides a computer program product, comprising a computer program, which, when executed by a processor, implements the diagnostic processing method for the vehicle described in any one of the above embodiments.

[0039] In a seventh aspect, the present application provides a computer program, which, when executed by a processor, is used to implement the diagnostic processing method for any of the vehicles described in the above embodiments.

[0040] The present application provides a vehicle diagnostic processing method, device, equipment, vehicle and storage medium, wherein the method can be applied to a diagnostic device, which includes: a diagnostic communication protocol module, a service allocation module, a diagnostic event management module and a data communication module. The diagnostic communication protocol module obtains a diagnostic service request, filters and unpacks it, and obtains a processed diagnostic service request. The service allocation module then uploads the processed diagnostic service request to the diagnostic event management module or the data communication module for corresponding service diagnostic processing based on the service request type in the processed diagnostic service request. Compared with the prior art in which diagnostic services are developed at the same time as application development, different applications need to write duplicate code to implement their corresponding diagnostic services for the same diagnostic type, resulting in a long development cycle and reduced development efficiency. The present application can receive diagnostic service requests containing various service request events and service request types through the diagnostic service protocol module, and after filtering and unpacking them based on the diagnostic communication protocol module, it can allocate them to the diagnostic event management module or the data communication module in a targeted manner based on the service allocation module to perform corresponding diagnostic processing, thereby realizing support for multiple diagnostic services, and calling the corresponding diagnostic services when developing different types of applications. There is no need to develop duplicate code for the same type of diagnostic service, thereby effectively improving the efficiency of fault diagnosis and reducing the development cost and maintenance difficulty of diagnostic equipment. BRIEF DESCRIPTION OF THE DRAWINGS

[0041] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.

[0042] FIG1 is a schematic diagram of the architecture of the application scenario of the vehicle diagnostic processing method in this application;

[0043] FIG2 is a flow chart of an embodiment of a vehicle diagnostic processing method provided by the present application;

[0044] FIG3 is a flow chart of another embodiment of a vehicle diagnostic processing method provided by the present application;

[0045] FIG4 is a flow chart of another embodiment of a vehicle diagnostic processing method provided by the present application;

[0046] FIG5 is a flow chart of another embodiment of a vehicle diagnostic processing method provided by the present application;

[0047] FIG6 is a schematic structural diagram of an embodiment of a diagnostic device provided by the present application;

[0048] FIG7 is a schematic structural diagram of an embodiment of a vehicle provided by the present application;

[0049] FIG8 is a schematic structural diagram of an embodiment of an electronic device provided in this application.

[0050] The above drawings illustrate specific embodiments of the present application, which will be described in more detail below. These drawings and the textual description are not intended to limit the scope of the present application in any way, but rather to illustrate the concepts of the present application to those skilled in the art by reference to specific embodiments. DETAILED DESCRIPTION

[0051] Exemplary embodiments will be described in detail herein, with examples illustrated in the accompanying drawings. In the following description, when referring to the drawings, identical numerals in different figures represent identical or similar elements, unless otherwise indicated. The embodiments described in the following exemplary embodiments are not intended to represent all embodiments consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present application, as detailed in the appended claims.

[0052] With the increasing popularity of vehicles, cars have become a common means of transportation, providing great convenience for people's daily travel. However, during use, vehicles inevitably experience malfunctions. To address these issues, middleware can be used to diagnose the faults.

[0053] However, traditional diagnostic approaches often couple the application layer and diagnostic strategies. Even for the same diagnostic type, each application needs to write specific code to implement fault diagnosis. This coupling makes the system difficult to scale and maintain, as any changes or upgrades to the communication protocol require corresponding modifications and updates to the diagnostic software. This leads to code duplication, increased development costs, and increased maintenance complexity.

[0054] In order to solve the above technical problems, the invention concept of this application is: how to achieve decoupling between diagnostic services and application software, improve fault diagnosis efficiency, and reduce development costs and maintenance difficulties.

[0055] The following specific embodiments describe in detail the technical solution of the present application and how the technical solution of the present application solves the above-mentioned technical problems. The following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments. The embodiments of the present application will be described below in conjunction with the accompanying drawings.

[0056] Figure 1 is an architectural diagram of the application scenario of the vehicle diagnostic processing method in this application. As shown in Figure 1, the scenario mainly includes: multiple domains, and each domain includes multiple controllers, and the controllers are connected via Ethernet. For example, this application takes two domains as an example, namely domain A and domain B; and takes one controller in each domain as an example, namely domain A controller and domain B controller, and a diagnostic device is deployed in each controller. Among them, the diagnostic device includes a diagnostic communication protocol module, a data communication module and a diagnostic event management module. Specifically, the diagnostic communication protocol module is used to obtain diagnostic service requests, including calls to UDP and TCP interfaces; the data communication module is mainly used to support diagnostic communication services; the diagnostic event management module is mainly used to support diagnostic event services, and implements application layer APP calls and cross-domain communications through the controller's communication interaction API interface.

[0057] FIG2 is a flow chart of an embodiment of a vehicle diagnostic processing method provided by the present application. As shown in FIG2 , the method includes:

[0058] Step 101: The diagnostic communication protocol module obtains a diagnostic service request.

[0059] In this embodiment, when the access device accesses a diagnostic communication protocol module, such as a DoIP module, the DoIP module may obtain a diagnostic service request issued by the access device; wherein the diagnostic service request includes a service request event and a service request type.

[0060] Step 102: The diagnostic communication protocol module filters and unpacks the diagnostic service request to obtain a processed diagnostic service request.

[0061] In this embodiment, after receiving a diagnostic service request from an access device, the DoIP module filters the diagnostic service request according to preset filtering rules. These rules may include target device, diagnostic type, data range, etc. Only requests that meet the filtering rules are processed. The DoIP module unpacks the filtered diagnostic service request to obtain the processed diagnostic service request.

[0062] Step 103: The service allocation module uploads the processed diagnostic service request to the diagnostic event management module or the data communication module according to the service request type in the processed diagnostic service request.

[0063] In this embodiment, when the service allocation module receives the processed diagnostic service request, it analyzes the service request type in the diagnostic service request and uploads the processed diagnostic service request to the diagnostic event management (DEM) module or the data communication (DCM) module according to different request types.

[0064] Step 104: When the diagnostic event management module or the data communication module receives the processed diagnostic service request, it performs corresponding service diagnostic processing according to the service request event.

[0065] In this embodiment, when the diagnostic event management module and the data communication module respectively receive processed diagnostic service requests of corresponding types, they perform corresponding service diagnostic processing according to the service request event in the diagnostic service request.

[0066] In this embodiment, a diagnostic service request is obtained through a diagnostic communication protocol module, and the diagnostic service request is filtered and unpacked. The service allocation module uploads the processed diagnostic service request to a diagnostic event management module or a data communication module according to the service request type in the processed diagnostic service request, and performs corresponding service diagnostic processing in the diagnostic event management module or the data communication module. Compared with the prior art in which diagnostic services are developed at the same time as an application, different applications need to write duplicate code to implement their corresponding diagnostic services for the same diagnostic type, thereby leading to a long development cycle and reduced development efficiency. The diagnostic device provided in this application can receive diagnostic service requests containing various service request events and service request types, and after filtering and unpacking them based on the diagnostic communication protocol module, it can be targeted and allocated to the diagnostic event management module or the data communication module based on the service allocation module for corresponding diagnostic processing, thereby supporting multiple diagnostic services. When developing different types of applications, there is no need to repeatedly develop code for the same type of diagnostic service, thereby effectively improving fault diagnosis efficiency and reducing the development cost and maintenance difficulty of the diagnostic device.

[0067] FIG3 is a flow chart of another embodiment of a vehicle diagnostic processing method provided by the present application. As shown in FIG3, based on the above embodiment, the diagnostic device further includes: a session judgment module, and the method further includes:

[0068] Step 201: If the session determination module determines that the processed diagnostic service request meets the pre-configured filtering condition, it uses the processed diagnostic service request as the target diagnostic service request and reports the target diagnostic service request to the service allocation module.

[0069] In this embodiment, the post-processing diagnostic service request is parsed and a match determination is performed on the obtained post-processing diagnostic service request based on the current session information and preset session rules. If the requested session information does not match the current session, the request may not be processed. Based on the determination result, the diagnostic service request that satisfies the current session is filtered, and the post-processing diagnostic service request is used as the target diagnostic service request, which is then reported to the service allocation module.

[0070] Accordingly, in step 103 of the above embodiment, the specific implementation of "the service allocation module uploading the processed diagnostic service request to the diagnostic event management module or the data communication module according to the service request type in the processed diagnostic service request" is as follows:

[0071] Step 202: The service allocation module uploads the target diagnostic service request to the diagnostic event management module or the data communication module according to the service request type in the target diagnostic service request.

[0072] In this embodiment, when the service allocation module receives the target diagnostic service request, it analyzes the service request type in the diagnostic service request and uploads the target diagnostic service request to the diagnostic event management module or the data communication module according to different request types.

[0073] In this embodiment, the session judgment module determines whether the processed diagnostic service request meets the pre-configured filtering conditions, and reports the diagnostic service request that meets the current session as the target diagnostic service request to the service allocation module; the service allocation module uploads it to the diagnostic event management module or the data communication module according to different request types. The method of the present application can reduce unnecessary diagnostic service requests sent to subsequent modules through the filtering mechanism of the session judgment module, thereby improving processing efficiency; at the same time, the service allocation module can allocate service requests to the diagnostic event management module or the data communication module according to the type of service request, ensuring that different types of requests are properly processed, further optimizing service allocation and resource utilization.

[0074] FIG4 is a flow chart illustrating another embodiment of a vehicle diagnostic processing method provided herein. As shown in FIG4 , based on the above embodiment, the specific implementation method of step 103, "the service allocation module uploads the processed diagnostic service request to the diagnostic event management module or the data communication module based on the service request type in the processed diagnostic service request," or step 202, "the service allocation module uploads the target diagnostic service request to the diagnostic event management module or the data communication module based on the service request type in the target diagnostic service request," may further include:

[0075] Step 301: When the service allocation module determines that the service request type is a passive service request type, the service allocation module uploads the processed diagnostic service request to a diagnostic event management module that matches the passive service request type.

[0076] In this embodiment, after receiving the processed diagnostic service request, the service allocation module first determines the type of the service request. If it is determined that the service request type is a passive service request type, the service allocation module uploads the processed diagnostic service request to the diagnostic event management module that matches the passive service request type.

[0077] Accordingly, based on the above embodiment, the specific implementation method of step 104 "the diagnostic event management module or the data communication module performs corresponding service diagnostic processing according to the service request event when receiving the processed diagnostic service request" may also include:

[0078] Step 302: When the diagnostic event management module receives the processed diagnostic service request, it reads diagnostic information related to the service request event from the diagnostic event management module according to the service request event, and obtains the fault code corresponding to the diagnostic information.

[0079] In this embodiment, when an application fails, the application immediately sends diagnostic information to the corresponding diagnostic event management module, and the diagnostic information of the application is stored in the diagnostic event management module; when the diagnostic event management module receives a processed diagnostic service request, the service request event is parsed, the diagnostic information related to the service request event is read from the diagnostic event management module, and the fault code corresponding to the diagnostic information is obtained.

[0080] In this embodiment, the diagnostic event management module stores diagnostic information generated by the corresponding application when a fault occurs. When the diagnostic event management module receives a processed diagnostic service request, based on the service request event, it reads the diagnostic information related to the service request event from the diagnostic event management module and obtains the fault code corresponding to the diagnostic information. Compared to the prior art, the method of this application stores the diagnostic information generated by the application when a fault occurs through the diagnostic event management module, and directly reads the corresponding diagnostic information when a diagnostic service request is received, thereby improving the accuracy and efficiency of diagnosis.

[0081] FIG5 is a flow chart illustrating another embodiment of a vehicle diagnostic processing method provided herein. As shown in FIG5 , based on the above embodiment, the specific implementation method of step 103, "the service allocation module uploads the processed diagnostic service request to the diagnostic event management module or the data communication module based on the service request type in the processed diagnostic service request," or step 202, "the service allocation module uploads the target diagnostic service request to the diagnostic event management module or the data communication module based on the service request type in the target diagnostic service request," may further include:

[0082] Step 401: When the service allocation module determines that the service request type is an active service request type, the service allocation module uploads the processed diagnostic service request to the data communication module matching the active service request type.

[0083] In this embodiment, if it is determined that the service request type is an active service request type, the service allocation module uploads the processed diagnostic service request to the data communication module that matches the passive service request type.

[0084] In this embodiment, the service allocation module divides the target diagnostic service request type into an active service type and a passive service type according to the service request type in the processed diagnostic service request; and uploads the processed diagnostic service requests of different service types to the data communication module or the diagnostic event management module that matches the service request type. Compared with the prior art, the method of the present application divides the service request type into an active service type and a passive service type, so that the service allocation module can process the diagnostic service request more efficiently. At the same time, according to the different service types, the processed diagnostic service request is uploaded to the corresponding module, which can more reasonably allocate diagnostic services and improve the efficiency of the overall diagnostic service.

[0085] Accordingly, based on the above embodiment, the specific implementation method of step 104 "the diagnostic event management module or the data communication module performs corresponding service diagnostic processing according to the service request event when receiving the processed diagnostic service request" may also include:

[0086] Step 402: When receiving the processed diagnostic service request, the data communication module determines the working mode corresponding to the diagnostic service request according to the target controller in the processed diagnostic service request.

[0087] In this embodiment, when receiving the processed diagnostic service request, the data communication module parses the content of the processed diagnostic service request and obtains the target controller corresponding to the service request; thereby determining the working mode corresponding to the diagnostic service request according to the target controller.

[0088] Step 403: When the data communication module determines that the corresponding working mode of the diagnostic service request is the intra-domain working mode, the processed diagnostic service request is sent to the domain controller so that the domain controller can perform diagnostic operations according to the target diagnostic application corresponding to the service request event and obtain diagnostic information.

[0089] In this embodiment, when the data communication module determines that the corresponding working mode of the diagnostic service request is the intra-domain working mode, it interacts with the diagnostic application in the domain through the ara::com interface of the domain controller. After final processing, the diagnostic service request is provided to the intra-domain application interface for the application to call and obtain diagnostic information.

[0090] In this embodiment, the data communication module determines the operating mode corresponding to the diagnostic service request based on the target controller in the processed diagnostic service request; when it is determined that the corresponding operating mode of the diagnostic service request is an intra-domain operating mode, the processed diagnostic service request is sent to the domain controller for the corresponding target diagnostic application to perform diagnostic operations and obtain diagnostic information. Compared to the prior art, the method of the present application determines the operating mode corresponding to the diagnostic service request based on the target controller in the processed diagnostic service request; when the corresponding operating mode of the diagnostic service request is an intra-domain operating mode, the data communication module can send the processed diagnostic service request to the domain controller, which can improve the adaptability and efficiency of the diagnostic service.

[0091] Furthermore, based on the above embodiment, the method further includes:

[0092] Step 404: When the data communication module determines that the corresponding working mode of the diagnostic service request is the out-of-domain working mode, the processed diagnostic service request is sent to the out-of-domain controller so that the out-of-domain controller can perform diagnostic operations on the target diagnostic application corresponding to the service request event and obtain diagnostic information.

[0093] In this embodiment, when the data communication module determines that the corresponding working mode of the diagnostic service request is the out-of-domain working mode, it interacts with the ara:com interface of the out-of-domain controller through the ara::com interface of the current domain controller, and sends the processed diagnostic service request to the ara:com interface of the out-of-domain controller. Finally, the processed diagnostic service request received by the out-of-domain controller is provided to the out-of-domain application interface for the application to call and obtain diagnostic information.

[0094] In this embodiment, when it is determined that the corresponding working mode of the diagnostic service request is an out-of-domain working mode, the ara::com interface of the domain controller interacts with the ara:com interface of the out-of-domain controller, and the processed diagnostic service request is sent to the out-of-domain controller, so that the out-of-domain controller can perform diagnostic operations on the target diagnostic application corresponding to the service request event. Compared with the existing technology, the method of the present application realizes cross-domain transmission of diagnostic service requests, which helps to obtain more comprehensive diagnostic information, improve the accuracy and completeness of diagnosis, and also improve the scalability and flexibility of the system.

[0095] FIG6 is a schematic diagram of the structure of an embodiment of a diagnostic device provided by the present application. As shown in FIG6 , the diagnostic device 50 includes a diagnostic communication protocol module 51 , a service allocation module 52 , a diagnostic event management module 53 and a data communication module 54 .

[0096] The diagnostic communication protocol module 51 is used to obtain a diagnostic service request.

[0097] The diagnostic communication protocol module 51 is further configured to filter and unpack the diagnostic service request to obtain a processed diagnostic service request.

[0098] The service allocation module 52 is configured to upload the processed diagnostic service request to the diagnostic event management module or the data communication module according to the service request type in the processed diagnostic service request.

[0099] The diagnostic event management module 53 is configured to perform corresponding service diagnostic processing according to the service request event when receiving a processed diagnostic service request.

[0100] or,

[0101] The data communication module 54 is configured to perform corresponding service diagnosis processing according to the service request event when receiving the processed diagnosis service request.

[0102] A diagnostic device provided in an embodiment of the present application can execute the technical solution shown in any of the above method embodiments. Its implementation principles and beneficial effects are similar and will not be repeated here.

[0103] Furthermore, based on this embodiment, the diagnostic device 50 may further include a session judgment module 55, which is used to use the processed diagnostic service request as the target diagnostic service request if it is determined that the processed diagnostic service request meets the preconfigured filtering conditions, and report the target diagnostic service request to the service allocation module.

[0104] The service allocation module 52 is further configured to upload the target diagnostic service request to the diagnostic event management module or the data communication module according to the service request type in the target diagnostic service request.

[0105] A diagnostic device provided in an embodiment of the present application can execute the technical solution shown in any of the above method embodiments. Its implementation principles and beneficial effects are similar and will not be repeated here.

[0106] FIG7 is a schematic diagram of the structure of an embodiment of a vehicle provided by this application. As shown in FIG7 , vehicle 60 includes two domain controllers, namely domain controller 61 and domain controller 62 . Each domain controller is also equipped with a diagnostic device, wherein domain controller 61 corresponds to diagnostic device 63 , and domain controller 62 corresponds to diagnostic device 64 .

[0107] The diagnostic device in a vehicle provided in an embodiment of the present application can execute the technical solution shown in any of the above method embodiments. Its implementation principles and beneficial effects are similar and will not be repeated here.

[0108] FIG8 is a schematic diagram of the structure of an embodiment of an electronic device provided by the present application. As shown in FIG8 , a server 70 may include: a processor 71 and a memory 72 .

[0109] The processor 71 is in communication with the memory 72 , and the memory 72 is used to store computer-executable instructions. The processor 71 is configured to execute the technical solution in any of the aforementioned method embodiments by executing the computer-executable instructions stored in the memory 72 .

[0110] Optionally, the memory 72 may be independent or integrated with the processor 71. Optionally, when the memory 72 is a device independent of the processor 71, the electronic device 70 may further include a bus for connecting the above devices.

[0111] The electronic device is used to execute the technical solution in any of the aforementioned method embodiments, and its implementation principles and technical effects are similar and will not be repeated here.

[0112] An embodiment of the present application further provides a computer program product, including a computer program, which, when executed by a processor, implements the diagnostic processing method for the vehicle described in any one of the above embodiments.

[0113] An embodiment of the present application also provides a computer program, which, when executed by a processor, is used to implement the diagnostic processing method for the vehicle described in any of the above embodiments.

[0114] An embodiment of the present application also provides a computer-readable storage medium, which stores computer-executable instructions. When the computer-executable instructions are executed by a processor, they are used to implement the above-mentioned method. The implementation principle and technical effect are similar and will not be repeated here.

[0115] Specifically, the computer-readable storage medium may include: a U disk, a mobile hard disk, a read-only memory (ROM), a RAM, a disk or an optical disk, and other media that can store computer-executable instructions. Specifically, the computer-readable storage medium stores computer-executable instructions. When the computer-executable instructions are executed by a computer, the technical solution shown in the above method embodiment is executed. The specific implementation method and technical effect are similar and will not be repeated here.

[0116] It should be noted that for the aforementioned method embodiments, for the sake of simplicity, they are all expressed as a series of action combinations, but those skilled in the art should be aware that this application is not limited by the order of the actions described, because according to this application, certain steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also be aware that the embodiments described in this specification are all optional embodiments, and the actions and modules involved are not necessarily required by this application.

[0117] It should be further noted that, although the various steps in the flowchart are shown in sequence as indicated by the arrows, these steps are not necessarily performed in the order indicated by the arrows. Unless otherwise specified herein, there is no strict order restriction on the execution of these steps, and these steps may be performed in other orders. Moreover, at least a portion of the steps in the flowchart may include multiple sub-steps or multiple stages, and these sub-steps or stages are not necessarily performed at the same time, but may be performed at different times. The execution order of these sub-steps or stages is not necessarily to be performed in sequence, but may be performed in turn or alternately with other steps or at least a portion of the sub-steps or stages of other steps.

[0118] It should be understood that the above-described device embodiments are merely illustrative, and the device of the present application may also be implemented in other ways. For example, the division of units / modules in the above-described embodiments is merely a logical functional division, and actual implementations may employ other division methods. For example, multiple units, modules, or components may be combined or integrated into another system, or some features may be omitted or not implemented.

[0119] In addition, unless otherwise specified, the functional units / modules in the various embodiments of the present application may be integrated into a single unit / module, each unit / module may exist physically separately, or two or more units / modules may be integrated together. The aforementioned integrated units / modules may be implemented in the form of hardware or software program modules.

[0120] If the integrated unit / module is implemented in hardware, the hardware may be digital circuits, analog circuits, etc. The physical implementation of the hardware structure includes, but is not limited to, transistors, memristors, etc. Unless otherwise specified, the processor may be any appropriate hardware processor, such as a CPU, GPU, FPGA, DSP, and ASIC. Unless otherwise specified, the storage unit may be any appropriate magnetic storage medium or magneto-optical storage medium, such as resistive random access memory (RRAM), dynamic random access memory (DRAM), static random access memory (SRAM), enhanced dynamic random access memory (EDRAM), high-bandwidth memory (HBM), hybrid memory cube (HMC), etc.

[0121] If the integrated unit / module is implemented in the form of a software program module and sold or used as an independent product, it can be stored in a computer-readable memory. Based on this understanding, the technical solution of the present application, 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, which is stored in a memory and includes a number of instructions for enabling a computer device (which can be a personal computer, server or network device, etc.) to execute all or part of the steps of the various embodiments of the present application. The aforementioned memory includes various media that can store program codes, such as a USB flash drive, a read-only memory (ROM), a random access memory (RAM), a mobile hard disk, a magnetic disk or an optical disk.

[0122] In the above embodiments, the description of each embodiment has its own emphasis. For parts not described in detail in a particular embodiment, please refer to the relevant description of other embodiments. The technical features of the above embodiments can be combined in any way. To keep the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0123] Those skilled in the art will readily appreciate other embodiments of the present application after considering the specification and practicing the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of the present application that follow the general principles of the present application and include common knowledge or customary techniques in the art not disclosed herein. The description and examples are to be considered as exemplary only, and the true scope and spirit of the present application are indicated by the following claims.

[0124] It should be understood that the present application is not limited to the exact structure described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present application is limited only by the appended claims.

Claims

1. A vehicle diagnostic processing method, characterized in that: Applied to a diagnostic device, the diagnostic device includes: a diagnostic communication protocol module, a service allocation module, a diagnostic event management module and a data communication module, and the method includes: The diagnostic communication protocol module obtains a diagnostic service request; wherein the diagnostic service request includes a service request event and a service request type; The diagnostic communication protocol module filters and unpacks the diagnostic service request to obtain a processed diagnostic service request; The service allocation module uploads the processed diagnostic service request to the diagnostic event management module or the data communication module according to the service request type in the processed diagnostic service request; When receiving the processed diagnostic service request, the diagnostic event management module or the data communication module performs corresponding service diagnostic processing according to the service request event.

2. The method according to claim 1, characterized in that The diagnostic device further includes: a conversation judgment module, and the method further includes: If the session determination module determines that the processed diagnostic service request meets the preconfigured filtering condition, the processed diagnostic service request is used as the target diagnostic service request, and the target diagnostic service request is reported to the service allocation module; The service allocation module uploads the processed diagnostic service request to the diagnostic event management module or the data communication module according to the service request type in the processed diagnostic service request, including: The service allocation module uploads the target diagnostic service request to the diagnostic event management module or the data communication module according to the service request type in the target diagnostic service request.

3. The method according to claim 1 or 2, characterized in that The service allocation module uploads the processed diagnostic service request to the diagnostic event management module or the data communication module according to the service request type in the processed diagnostic service request, including: When the service allocation module determines that the service request type is a passive service request type, the service allocation module uploads the processed diagnostic service request to a diagnostic event management module that matches the passive service request type; or, When the service allocation module determines that the service request type is an active service request type, the service allocation module uploads the processed diagnostic service request to a data communication module that matches the active service request type.

4. The method according to any one of claims 1 to 3, characterized in that When the diagnostic event management module or the data communication module receives the processed diagnostic service request, the diagnostic event management module or the data communication module performs corresponding service diagnostic processing according to the service request event, including: When receiving the processed diagnostic service request, the diagnostic event management module reads diagnostic information related to the service request event from the diagnostic event management module according to the service request event, and obtains a fault code corresponding to the diagnostic information.

5. The method according to any one of claims 1 to 3, characterized in that When the diagnostic event management module or the data communication module receives the processed diagnostic service request, the diagnostic event management module or the data communication module performs corresponding service diagnostic processing according to the service request event, including: When receiving the processed diagnostic service request, the data communication module determines the working mode corresponding to the diagnostic service request according to the target controller in the processed diagnostic service request; When the data communication module determines that the corresponding working mode of the diagnostic service request is the intra-domain working mode, the processed diagnostic service request is sent to the domain controller so that the domain controller can perform diagnostic operations according to the target diagnostic application corresponding to the service request event and obtain diagnostic information.

6. The method according to claim 5, characterized in that The method further comprises: When the data communication module determines that the corresponding working mode of the diagnostic service request is an out-of-domain working mode, the processed diagnostic service request is sent to the out-of-domain controller so that the out-of-domain controller can perform diagnostic operations on the target diagnostic application according to the service request event and obtain diagnostic information.

7. A diagnostic device, characterized in that The diagnostic device includes a diagnostic communication protocol module, a service allocation module, a diagnostic event management module and a data communication module; Diagnostic communication protocol module, used to obtain diagnostic service requests; The diagnostic communication protocol module is further configured to filter and unpack the diagnostic service request to obtain a processed diagnostic service request; a service allocation module, configured to upload the processed diagnostic service request to the diagnostic event management module or the data communication module according to the service request type in the processed diagnostic service request; The diagnostic event management module is configured to, upon receiving the processed diagnostic service request, perform corresponding service diagnostic processing according to the service request event; or, The data communication module is configured to perform corresponding service diagnosis processing according to the service request event when receiving the processed diagnosis service request.

8. An electronic device, characterized in that: include: a processor, and a memory communicatively connected to the processor; The memory stores computer-executable instructions; The processor executes the computer-executable instructions stored in the memory to implement the method according to any one of claims 1 to 6.

9. A vehicle, characterized in that: The system comprises a domain controller and a diagnostic device provided in each domain controller; wherein the diagnostic device is used to implement the method according to any one of claims 1 to 6.

10. A computer-readable storage medium, characterized in that The computer-readable storage medium stores computer-executable instructions, which are used to implement the method according to any one of claims 1 to 6 when executed by a processor.

11. A computer program product, characterized in that The invention comprises a computer program, which implements the method according to any one of claims 1 to 6 when the computer program is executed by a processor.

12. A computer program, characterized in that When the computer program is executed by a processor, the method according to any one of claims 1 to 6 is implemented.

Images