Vehicle diagnosis method, device, system, equipment, medium and program product

Abstract

The invention relates to a vehicle diagnosis method, device, system and equipment, a medium and a program product, and relates to the technical field of automotive electronics. The method comprises the steps that a vehicle interacts with a browser client through a browser server, an access request generated by a diagnosis terminal through the browser client can be obtained, and after the access request is obtained, the vehicle can obtain diagnosis related resources according to a preset process or the requirement of the diagnosis terminal; and the information is provided for the diagnosis equipment through interaction between the browser server and the browser client. Through the mode, equipment such as a mobile phone or a computer capable of operating the browser client side can be used as a diagnosis terminal, and vehicle diagnosis related resources are obtained through interaction between the browser client side and the browser server side operating on the vehicle so as to complete diagnosis of the vehicle. According to the mode, the requirement for equipment serving as a diagnosis terminal is low, a professional diagnosis instrument does not need to be used, and the flexibility of vehicle diagnosis can be improved.

Description

Technical Field

[0001] The present invention relates to the field of automotive electronics technology, and in particular to a vehicle diagnostic method, device, system, equipment, medium and program product. Background Art

[0002] With the development of the automotive industry, vehicles have become highly complex mechatronic systems, integrating numerous electronic control units (ECUs) to achieve vehicle control and auxiliary entertainment functions. Vehicle diagnostics, the process of monitoring the status of a vehicle's ECUs and identifying faults, is crucial to vehicle operation.

[0003] Currently, vehicle diagnostics often require specialized diagnostic instruments, which use specialized software and protocols to access internal vehicle components and retrieve relevant data for diagnosis. However, this diagnostic approach places high demands on both equipment and operators, limiting diagnostic flexibility. Furthermore, updates to on-board diagnostic configurations require simultaneous updates to the instrument's software and protocols. Failure to do so could significantly impact the vehicle diagnostic process and lead to excessive diagnostic limitations. Summary of the Invention

[0004] One of the purposes of the present invention is to provide a vehicle diagnostic method, apparatus, system, device, medium and program product to solve the problem of excessive vehicle diagnostic limitations.

[0005] In order to achieve the above object, the technical solution adopted by the present invention is as follows:

[0006] A vehicle diagnostic method, applied to a vehicle, wherein a browser server is running in the vehicle, comprises:

[0007] Obtaining an access request from the browser client through interaction between the browser server and the browser client, wherein the browser client runs on the diagnostic terminal;

[0008] According to the access request, vehicle diagnosis related resources are provided to the diagnosis terminal through interaction between the browser server and the browser client, and the vehicle diagnosis related resources are used for diagnosis of the vehicle.

[0009] Furthermore, the vehicle diagnosis related resources are provided to the diagnostic terminal, including:

[0010] providing information of at least one accessible diagnostic object to the browser client via a browser transmission protocol;

[0011] receiving a diagnosis request for a target diagnosis object sent by the browser client, wherein the target diagnosis object is one of the at least one diagnosis object;

[0012] The corresponding diagnostic resource is obtained according to the diagnostic request, and the diagnostic resource is transmitted to the browser client through the browser transmission protocol.

[0013] Further, obtaining corresponding diagnostic resources according to the diagnostic request includes:

[0014] Determining, by a diagnostic management module or an adaptor for a service vehicle diagnostic (SOVD) architecture, a target diagnostic object from the at least one diagnostic object according to the diagnostic request, and generating a request message in a SOVD format according to the diagnostic request;

[0015] Obtaining a response message in a SOVD format corresponding to the request message from a node corresponding to the target diagnosis object, wherein the response message in the SOVD format includes a diagnostic resource corresponding to the diagnostic request;

[0016] Parse the response message to obtain the diagnostic resource corresponding to the diagnostic request.

[0017] Further, obtaining a response message in the SOVD format corresponding to the request message from the node corresponding to the target diagnosis object includes:

[0018] Converting the SOVD request message into a unified diagnostic service (UDS) request message.

[0019] Sending the request message in the UDS format to the node corresponding to the target diagnosis object, and obtaining a response message in the UDS format returned by the node, wherein the UDS response message includes the diagnosis resource corresponding to the diagnosis request;

[0020] The UDS response message is converted into a SOVD response message.

[0021] Furthermore, the vehicle is connected to the diagnostic terminal via a local area network, or the vehicle establishes a remote connection with the diagnostic terminal via a cloud server, and the local area network connection or the remote connection is used for interaction between the browser server and the browser client.

[0022] A vehicle diagnostic method, applied to a diagnostic terminal, wherein the diagnostic terminal runs a browser client, comprises:

[0023] Obtaining relevant information of a diagnosed vehicle through the browser client, and generating an access request for the vehicle based on the relevant information, wherein the vehicle has a browser server running;

[0024] Transmitting the access request to the vehicle through interaction between the browser client and the browser server, and receiving vehicle diagnosis-related resources provided by the vehicle;

[0025] The vehicle is diagnosed according to the vehicle diagnosis related resources.

[0026] Furthermore, before receiving the vehicle diagnosis related resources provided by the vehicle, the method further includes:

[0027] Obtaining information of at least one diagnostic object provided by the vehicle, and displaying the information through the browser client;

[0028] In response to obtaining a selection operation for a target diagnostic object from the at least one diagnostic object, generating a diagnosis request for the target diagnostic object;

[0029] The diagnostic request is transmitted to the vehicle via a browser transmission protocol.

[0030] A vehicle diagnostic device is applied to a vehicle, wherein a browser server is running in the vehicle, and the device comprises:

[0031] an acquisition module, configured to acquire an access request from the browser client through interaction between the browser server and the browser client, wherein the browser client runs on the diagnostic terminal;

[0032] The output module is used to provide vehicle diagnosis related resources to the diagnosis terminal according to the access request through the interaction between the browser server and the browser client, and the vehicle diagnosis related resources are used for diagnosis of the vehicle.

[0033] A vehicle diagnostic device, applied to a diagnostic terminal, wherein the diagnostic terminal runs a browser client, comprises:

[0034] an access module for obtaining relevant information of a diagnosed vehicle through the browser client and generating an access request for the vehicle based on the relevant information, wherein the vehicle has a browser server running therein;

[0035] a transmission module, configured to transmit the access request to the vehicle through interaction between the browser client and the browser server, and receive vehicle diagnosis-related resources provided by the vehicle;

[0036] A diagnosis module is used to diagnose the vehicle based on the vehicle diagnosis related resources.

[0037] An electronic device comprises: a processor, and a memory communicatively connected to the processor;

[0038] The memory stores computer-executable instructions;

[0039] The processor executes the computer-executable instructions stored in the memory to implement any one of the vehicle diagnostic methods described above.

[0040] A computer-readable storage medium comprises: computer-executable instructions stored in the computer-readable storage medium, wherein the computer-executable instructions are used to implement any of the above vehicle diagnostic methods when executed by a processor.

[0041] A computer program product comprises a computer program, wherein when the computer program is executed by a processor, the vehicle diagnosis method as described above is implemented.

[0042] The present invention provides the following benefits: A device capable of running a browser client, such as a mobile phone or computer, can be used as a diagnostic terminal. Through interaction between the browser client and a browser server running on the vehicle, vehicle diagnostic resources can be obtained to complete vehicle diagnosis. This approach has lower requirements for the device used as the diagnostic terminal, eliminates the need for specialized diagnostic equipment, and improves vehicle diagnostic flexibility. BRIEF DESCRIPTION OF THE DRAWINGS

[0043] Figure 1 A schematic diagram of the architecture of a vehicle diagnostic system provided by an exemplary embodiment of the present invention;

[0044] Figure 2 A vehicle diagnostic method according to an exemplary embodiment of the present invention is provided. Figure 1 ;

[0045] Figure 3 A vehicle diagnostic method according to an exemplary embodiment of the present invention is provided. Figure 2 ;

[0046] Figure 4 A vehicle diagnostic timing diagram provided by an exemplary embodiment of the present invention;

[0047] Figure 5 A schematic diagram of a browser page for vehicle diagnosis provided by an exemplary embodiment of the present invention;

[0048] Figure 6 A schematic diagram of a vehicle diagnostic network architecture provided by an exemplary embodiment of the present invention;

[0049] Figure 7 A schematic diagram of a vehicle diagnostic network connection provided by an exemplary embodiment of the present invention;

[0050] Figure 8 A schematic diagram of a vehicle diagnostic device provided by an exemplary embodiment of the present invention Figure 1 ;

[0051] Figure 9 A schematic diagram of a vehicle diagnostic device provided by an exemplary embodiment of the present invention Figure 2 ;

[0052] Figure 10 A schematic structural diagram of an electronic device provided by an exemplary embodiment of the present invention.

[0053] The above drawings have shown specific embodiments of the present invention, which will be described in more detail below. These drawings and the text description are not intended to limit the scope of the present invention in any way, but rather to illustrate the concept of the present invention to those skilled in the art by referring to specific embodiments. DETAILED DESCRIPTION

[0054] The following describes the embodiments of the present invention with reference to the accompanying drawings and preferred embodiments. Those skilled in the art will readily appreciate the other advantages and benefits of the present invention from the disclosure herein. The present invention may also be implemented or applied through various other specific embodiments, and the various details in this specification may be modified or altered based on different viewpoints and applications without departing from the spirit of the present invention. It should be understood that the preferred embodiments are intended only to illustrate the present invention and are not intended to limit the scope of protection of the present invention.

[0055] It should be noted that the illustrations provided in the following embodiments are merely schematic illustrations of the basic concept of the present invention. Therefore, the illustrations only show components related to the present invention and are not drawn according to the number, shape, and size of components in actual implementation. In actual implementation, the type, quantity, and proportion of each component may be changed arbitrarily, and the component layout may also be more complex.

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

[0057] The terms "comprises," "comprising," or any other variations thereof are intended to encompass non-exclusive inclusion, such that a process, method, product, or apparatus that includes a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such process, method, product, or apparatus. Without further limitation, the presence of additional identical or equivalent elements in a process, method, product, or apparatus that includes the elements is not precluded. For example, the terms "first," "second," etc., when used, are used to indicate names and do not imply any particular order.

[0058] With the development of the automotive industry, vehicles are integrating more and more hardware and software. Vehicle diagnostics can monitor the status of a vehicle's internal hardware and software components to determine whether they are functioning properly. Currently, vehicle diagnostics typically require specialized diagnostic equipment equipped with manufacturer-developed diagnostic software that accesses the vehicle's internal components based on specific protocols to read data and perform diagnostics.

[0059] Traditional diagnostic instruments usually take the form of a customized tablet computer with a wirelessly connected OBD (On-Board Diagnostics) plug. Software needs to be developed in the tablet computer for diagnostic communication with the vehicle and parsing diagnostic data. The connection method is a local physical connection.

[0060] This method, which relies on diagnostic instruments and diagnostic software, limits the flexibility of vehicle diagnosis. The diagnostic instrument must be operated by personnel familiar with the diagnostic software to perform diagnosis. In addition, the car manufacturer may also update the vehicle-side configuration. The diagnostic software and even the diagnostic instrument need to follow the vehicle-side configuration update. If there are vehicles with unupdated configurations and vehicles with updated configurations that need to be diagnosed at the same time, the diagnosis cannot be completed through the same diagnostic instrument, and there are too many diagnostic restrictions.

[0061] The inventors discovered that the reason why vehicle diagnosis relies on diagnostic instruments is that vehicle diagnosis requires obtaining diagnostic-related data from units such as the ECU (Electronic Control Unit) inside the vehicle. For traditional diagnostic methods, a diagnostic instrument is required to collect data from these internal units of the vehicle through specific communication methods and protocols, and perform diagnosis locally on the diagnostic instrument based on the collected data. As a diagnostic device, the diagnostic instrument must not only support specific communication methods and protocols, but also deploy diagnostic software that matches the vehicle to perform vehicle diagnosis, resulting in the diagnostic process being overly dependent on the diagnostic instrument.

[0062] Based on this, a technical concept has been proposed to improve the vehicle-side diagnostic architecture. This approach collects and uniformly converts diagnostic data from various internal vehicle units on the vehicle side, enabling the converted data to be transmitted and used via browser-supported methods. A browser server runs on the vehicle side, transmitting diagnostic data to a browser client external to the vehicle via the browser server and browser transmission. In this way, for vehicle diagnostics, devices such as mobile phones or computers that can run browser clients can be used as diagnostic terminals. Through interaction between the browser client and the browser server running on the vehicle, vehicle diagnostic resources can be obtained to complete the vehicle diagnosis. This approach places lower demands on the device used as the diagnostic terminal, eliminating the need for specialized diagnostic equipment and increasing the flexibility of vehicle diagnostics. Furthermore, the diagnostic terminal only needs to implement browser-related functions and does not need to update diagnostic configurations along with the vehicle side.

[0063] The above-mentioned application scenarios are only some examples. Those skilled in the art can expand the application according to their specific needs and scenarios. The embodiments of the present invention do not impose specific limitations on this. The following describes the vehicle diagnostic method, device, system, equipment, medium and program product according to exemplary embodiments of the present invention with reference to the accompanying drawings.

[0064] Figure 1 FIG1 is a schematic diagram of the architecture of a vehicle diagnostic system provided by an exemplary embodiment of the present invention. Figure 1 As shown, the vehicle diagnostic system may include a diagnostic terminal and a vehicle to be diagnosed.

[0065] The diagnostic terminal can be an electronic device such as a mobile phone, computer, or tablet computer, running a browser client. The browser client can generate diagnostic requests for diagnostic objects in the vehicle and send these requests to the browser server. It can also receive relevant diagnostic resources provided by the browser server and display them on the browser page.

[0066] The vehicle being diagnosed contains at least one diagnostic object, which can be an internal ECU or software entity. A diagnostic gateway is also deployed on the vehicle, acting as a browser server, receiving and parsing diagnostic requests from the browser client. Based on the diagnostic request, the diagnostic gateway retrieves relevant diagnostic resources from the corresponding diagnostic object within the vehicle and, acting as a browser server, sends these resources to the browser client.

[0067] In an embodiment of the present invention, the diagnostic gateway can be a software entity deployed on the vehicle-side operating system. It can be written in a cross-platform programming language and use a set of universal upper and lower layer software interfaces to be compatible with different vehicle operating systems, thereby achieving the versatility and portability of the diagnostic gateway. The diagnostic gateway can be compatible with browser-related protocols such as HTTP (Hypertext Transfer Protocol) to implement functions such as parsing requests generated by the browser client as a browser server. The diagnostic gateway can also be compatible with diagnostic protocols such as SOVD (Service-Oriented Vehicle Diagnostics) to achieve management of diagnostic objects in the vehicle, thereby realizing vehicle diagnosis-related functions.

[0068] In some possible implementations, the diagnostic gateway may include modules such as a browser server, a conversion module, and a diagnostic server. The diagnostic server can manage diagnostic objects such as ECU units and software entities in the vehicle and implement various diagnostic functions, including reading data such as fault codes, real-time status data, and ECU identification data. It can also include active tests such as component activation and actuator testing, or parameter calibration. The browser server can obtain the diagnostic request generated by the browser client and parse the request and forward it to the diagnostic server. The diagnostic server can identify the diagnostic object targeted by the diagnostic request and the diagnostic function to be performed based on the information forwarded by the browser server. The diagnostic server can implement the diagnostic function by interacting with the identified diagnostic object and forward the generated result data as a diagnostic-related resource to the browser server, which is then sent to the browser client by the browser server. The conversion module can be used to convert data of different protocols so that the diagnostic server can interact with the diagnostic object and the corresponding node.

[0069] For communication between the diagnostic terminal and the vehicle, the diagnostic terminal can establish a local area network (LAN) connection with the vehicle via a wired method such as an Ethernet cable, or by connecting to the vehicle's Wi-Fi. This allows the browser client running on the diagnostic terminal to communicate directly with the diagnostic gateway deployed on the vehicle via the LAN connection. In other possible implementations, the diagnostic terminal and the vehicle can also forward data through a cloud server, allowing the browser client running on the diagnostic terminal to communicate indirectly with the diagnostic gateway deployed on the vehicle via the cloud server.

[0070] Figure 2 A vehicle diagnostic method according to an exemplary embodiment of the present invention is provided. Figure 1 .like Figure 2 As shown, the method may include:

[0071] Step S201: obtaining an access request from the browser client through interaction between the browser server and the browser client.

[0072] The browser client runs on the diagnostic terminal.

[0073] The vehicle diagnostic method provided by the embodiment of the present invention may be executed by a vehicle being diagnosed, in which a diagnostic gateway may be deployed and a browser server may be running, and the browser server may be a submodule of the diagnostic gateway.

[0074] The browser client can generate an access request for the vehicle being diagnosed based on relevant information such as the vehicle identification number (VIN) of the vehicle being diagnosed, and can send the access request to the browser server via a browser protocol such as HTTP. The browser server can obtain the access request generated by the browser client based on the first interaction with the browser client.

[0075] Step S202 : providing vehicle diagnosis related resources to the diagnosis terminal through interaction between the browser server and the browser client according to the access request.

[0076] Among them, vehicle diagnosis related resources are used for vehicle diagnosis.

[0077] In an embodiment of the present invention, the access request generated by the browser client can be verified. If the verification is successful, an IP address can be allocated to the diagnostic terminal, so that the vehicle and the diagnostic terminal can perform a second interaction between the browser server and the browser client based on the allocated IP (Internet Protocol) address. The second interaction can be used to transmit data related to the diagnostic object between the browser server and the browser client.

[0078] Optionally, after the access request is verified, the vehicle can automatically perform diagnostic operations such as reading fault codes on some or all diagnostic objects according to a preset procedure, and transmit the results of the diagnostic operations as diagnostic resources to the diagnostic terminal through a second interaction; or, after the access request is verified, the vehicle can provide the diagnostic terminal with a list of some or all diagnostic objects or executable diagnostic operations and other content through a second interaction, execute corresponding diagnostic operations based on the request generated by the diagnostic terminal for these contents, and transmit the results of the diagnostic operations as diagnostic resources to the diagnostic terminal through a second interaction.

[0079] It should be noted that data interaction processes such as a first interaction and a second interaction can occur between the browser server and the browser client. The first interaction can be established based on the vehicle's public IP address and can be used for initial access to the vehicle by the diagnostic terminal. The second interaction can be established based on temporary IP addresses assigned to the diagnostic terminal and the vehicle and can be used to transmit diagnostic resources related to diagnostic objects within the vehicle, providing greater privacy and security.

[0080] For example, if the vehicle and the diagnostic terminal communicate directly over a local area network, a DHCP server can be running on the vehicle. The DHCP server can then assign an IP address to the diagnostic terminal, and the browser server can then provide diagnostic resources related to the diagnostic object (such as fault codes) to the browser client based on the IP address. DHCP (Dynamic Host Configuration Protocol) is a protocol that allows a server to dynamically assign an IP address and configuration information to a client.

[0081] For example, if the vehicle and the diagnostic terminal communicate indirectly through a cloud server, a DHCP server can run on the cloud server, and the DHCP server can assign IP addresses to the diagnostic terminal and the vehicle respectively, so that diagnostic resources related to the diagnostic object can be transmitted between the browser server and the browser client through the assigned IP address.

[0082] After the diagnostic terminal obtains the diagnostic related resources provided by the vehicle, it can be displayed through the browser page of the browser client. The diagnostic personnel can determine whether there is a fault in the vehicle or take further diagnostic operations based on the displayed content to complete the diagnosis of the vehicle.

[0083] In the above embodiment, the vehicle can obtain the access request generated by the diagnostic terminal through the browser client through the interaction between the browser server and the browser client. After receiving the access request, the vehicle can obtain diagnosis-related resources according to the preset process or according to the needs of the diagnostic terminal, and provide them to the diagnostic device through the interaction between the browser server and the browser client. In this way, a device that can run a browser client, such as a mobile phone or a computer, can be used as a diagnostic terminal. Through the interaction between the browser client and the browser server running on the vehicle, vehicle diagnosis-related resources can be obtained to complete the diagnosis of the vehicle. This method has low requirements for the device used as the diagnostic terminal, does not require the use of a professional diagnostic instrument, and can improve the flexibility of vehicle diagnosis.

[0084] Figure 3 A vehicle diagnostic method according to an exemplary embodiment of the present invention is provided. Figure 2 .like Figure 3 As shown, the process may include:

[0085] Step S301 : obtaining relevant information of a diagnosed vehicle through a browser client, and generating an access request for the vehicle based on the relevant information.

[0086] Among them, a browser server runs in the vehicle.

[0087] The vehicle diagnostic method provided in the embodiment of the present invention may be executed by a diagnostic terminal that runs a browser client. The diagnostic terminal may be an electronic device such as a mobile phone, a computer, or a tablet computer.

[0088] For example, the diagnostician can obtain vehicle identification information such as the vehicle's VIN code by scanning the barcode on the windshield of the diagnosed vehicle and enter it into the browser page of the browser client. After the browser client obtains the information through the browser page, it can generate an access request carrying the vehicle identification information.

[0089] In step S302 , the browser client interacts with the browser server to transmit the access request to the vehicle, and receives vehicle diagnosis-related resources provided by the vehicle.

[0090] Step S303: diagnose the vehicle based on vehicle diagnosis related resources.

[0091] Among them, vehicle diagnosis-related resources may include information such as the fault code and real-time status data of the diagnosis object. Diagnostic personnel can determine the vehicle's diagnosis results or perform the next diagnostic operation based on this information.

[0092] In the above embodiment, the diagnostic terminal can access the vehicle being diagnosed through a browser client. The browser client interacts with the browser server to obtain diagnostic resources provided by the vehicle for vehicle diagnosis. This approach places relatively low demands on the diagnostic terminal, requiring only the ability to run the browser client. This significantly reduces reliance on specialized equipment such as diagnostic instruments, alleviating limitations on vehicle diagnosis. Furthermore, the diagnostic terminal does not require the deployment of specialized vehicle diagnostic protocols and software, minimizing the risk of vehicle data leakage and enhancing security.

[0093] Figure 4 A vehicle diagnostic timing diagram is provided for an exemplary embodiment of the present invention. Figure 4 The interactive process in vehicle diagnosis only needs to be explained.

[0094] like Figure 4 As shown, the diagnostic gateway deployed on the vehicle can also include a diagnostic server. This diagnostic server can manage diagnostic objects such as ECU units and software entity units within the vehicle, including registering diagnostic object information and invoking diagnostic data and functions related to diagnostic objects. For example, the diagnostic server can record the registration information of diagnostic objects (such as diagnostic object 1, diagnostic object 2, etc.) in the vehicle's local database and can also read diagnostic data such as fault codes of diagnostic objects.

[0095] like Figure 4 As shown, the process of the vehicle providing vehicle diagnosis related resources to the diagnostic terminal may include:

[0096] S410: providing information of at least one accessible diagnostic object to a browser client via a browser transmission protocol.

[0097] S420: Receive a diagnosis request for a target diagnosis object sent by a browser client.

[0098] The target diagnostic object is one of the at least one diagnostic object.

[0099] S430: Obtain corresponding diagnostic resources according to the diagnostic request, and transmit the diagnostic resources to the browser client via the browser transmission protocol.

[0100] For example, a list of diagnostic objects in the vehicle can be obtained from the vehicle-side database. The list can include identification information of multiple diagnostic objects in the vehicle and diagnostic operations that can be performed, and the content in the list can be sent to the browser client via the HTTP protocol. The browser client will select a target diagnostic object based on the content sent this time to generate a diagnostic request. The diagnostic gateway can receive the request and hand it over to the browser server. The browser server can parse the request and forward the parsed content to the diagnostic server. The parsed content may include identification information of the target diagnostic object and diagnostic operations (the content may be in the browser message format). The diagnostic server can parse the content forwarded by the browser server to determine the corresponding target diagnostic object and the diagnostic operations that need to be performed on the target diagnostic object (such as reading fault codes, etc.). After the diagnostic server performs the diagnostic operation, it can send the operation results as diagnostic resources to the browser server. The browser server can generate page resources available to the browser based on the diagnostic resources sent by the diagnostic server, and send the page resources to the browser client via the HTTP protocol.

[0101] like Figure 4 As shown, before receiving the vehicle diagnosis related resources provided by the vehicle, the diagnostic terminal also includes:

[0102] S411 , obtaining information of at least one diagnostic object provided by the vehicle, and displaying the information through a browser client.

[0103] S412 : In response to obtaining a selection operation for a target diagnostic object from the at least one diagnostic object, generating a diagnosis request for the target diagnostic object.

[0104] S413: The diagnostic request is transmitted to the vehicle via the browser transmission protocol.

[0105] Figure 5 A schematic diagram of a vehicle diagnosis browser page provided by an exemplary embodiment of the present invention. Figure 5As shown, the diagnostic terminal can receive the information of the diagnostic object in the vehicle sent by the browser server, and the browser client can display this information through the browser page. Figure 5 As shown, the browser page can contain diagnostic objects such as Diagnostic Object 1, Diagnostic Object 2, Diagnostic Object 3, and Diagnostic Object 4 within the vehicle. These objects can be ECU units or software entities within the vehicle. On this page, a diagnostic object can be selected as the target diagnostic object by clicking the mouse and determining the corresponding diagnostic operation. Based on the selection result, the browser client can generate a diagnostic request and send it to the browser server via the HTTP protocol.

[0106] It is understandable that Figure 5 This is only an example scenario of the present invention. In other examples, the diagnostic operations and diagnostic objects can be displayed hierarchically in different pages. A hierarchical menu can also be set according to the domain controller or operating system to which the diagnostic object belongs to generate a corresponding page.

[0107] In one embodiment, obtaining corresponding diagnostic resources according to a diagnostic request includes:

[0108] S4301, through the diagnosis management module or the adaptor of the service vehicle diagnosis SOVD architecture, determine the target diagnosis object from at least one diagnosis object according to the diagnosis request, and generate a request message in the SOVD format according to the diagnosis request.

[0109] The Diagnostic Management (DM) module is a diagnostic solution based on the AUTOSAR DM framework. The SOVD (Software-Operated Vehicle) Adapter (SOVD) and the DM module can both manage diagnostic objects using the SOVD protocol.

[0110] S4302: Obtain a response message in the SOVD format corresponding to the request message from the node corresponding to the target diagnosis object.

[0111] The response message in the SOVD format includes the diagnostic resources corresponding to the diagnostic request.

[0112] S4303: parse the response message to obtain the diagnostic resource corresponding to the diagnostic request.

[0113] In this embodiment of the present invention, different diagnostic servers can be deployed based on the type of diagnostic object within the vehicle. If the diagnostic object is software based on the AUTOSAR AP architecture, the DM module (Diagnostic Management) is used as the diagnostic server. If the diagnostic object is software outside the AUTOSAR AP architecture, a SOVD Adaptor (adapter) is developed based on software-related information to serve as the diagnostic server. AUTOSAR (AUTomotive Open System Architecture) is an automotive electronic software architecture standard, and AUTOSAR AP (Adaptive Platform) is an architecture proposed for automotive high-performance computing (HPC).

[0114] Exemplarily, the vehicle's operating system can be equipped with two diagnostic servers, a DM module and a SOVD Adaptor. According to the information of the target diagnostic object carried in the diagnostic request, the corresponding diagnostic server (DM module or SOVD Adaptor) can be called to find the target diagnostic object and generate a SOVD request message for the diagnostic object. The request message carries the diagnostic operation performed on the target diagnostic object (such as reading fault codes, etc.). The diagnostic server can send the SOVD request message to the communication node corresponding to the target diagnostic object. After receiving the request message through the communication node, the target diagnostic object returns a response message. The diagnostic server can parse the response message to obtain the corresponding diagnostic resources (such as fault codes, etc.).

[0115] Vehicle diagnosis requires obtaining diagnostic data such as fault codes from diagnostic objects such as the ECU inside the vehicle. However, traditional diagnostic methods are limited by communication methods and protocols, and data transmission efficiency is low. It is necessary to increase diagnostic speed by minimizing the amount of transmitted data. As a diagnostic device, the diagnostic instrument must not only support specific communication methods and protocols, but also deploy diagnostic software and a local database that matches the vehicle to parse the original data on the vehicle side. As a result, vehicle diagnosis must rely on the diagnostic instrument, and the database is stored on the diagnostic instrument, which has poor data security.

[0116] In the above embodiment, a database and a diagnostic server for parsing diagnostic data can be deployed on the vehicle side, so that at least part of the diagnostic functions can be realized on the vehicle side. By deploying functions such as parsing diagnostic data and a database on the vehicle side, only the diagnosis-related configuration on the vehicle side can be updated, without updating the configuration of the diagnostic equipment, thereby reducing the amount of repetitive work.

[0117] In one embodiment, obtaining a response message in the SOVD format corresponding to the request message from the node corresponding to the target diagnosis object includes:

[0118] S43021: Convert the request message in the SOVD format into a request message in the unified diagnostic service UDS format.

[0119] Among them, UDS (Unified Diagnostic Services) is a diagnostic protocol used for units such as ECUs in vehicles.

[0120] S43022: Send a request message in the UDS format to the node corresponding to the target diagnosis object, and obtain a response message in the UDS format returned by the node.

[0121] The UDS response message contains the diagnostic resource corresponding to the diagnostic request. The node corresponding to the target diagnostic object can be the communication node of the target diagnostic object, which can be a DoIP node or a CAN node. DoIP (Diagnostic Communication over Internet Protocol) refers to a communication entity in the vehicle network that supports the DoIP protocol and can transmit diagnostic data via the vehicle Ethernet.

[0122] S43023 converts the UDS response message into a SOVD response message.

[0123] In an embodiment of the present invention, a diagnostic server can use the SOVD protocol to manage diagnostic objects such as ECUs, while these ECUs may use the UDS protocol. To address this situation, a conversion module can be used to convert data between the different protocols between the diagnostic server and the diagnostic object. When the diagnostic server generates an SOVD request message, the conversion module converts it into a UDS request message readable by the diagnostic object. The UDS request message is then sent via the corresponding communication node of the diagnostic object. The diagnostic object responds to the request message with a UDS response message, which is then converted into an SOVD response message by the conversion module and reported to the diagnostic server.

[0124] In one embodiment, the vehicle is connected to the diagnostic terminal via a local area network, or the vehicle establishes a remote connection with the diagnostic terminal via a cloud server, wherein the local area network connection or the remote connection is used for interaction between the browser server and the browser client.

[0125] In an embodiment of the present invention, the diagnostic terminal can establish a local area network connection with the vehicle through a wired method such as a network cable, or can establish a local area network connection with the vehicle by connecting to the vehicle's WiFi, so that the browser client running on the diagnostic terminal can communicate directly with the diagnostic gateway deployed on the vehicle through the local area network connection.

[0126] In some possible implementations, the diagnostic terminal and vehicle can also forward data through a cloud server, establishing a remote connection and enabling indirect communication between the browser server and browser client. In this case, the cloud server only needs to implement DNS network address resolution and HTTP data relay, without having to perform vehicle diagnostic analysis based on the forwarded data.

[0127] For example, a car company can set up a cloud server for data forwarding. The cloud server can store the identification information and public IP addresses of multiple vehicles. Diagnostic personnel can generate an access request by filling in the identification information of a vehicle to be diagnosed on the web page of the browser client and send it to the cloud server. The cloud server performs DNS network address resolution based on the request to determine the corresponding vehicle to be diagnosed, and forwards the access request to the diagnostic gateway of the vehicle to be diagnosed based on the public IP address of the vehicle to be diagnosed. The diagnostic gateway sends the received access request to the internal browser server. Optionally, after forwarding the access request, the cloud server can also allocate a temporary IP address to the diagnostic terminal and the vehicle to be diagnosed through the DHCP Server (Dynamic Host Configuration Protocol Server). The diagnostic terminal and the vehicle to be diagnosed can continue to forward data through the cloud server based on the temporary IP address.

[0128] In the above embodiment, the diagnostic terminal and the vehicle being diagnosed can communicate indirectly through a cloud server. The cloud server is only used to identify the communicating parties and forward data based on the browser protocol. Neither the cloud server nor the diagnostic terminal performs diagnostic data parsing functions. This way, when diagnostic functions on the vehicle require updates, neither the cloud server nor the diagnostic terminal requires software changes; they only need to ensure the normal operation of the browser, significantly reducing the workload for software updates.

[0129] To further illustrate the application of the present invention, specific examples are provided below for illustration.

[0130] Figure 6 A schematic diagram of a vehicle diagnostic network architecture is provided for an exemplary embodiment of the present invention. In this example, the diagnostic system may include the vehicle being diagnosed, a diagnostic terminal, and an OEM cloud diagnostic server. The diagnostic terminal may be a mobile device such as a mobile phone, which can be used to run a browser client. The term "OEM" (Original Equipment Manufacturer) may represent the vehicle manufacturer.

[0131] Normally, diagnosticians can use remote diagnosis. After powering on the vehicle, they open a browser on their phone, tablet, or computer, log in to the OEM's cloud diagnostic server, enter the VIN code, or use a camera to scan the VIN barcode on the windshield to connect to the vehicle via the Internet. Diagnostic operations can be performed on the vehicle using buttons on the web page. When the vehicle's external network access function is limited or fails, local diagnostic access can be performed by turning on the vehicle's Wi-Fi, connecting the terminal device to Wi-Fi, or using an Ethernet cable to connect to the vehicle's OBD port for local diagnosis.

[0132] The vehicle being diagnosed can deploy a diagnostic gateway on the vehicle operating system. The diagnostic gateway is a software entity deployed on the vehicle operating system. It can be written in a cross-platform programming language and uses a set of universal upper and lower layer software interfaces to be compatible with different vehicle operating systems to achieve the universality and portability of the diagnostic gateway and reduce the cost of software development. The software interface is covered by the present invention and will not be described in detail. The diagnostic gateway needs to be compatible with the SOVD diagnostic protocol and the universal HTTP protocol. The SOVD protocol can implement most of the current diagnostic functions and can be compatible with traditional vehicle electronic and electrical architectures through protocol conversion software. This protocol is more suitable for vehicle diagnostic usage scenarios; the universal HTTP protocol can be used to enable web browsers to communicate normally with the vehicle-side diagnostic gateway through the external network or local area network, as well as to implement OEM-defined functions that are not covered by the SOVD protocol.

[0133] During remote diagnosis, the cloud server only needs to implement DNS network address resolution and HTTP data relay forwarding without paying attention to specific functional logic. During local diagnosis, it does not need to go through the OEM cloud diagnostic server. When updating diagnostic-related functions on the vehicle side, the cloud server does not need to make any software changes.

[0134] The diagnostic gateway acts as a browser server and forwards vehicle diagnostic resources provided by the in-vehicle SOVD server to the browser client. Specifically, the diagnostic gateway can include modules such as the SOVD edge node, TLS authentication terminal, HTTP reverse proxy, and mDNS server.

[0135] OVD edge node: responsible for network connection with external diagnostic equipment or OEM diagnostic server

[0136] TLS authentication terminal: responsible for performing TLS two-way authentication with external devices or servers to ensure vehicle and data security.

[0137] HTTP reverse proxy: routes external SOVD requests to the SOVD server inside the vehicle.

[0138] mDNS server: used to resolve the vehicle-side LAN IP address corresponding to the URL in the request.

[0139] In addition, the diagnostic gateway can also provide resources for the browser to access the basic URL page of the vehicle through the HTTP protocol: the page needs to provide a hierarchy of vehicle components and a list of diagnostic entities and selection buttons to facilitate users to select diagnostic objects.

[0140] The diagnostic gateway can also deploy SOVD Adaptor and AUTOSAR DM modules based on the type of software entity in the vehicle's operating system (VMS) where the gateway resides. The SOVD Adaptor and AUTOSAR DM modules function like the SOVD Server within the vehicle, providing diagnostic resources for components or software entities such as the adapted ECU. AUTOSAR AP software uses the DM module, while non-AUTOSAR software requires the development of a SOVD Adaptor.

[0141] The diagnostic gateway can also deploy a software module for converting SOVD to UDS (i.e. Figure 6 The SOVD2UDS module in the HPC is used to adapt to traditional Doip nodes and CAN nodes in the vehicle. This software module is developed according to the SOVD API specification, converting SOVD requests to and from UDS. OEMs can customize UDS services not covered by SOVD. When adapting to CAN nodes, it's important to note that if the SoC chip in the HPC lacks a CAN transceiver, forwarding must be done through the MCU.

[0142] Figure 7 A vehicle diagnostic network connection diagram is provided for an exemplary embodiment of the present invention. Figure 7 As shown, there are multiple ways to connect a diagnostic terminal such as a mobile phone or a computer to a vehicle.

[0143] 1. Network cable connection: The mobile phone or tablet uses an OTG network card, and the laptop uses the RJ45 port to connect to the TX port of the vehicle's OBD using a network cable for local wired diagnosis.

[0144] 2. Local WIFI LAN connection: The car computer turns on the WIFI hotspot, and the mobile device connects to the car computer hotspot.

[0145] 3. Remote connection: Use a browser on a PC, tablet, or mobile phone to enter the address of the OEM's remote diagnostic server, log in to your account, and enter the vehicle's VIN code to connect to the vehicle's diagnostic gateway.

[0146] Regarding the connection, the requirements for the diagnostic gateway are:

[0147] 1. The HPC as a diagnostic gateway supports AutoIP (RFC3927) and DHCP client functions for IP address allocation on the local area network. When remote diagnosis is performed through the OEM server, the DHCP server in the server assigns IP addresses to the diagnostic equipment and the vehicle.

[0148] 2. Considering the network security requirements on the vehicle side, it is necessary to directly connect the OBD port to the diagnostic gateway as much as possible to achieve isolation between the in-vehicle network and the external network. If it passes through a switch, the switch forwarding configuration must be used to prevent the OBD port messages from being forwarded to ports other than the diagnostic gateway.

[0149] Diagnostic Conflict Detection Module: The vehicle retains the traditional OBD diagnostic port to meet regulatory requirements for access to testing equipment and serve as a backup diagnostic solution in the event of vehicle computer damage. After a diagnostic instrument is connected to the OBD port, the vehicle computer's diagnostic software detects the presence of a local instrument through diagnostic messages, changes in the Ethernet activation line level, or the OBD port network link status. When a local instrument is connected, the diagnostic gateway stops sending diagnostic information to other nodes in the vehicle to avoid diagnostic conflicts. When the diagnostic gateway receives an access request, it returns a fixed-format response, notifying the user that a higher-priority diagnostic function is currently executing.

[0150] Figure 8 A schematic diagram of a vehicle diagnostic device provided by an exemplary embodiment of the present invention Figure 1 .like Figure 8 As shown, the vehicle diagnostic device 800 may include:

[0151] An acquisition module 801 is configured to acquire an access request from a browser client through interaction between the browser server and the browser client, wherein the browser client runs on a diagnostic terminal;

[0152] The output module 802 is configured to provide vehicle diagnosis related resources to the diagnosis terminal according to the access request through interaction between the browser server and the browser client, wherein the vehicle diagnosis related resources are used for diagnosis of the vehicle.

[0153] In some possible implementations, the output module 802 can be used to: provide information of at least one accessible diagnostic object to the browser client via a browser transmission protocol; receive a diagnostic request for a target diagnostic object sent by the browser client, where the target diagnostic object is one of the at least one diagnostic object; obtain corresponding diagnostic resources based on the diagnostic request, and transmit the diagnostic resources to the browser client via a browser transmission protocol.

[0154] In some possible implementations, the output module 802 can be used to: determine the target diagnostic object from the at least one diagnostic object according to the diagnostic request through a diagnostic management module or an adaptor of the service vehicle diagnosis SOVD architecture, and generate a request message in the SOVD format according to the diagnostic request; obtain a response message in the SOVD format corresponding to the request message from the node corresponding to the target diagnostic object, the response message in the SOVD format including the diagnostic resources corresponding to the diagnostic request; parse the response message to obtain the diagnostic resources corresponding to the diagnostic request.

[0155] In some possible implementations, the output module 802 can be used to: convert the request message in the SOVD format into a request message in the unified diagnostic service UDS format; send the request message in the UDS format to the node corresponding to the target diagnostic object, and obtain the response message in the UDS format returned by the node, wherein the UDS response message includes the diagnostic resources corresponding to the diagnostic request; and convert the UDS response message into a SOVD response message.

[0156] Figure 9 A schematic diagram of a vehicle diagnostic device provided by an exemplary embodiment of the present invention Figure 2 .like Figure 9 As shown, the vehicle diagnostic device 900 may include:

[0157] Access module 901, configured to obtain relevant information of a diagnosed vehicle through the browser client, and generate an access request for the vehicle based on the relevant information, wherein the vehicle has a browser server running therein;

[0158] a transmission module 902 for transmitting the access request to the vehicle through interaction between the browser client and the browser server, and receiving vehicle diagnosis-related resources provided by the vehicle;

[0159] The diagnosis module 903 is configured to diagnose the vehicle based on the vehicle diagnosis related resources.

[0160] In some possible implementations, the transmission module 902 can be used to: obtain information of at least one diagnostic object provided by the vehicle and display it through the browser client; generate a diagnostic request for the target diagnostic object in response to obtaining a selection operation for the target diagnostic object among the at least one diagnostic object; and transmit the diagnostic request to the vehicle through the browser transmission protocol.

[0161] The vehicle diagnostic device provided in this embodiment is used to execute the technical solution in any of the aforementioned method embodiments. Its implementation principles and technical effects are similar and will not be described in detail here.

[0162] It should be understood that the above-described device embodiments are merely illustrative, and the devices of the present invention may 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 alternative divisions. For example, multiple units, modules, or components may be combined or integrated into another system, or some features may be omitted or not implemented.

[0163] In addition, unless otherwise specified, the functional units / modules in the various embodiments of the present invention 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.

[0164] Figure 10 FIG1 is a schematic diagram of the structure of an electronic device provided by an exemplary embodiment of the present invention. Figure 10 As shown, the electronic device 100 includes:

[0165] Processor 101, memory 102, and communication interface 103;

[0166] The memory 102 is used to store executable instructions of the processor 101; the executable instructions may be computer-executable instructions;

[0167] The processor 101 is configured to execute the technical solution in any of the aforementioned method embodiments by executing the executable instructions.

[0168] Optionally, the memory 102 may be independent or integrated with the processor 101 .

[0169] Optionally, when the memory 102 is a device independent of the processor 101, the electronic device 100 may further include:

[0170] The bus 104 , the memory 102 and the communication interface 103 are connected to the processor 101 via the bus 104 and communicate with each other. The communication interface 103 is used to communicate with other devices.

[0171] Optionally, the communication interface 103 may be implemented using a transceiver. The communication interface is used to enable communication between the database access device and other devices (e.g., a client, a read-write library, and a read-only library). The memory may include random access memory (RAM) and may also include non-volatile memory (non-volatile memory), such as at least one disk storage device.

[0172] Bus 104 may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus. Buses can be categorized as address buses, data buses, and control buses. For ease of illustration, the figure uses only one line, but this does not imply that there is only one bus or only one type of bus.

[0173] The above-mentioned processor can be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; it can also be a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, and discrete hardware components.

[0174] 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.

[0175] An embodiment of the present invention further provides a readable storage medium, which may be a computer-readable storage medium having a computer program stored thereon. When the computer program is executed by a processor, the technical solution provided by any of the aforementioned method embodiments is implemented.

[0176] An embodiment of the present invention further provides a computer program product, including a computer program, which is used to implement the technical solution provided by any of the aforementioned method embodiments when executed by a processor.

[0177] Those skilled in the art will appreciate that all or part of the steps in the above-described method embodiments can be implemented using hardware associated with program instructions. The aforementioned program can be stored in a computer-readable storage medium. When executed, the program performs the steps of the above-described method embodiments. The aforementioned storage medium includes various media capable of storing program code, such as ROM, RAM, magnetic disks, or optical disks.

[0178] 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.

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

[0180] The above embodiments are only preferred embodiments for fully illustrating the present invention, and the protection scope of the present invention is not limited thereto. Any equivalent substitution or modification made by those skilled in the art based on the present invention is within the protection scope of the present invention.

Claims

1. A vehicle diagnostic method, characterized in that: Applied to a vehicle, wherein a browser server is running in the vehicle, the method includes: Obtaining an access request from the browser client through interaction between the browser server and the browser client, wherein the browser client runs on the diagnostic terminal; According to the access request, vehicle diagnosis related resources are provided to the diagnosis terminal through interaction between the browser server and the browser client, and the vehicle diagnosis related resources are used for diagnosis of the vehicle.

2. The vehicle diagnostic method according to claim 1, wherein: The providing vehicle diagnosis related resources to the diagnostic terminal includes: providing information of at least one accessible diagnostic object to the browser client via a browser transmission protocol; receiving a diagnosis request for a target diagnosis object sent by the browser client, wherein the target diagnosis object is one of the at least one diagnosis object; The corresponding diagnostic resource is obtained according to the diagnostic request, and the diagnostic resource is transmitted to the browser client through the browser transmission protocol.

3. The vehicle diagnostic method according to claim 2, wherein: The obtaining corresponding diagnostic resources according to the diagnostic request includes: Determining, by a diagnostic management module or an adaptor for a service vehicle diagnostic (SOVD) architecture, a target diagnostic object from the at least one diagnostic object according to the diagnostic request, and generating a request message in a SOVD format according to the diagnostic request; Obtaining a response message in a SOVD format corresponding to the request message from a node corresponding to the target diagnosis object, wherein the response message in the SOVD format includes a diagnostic resource corresponding to the diagnostic request; Parse the response message to obtain the diagnostic resource corresponding to the diagnostic request.

4. The vehicle diagnostic method according to claim 3, characterized in that: The obtaining, from the node corresponding to the target diagnosis object, a response message in the SOVD format corresponding to the request message, includes: Converting the SOVD request message into a unified diagnostic service (UDS) request message. Sending the request message in the UDS format to the node corresponding to the target diagnosis object, and obtaining a response message in the UDS format returned by the node, wherein the UDS response message includes the diagnosis resource corresponding to the diagnosis request; The UDS response message is converted into a SOVD response message.

5. The vehicle diagnostic method according to any one of claims 1 to 4, characterized in that: The vehicle is connected to the diagnostic terminal via a local area network, or the vehicle establishes a remote connection with the diagnostic terminal via a cloud server. The local area network connection or the remote connection is used for interaction between the browser server and the browser client.

6. A vehicle diagnostic method, characterized in that: Applied to a diagnostic terminal running a browser client, the method includes: Obtaining relevant information of a diagnosed vehicle through the browser client, and generating an access request for the vehicle based on the relevant information, wherein the vehicle has a browser server running; Transmitting the access request to the vehicle through interaction between the browser client and the browser server, and receiving vehicle diagnosis-related resources provided by the vehicle; The vehicle is diagnosed according to the vehicle diagnosis related resources.

7. The vehicle diagnostic method according to claim 6, characterized in that: Before receiving the vehicle diagnosis related resources provided by the vehicle, the method further includes: Obtaining information of at least one diagnostic object provided by the vehicle, and displaying the information through the browser client; In response to obtaining a selection operation for a target diagnostic object from the at least one diagnostic object, generating a diagnosis request for the target diagnostic object; The diagnostic request is transmitted to the vehicle via a browser transmission protocol.

8. A vehicle diagnostic device, characterized in that: Applied to a vehicle, wherein a browser server is running in the vehicle, the device comprises: an acquisition module, configured to acquire an access request from the browser client through interaction between the browser server and the browser client, wherein the browser client runs on the diagnostic terminal; The output module is used to provide vehicle diagnosis related resources to the diagnosis terminal according to the access request through the interaction between the browser server and the browser client, and the vehicle diagnosis related resources are used for diagnosis of the vehicle.

9. A vehicle diagnostic device, characterized in that: Applied to a diagnostic terminal running a browser client, the device includes: an access module for obtaining relevant information of a diagnosed vehicle through the browser client and generating an access request for the vehicle based on the relevant information, wherein the vehicle has a browser server running therein; and a transmission module for transmitting the access request to the vehicle through interaction between the browser client and the browser server, and receiving vehicle diagnosis-related resources provided by the vehicle; A diagnosis module is used to diagnose the vehicle based on the vehicle diagnosis related resources.

10. A vehicle diagnostic system comprising: Diagnostic terminals and vehicles equipped with diagnostic gateways; The vehicle contains at least one diagnostic object; The diagnostic terminal runs a browser client, the browser client is used to generate a diagnostic request for the diagnostic object, and the browser client is also used to display the diagnostic resources provided by the browser server through a browser page; The diagnostic gateway is used to obtain the diagnostic resource corresponding to the diagnostic request and transmit it to the browser client through the browser transmission protocol.

11. The vehicle diagnostic system according to claim 10, characterized in that: The diagnostic gateway includes a browser server, a conversion module and a diagnostic server; The browser server is used to forward the diagnostic request to the diagnostic server and receive the diagnostic resource corresponding to the diagnostic request reported by the diagnostic server; The diagnostic server is configured to convert the diagnostic request through the conversion module so that the converted request can be received by the node corresponding to the diagnostic object, and is further configured to obtain corresponding diagnostic resources from the node.

12. 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 7.

13. 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 7 when executed by a processor.

14. 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 7 when being executed by a processor.

Images