A vehicle diagnosis method, device, server, and computer storage medium

Abstract

The present application discloses a vehicle diagnosis method, device, server, and computer storage medium, which are used to enable users with different identities to diagnose a vehicle with different focuses, thereby improving the user experience. The method of the present application includes: obtaining a diagnosis request sent by a client, where the diagnosis request includes a user identifier of the client; determining the user category of the client according to the user identifier; determining a target diagnosis process corresponding to the user category according to the user category; and diagnosing a target vehicle according to the target diagnosis process.

Description

Technical Field

[0001] This application relates to the field of vehicle diagnosis, and particularly to a vehicle diagnosis method, device, server, and computer storage medium. Background Art

[0002] With the increasing popularity of automobiles, the automotive service market has been continuously expanding. Automotive repair companies have an ever-growing need for rapid vehicle fault location. Additionally, for vehicle owners, quickly understanding the vehicle condition and fault information helps in timely vehicle inspection and maintenance.

[0003] Currently, vehicle diagnosis is generally carried out through a device tablet configured by equipment manufacturers. After downloading relevant vehicle models' software, it is connected to a diagnostic adapter via wireless or wired means for vehicle fault diagnosis. In the existing diagnosis methods, the diagnosis process is fixed, not user-friendly, and the user experience is poor. Summary of the Invention

[0004] Embodiments of this application provide a vehicle diagnosis method, device, server, and computer storage medium, enabling users with different identities to diagnose a vehicle with different focuses, thereby enhancing the user experience.

[0005] In a first aspect of the embodiments of this application, a vehicle diagnosis method is provided, including:

[0006] Obtain a diagnosis request sent by a client, where the diagnosis request includes the user identifier of the client;

[0007] Determine the user category of the client according to the user identifier;

[0008] Determine a target diagnosis process corresponding to the user category according to the user category;

[0009] Diagnose a target vehicle according to the target diagnosis process.

[0010] In a first possible implementation manner of the first aspect, the user categories of the client include a professional user category and an ordinary user category;

[0011] When the user category of the client is the professional user category, the target diagnosis process is a professional diagnosis process;

[0012] When the user category of the client is the ordinary user category, the target diagnosis process is an ordinary diagnosis process.

[0013] In a first case of the first possible implementation manner of the first aspect, the professional diagnosis process includes:

[0014] Obtain the basic information of the target vehicle;

[0015] Perform a full-system diagnosis on the target vehicle to obtain a full-system diagnosis result;

[0016] Generate a diagnostic report before repair based on the full-system diagnosis result;

[0017] Repair the target vehicle according to the full-system diagnosis result;

[0018] After the repair is completed, perform a full-system diagnosis on the target vehicle again to generate a diagnostic report after repair.

[0019] In the second case of the first possible implementation manner of the first aspect, the general diagnostic process includes:

[0020] Obtain the historical information of the target vehicle, where the historical information includes historical diagnostic record information, maintenance information records, and vehicle mileage information;

[0021] Determine the vehicle system to be detected according to the historical information;

[0022] Diagnose the vehicle system to be detected;

[0023] Generate a diagnostic report according to the result of the diagnosis.

[0024] In the second possible implementation manner of the first aspect, before obtaining the diagnostic request sent by the client, the method further includes:

[0025] Receive a registration request sent by the client, where the registration request carries the user identification and user category of the client;

[0026] Establish a mapping relationship between the user identification of the client and the user category;

[0027] The determining the user category of the client according to the user identification includes:

[0028] Determine the user category of the client according to the user identification and the mapping relationship.

[0029] In the third possible implementation manner of the first aspect, the determining the user category of the client according to the user identification includes:

[0030] Send a user category selection pop-up window to the client according to the user identification;

[0031] Determine the user category of the client according to the user category selection result returned by the client.

[0032] In the first aspect of the embodiments of the present application, in the first possible implementation manner of the first aspect, in the first case of the first possible implementation manner of the first aspect, in the second case of the first possible implementation manner of the first aspect, in the second possible implementation manner of the first aspect, in the third possible implementation manner of the first aspect, after receiving the diagnostic request sent by the receiving client, the method further includes:

[0033] Establish a communication connection with the in-vehicle device according to the diagnostic request;

[0034] The diagnosing the vehicle according to the target diagnostic process includes:

[0035] Control the in-vehicle device to diagnose the target vehicle according to the target diagnostic process;

[0036] Receive the diagnostic result sent by the in-vehicle device.

[0037] A vehicle diagnostic device is provided in the second aspect of the embodiments of the present application, including:

[0038] An acquisition unit, configured to acquire a diagnostic request sent by a client, where the diagnostic request includes a user identifier of the client;

[0039] A first determination unit, configured to determine a user category of the client according to the user identifier;

[0040] A second determination unit, configured to determine a target diagnostic process corresponding to the user category according to the user category;

[0041] A diagnosis unit, configured to diagnose a target vehicle according to the target diagnostic process.

[0042] In the first possible implementation manner of the second aspect, the user categories of the client include a professional user category and an ordinary user category;

[0043] When the user category of the client is the professional user category, the target diagnostic process is a professional diagnostic process;

[0044] When the user category of the client is the ordinary user category, the target diagnostic process is an ordinary diagnostic process.

[0045] In the first case of the first possible implementation manner of the second aspect, the professional diagnostic process includes:

[0046] Obtain basic information of the target vehicle;

[0047] Perform a full-system diagnosis on the target vehicle to obtain a full-system diagnostic result;

[0048] Generate a diagnostic report before maintenance according to the full-system diagnostic results;

[0049] Repair the target vehicle according to the full-system diagnostic results;

[0050] After completing the repair, perform a full-system diagnosis on the target vehicle again to generate a diagnostic report after maintenance.

[0051] In the second case of the first possible implementation manner of the second aspect, the general diagnostic process includes:

[0052] Obtain the historical information of the target vehicle, where the historical information includes historical diagnostic record information, maintenance information records, and vehicle mileage information;

[0053] Determine the vehicle system to be detected according to the historical information;

[0054] Diagnose the vehicle system to be detected;

[0055] Generate a diagnostic report according to the results of the diagnosis.

[0056] In the second possible implementation manner of the second aspect, the diagnostic device further includes:

[0057] A registration unit, configured to receive a registration request sent by a client, where the registration request carries a user identifier and a user category of the client;

[0058] An establishment unit, configured to establish a mapping relationship between the user identifier of the client and the user category;

[0059] The first determination unit is specifically configured to:

[0060] Determine the user category of the client according to the user identifier and the mapping relationship.

[0061] In the third possible implementation manner of the second aspect, the first determination unit is further specifically configured to:

[0062] Send a user category selection pop-up window to the client according to the user identifier;

[0063] Determine the user category of the client according to the user category selection result returned by the client.

[0064] In the second aspect, the first possible implementation manner of the second aspect, the first case of the first possible implementation manner of the second aspect, the second case of the first possible implementation manner of the second aspect, the second possible implementation manner of the second aspect, and the third possible implementation manner of the second aspect of the embodiments of the present application, the diagnostic device further includes:

[0065] A communication unit for establishing a communication connection with a vehicle-mounted device according to the diagnosis request;

[0066] The diagnosis unit is specifically configured to:

[0067] Control the vehicle-mounted device to diagnose the target vehicle according to the target diagnosis process;

[0068] Receive the diagnosis result sent by the vehicle-mounted device.

[0069] A third aspect of the embodiments of the present application provides a server, the server includes:

[0070] A processor, a memory, an input / output unit, and a bus;

[0071] The processor is connected to the memory, the input / output unit, and the bus;

[0072] The memory stores a program, and the processor calls the program to execute the vehicle diagnosis method in the first aspect and any optional one in the first aspect.

[0073] A fourth aspect of the embodiments of the present application provides a computer-readable storage medium, on which a program is stored, and when the program is executed on a computer, it executes the vehicle diagnosis method in the first aspect and any optional one in the first aspect.

[0074] It can be seen from the above technical solutions that the embodiments of the present application have the following advantages:

[0075] Before a user performs an automotive diagnosis through a client, the user can first set their own user category. Before the diagnosis, the device will determine different target diagnosis processes based on the different client user categories, and then diagnose the vehicle according to the target diagnosis process. The diagnosis items involved in different target diagnosis processes are different, so that users with different identities can diagnose the vehicle with different focuses, thereby improving the user experience. BRIEF DESCRIPTION OF THE DRAWINGS

[0076] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the following will briefly introduce the drawings required for the description of the embodiments. Obviously, the drawings in the following description are only some embodiments of the present application. For those of ordinary skill in the art, without creative efforts, other drawings can also be obtained based on these drawings.

[0077] Figure 1 It is a schematic diagram of the architecture of the vehicle diagnosis system provided by the embodiments of the present application;

[0078] Figure 2Schematic flowchart of an embodiment of the vehicle diagnosis method provided by an embodiment of the present application;

[0079] Figure 3 Schematic flowchart of another embodiment of the vehicle diagnosis method provided by an embodiment of the present application;

[0080] Figure 4 Schematic flowchart of another embodiment of the vehicle diagnosis method provided by an embodiment of the present application;

[0081] Figure 5 Schematic structural diagram of an embodiment of the vehicle diagnosis device provided by an embodiment of the present application;

[0082] Figure 6 Schematic structural diagram of another embodiment of the vehicle diagnosis device provided by an embodiment of the present application;

[0083] Figure 7 Schematic structural diagram of an embodiment of the vehicle diagnosis device provided by an embodiment of the present application. Detailed implementation manners

[0084] Embodiments of the present application provide a vehicle diagnosis method, device, server, and computer storage medium, which are used to enable users with different identities to diagnose a vehicle with different focuses, thereby improving the user experience.

[0085] Please refer to Figure 1 , Figure 1 Schematic architecture diagram of the vehicle diagnosis system provided by an embodiment of the present application. The vehicle diagnosis method provided by an embodiment of the present application is applied to the vehicle diagnosis system. The vehicle diagnosis system includes: a server 101, a client 102, a diagnostic communication device 103, and a device to be diagnosed 104.

[0086] In embodiments of the present application, communication connections are established between the server 101 and the client 102, between the client 102 and the diagnostic communication device 103, between the diagnostic communication device 103 and the device to be diagnosed 103, and between the server 101 and the diagnostic communication device 103, and communication is carried out through a communication protocol. In practical applications, the client 102 sends a diagnostic instruction to the server 101. The server 101 determines the corresponding diagnostic communication device 103 according to the diagnostic instruction and establishes communication. The diagnostic communication device 103 then performs information interaction with the device to be diagnosed 104 according to the diagnostic instruction, collects diagnostic data, and sends the diagnostic data to the server 101, so that the server 101 determines a target diagnostic result according to the diagnostic data.

[0087] Specifically, the server 101 can be a cloud server, a workstation, a cluster server, a distributed server, or other computing devices with computing capabilities. The client 102 can be a mobile phone, a personal computer (PC), a personal digital assistant (PDA), or a mobile terminal. The diagnostic communication device 103 specifically refers to a device for communicating with the device to be diagnosed 104, such as a vehicle diagnostic connector, and the device to be diagnosed 104 refers to the vehicle to be diagnosed.

[0088] It should be noted that the diagnostic result display method based on the client identity provided in the embodiments of the present application is applied to a server, which can be a cloud server, a cluster server, a distributed server, or a workstation, etc. The server stores a vehicle diagnostic program for diagnosing the vehicle to be diagnosed according to the diagnostic request of the client.

[0089] Please refer to Figure 2 , Figure 2 This is an embodiment of the vehicle diagnostic method provided in the embodiments of the present application. The method is applied to a server, which can be a cloud server, a cluster server, a distributed server, a workstation, etc. The method includes:

[0090] 201. Obtain the diagnostic request sent by the client. The diagnostic request includes the user identification of the client.

[0091] Specifically, for the convenience of user operation and viewing, the vehicle diagnostic program stored in the server is provided with a client interface, which can be lightweight client software, providing a diagnostic interface and operation instructions for the user, and displaying the diagnostic results of the server based on the operation instructions in the client software; it can also be a web interface. After the user enters the web interface by inputting the website address, the user sends operation instructions and views the diagnostic results according to the feedback of the diagnostic results of the server. The client interface is generally presented on the user terminal. The user terminal can be a personal computer (PC), a personal digital assistant (PDA), or a mobile terminal. When the user terminal has the function of accessing and displaying the client interface, the user terminal can be regarded as a client device at this time. For the convenience of description, the client in the following generally refers to the user terminal that can access and display the client interface.

[0092] When a user needs to diagnose a vehicle to be diagnosed, the server obtains a diagnostic request through the input information of the user on the client side. In some specific embodiments, after the user logs in to the account on the client interface, the user initiates a diagnostic request by inputting the identification of the in-vehicle device installed on the vehicle to be diagnosed. At this time, the server can obtain a diagnostic request including the user identification and the in-vehicle device identification. Among them, the user identification is used to uniquely identify the user, including the user account or other information with the ability to identify the user's identity; the in-vehicle device identification is used by the server to determine the in-vehicle device and the corresponding vehicle to be diagnosed, so as to establish a communication interaction with the vehicle to be diagnosed. The in-vehicle device identification can be the device serial number of the in-vehicle device, or other device identifications of the in-vehicle device, as long as it can uniquely identify the in-vehicle device, and no specific limitation is made here. In some specific application scenarios, the in-vehicle device can be a vehicle central control device or an OBD connector installed on the vehicle OBD interface.

[0093] 202. Determine the user category of the client according to the user identification.

[0094] Specifically, the server determines the user category of the client according to the user identification in the obtained diagnostic request. The user categories include professional user categories and ordinary user categories. Among them, professional users refer to users with professional skills. In the embodiments of the present application, they specifically refer to personnel with professional skills in vehicle diagnosis, such as vehicle maintenance technicians, while ordinary users refer to users who use the vehicle for diagnosis and do not have professional skills, such as individual car owners.

[0095] Specifically, the user category of the client can be set by the user himself during registration, or can be selected by the client before diagnosis. No specific limitation is made here.

[0096] 203. Determine the target diagnostic process corresponding to the user category according to the user category.

[0097] After the server determines the user category of the client, it determines the corresponding target diagnostic process according to different user categories. Specifically, the user categories of the client include professional user categories and ordinary user categories, and the corresponding target diagnostic processes are professional diagnostic processes and ordinary diagnostic processes respectively. Among them, the professional diagnostic process focuses on diagnosing the faults of the whole vehicle and can directly perform repairs according to the maintenance requirements during the diagnosis process, while the ordinary diagnostic process focuses on detecting specific systems of the vehicle and provides maintenance suggestions and professional remote assistance services.

[0098] 204. Diagnose the target vehicle according to the target diagnostic process.

[0099] After the server determines the corresponding target diagnostic process according to the different user categories of the client, it diagnoses the target vehicle according to the target diagnostic process. Specifically, after the server obtains a diagnostic request, it determines the target in-vehicle device according to the in-vehicle device identifier in the diagnostic request, and then determines whether the target in-vehicle device is connected to the network. If it is in the connected state, it communicates with the corresponding target vehicle through the target in-vehicle device and diagnoses the target vehicle according to the target diagnostic process to obtain a diagnostic result.

[0100] In this embodiment, after the server obtains the diagnostic request sent by the client, it determines the user category of the client according to the user identifier of the diagnostic request, then determines the target in-vehicle device according to the in-vehicle device identifier in the diagnostic request, then establishes a communication connection with the corresponding target vehicle based on the target in-vehicle device, and then diagnoses the target vehicle using the target diagnostic process determined based on the user category to obtain a diagnostic result. This enables users with different identities to diagnose the vehicle with different focuses, thereby improving the user experience.

[0101] In the embodiments of the present application, the user categories include professional user categories and ordinary user categories. The diagnostic processes executed by the server for different user categories are different, and are described separately below:

[0102] I. Professional diagnostic process for professional users:

[0103] Please refer to Figure 3 , Figure 3 which is another embodiment of the vehicle diagnostic method provided by the embodiments of the present application. This method is applied to a server, which can be a cloud server, a cluster server, a distributed server, a workstation, etc. This method includes:

[0104] 301. Receive a registration request sent by the client. The registration request carries the user identifier and user category of the client.

[0105] The user can register a user account through the client interface of the client. When registering, the user needs to complete the setting of the user category. The user categories in the embodiments of the present application include professional user categories and ordinary user categories. The server obtains the registration request sent by the client, and this registration request carries the user identifier of the client and the user category set by the client. Specifically, the user identifier refers to the unique identifier of the user of this client, including the user account or other information that can identify the user's identity. For example, it can be the user ID customized by the user during registration or the identity ID automatically generated by the client using a specific algorithm.

[0106] For example, when a user registers on the client side, the user can set their user identity based on their own repair experience. If the user has certain vehicle repair experience, they can set their user category as a repair technician (professional user category). If the user is a vehicle user such as a car owner and has no repair experience, they can set their user category as an ordinary user category.

[0107] 302. Establish a mapping relationship between the user identifier and the user category on the client side.

[0108] After the server receives the registration request sent by the client, it establishes a mapping relationship between the user identifier carried in the registration request and the user category. For example, if the user identifier carried in the registration request is: user01 and the user category is the professional user category, the server establishes a mapping relationship between user01 and the professional user category. Specifically, it can add user01 to the list of professional user categories so that the server can subsequently determine that the user category of the corresponding client is the professional user category based on the user identifier user01. Another example is that if the user identifier carried in the registration request is user02 and the user category is the ordinary user category, the server establishes a mapping relationship between user02 and the ordinary user category. Specifically, it can add user02 to the list of ordinary user categories so that the server can subsequently determine that the user category of the client is the ordinary user category based on the user identifier user02.

[0109] 303. Obtain the diagnostic request sent by the client, and the diagnostic request contains the user identifier of the client.

[0110] Step 303 in this embodiment is similar to step 201 in the foregoing embodiment, and will not be elaborated here.

[0111] 304. Establish a communication connection with the in-vehicle device according to the diagnostic request.

[0112] After the server receives the diagnostic request sent by the client, it determines the target in-vehicle device according to the in-vehicle device identifier carried in the diagnostic request, and then establishes a communication connection with the target in-vehicle device by establishing a communication connection with the communication module built in the target in-vehicle device. For example, when the in-vehicle device is an OBD connector, the server determines the target OBD connector according to the OBD connector identifier in the diagnostic request, and then establishes a communication connection with the target OBD connector through the mobile communication module of the target OBD connector.

[0113] 305. Determine that the user category of the client is the professional user category according to the user identifier.

[0114] After the server receives the diagnostic request, it analyzes the user identification therein and searches for the user identification in the professional user list and the general user list respectively. When the user identification is found in the professional user list, it determines that the user category corresponding to the client is the professional user category. For example, when the user identification is user01, and the server finds the user identification user01 in the professional user list, it determines that the user category of the client corresponding to user01 is the professional user category.

[0115] It should be noted that the professional user category refers to users with professional skills, such as maintenance technicians and other relevant technical personnel.

[0116] In some possible implementation manners, if the user does not set the user category during registration, the server can also determine the user category of the client by sending a user category selection pop-up window to the corresponding client after receiving the diagnostic request sent by the client, as follows:

[0117] The server sends a user category selection pop-up window to the client according to the user identification;

[0118] The server determines the user category of the client according to the user category selection result returned by the client.

[0119] In this way, even if the user does not set the corresponding user category during registration, the server can also inquire about the user category from the client before diagnosis to achieve vehicle diagnosis with different focuses based on the different user categories of the client.

[0120] 306. Determine the professional diagnosis process corresponding to the professional user category.

[0121] After determining that the identity of the client is the professional user category, that is, a user with professional skills, such as maintenance technicians and other relevant technical personnel, the server can thus determine that the target diagnosis process is the professional diagnosis process. Then, the server controls the in-vehicle device head to diagnose the target vehicle according to the professional diagnosis process.

[0122] The professional diagnosis process focuses on diagnosing the faults of the whole vehicle, and during the diagnosis process, repairs can be directly carried out according to the repair requirements. Steps 307 to 311 are an implementation manner of the professional diagnosis process, which will be described in detail below:

[0123] 307. Obtain the basic information of the target vehicle.

[0124] Specifically, the server can obtain the basic information of the target vehicle through the vehicle model information input by the user on the client (including the user selecting a specific vehicle model on the client, or the user using the client to scan the VIN code, etc.), or directly read the basic information of the vehicle by communicating with the in-vehicle device. In some specific embodiments, the basic information of the target vehicle includes the vehicle model information of the target vehicle and the information of the configured electronic control unit (ECU).

[0125] 308. Perform a full-system diagnosis on the target vehicle to obtain the full-system diagnosis result.

[0126] Specifically, after obtaining the basic information of the target vehicle, the server performs a one-by-one diagnosis on the full system of the target vehicle through the target in-vehicle device installed on the target vehicle, reads the fault codes in all ECU systems of the target vehicle, and thus obtains the full-system diagnosis result.

[0127] Specifically, the server can determine whether there is a fault in the target vehicle through the fault code. If a fault code is generated during the diagnosis process, the reference bus signal and reference diagnostic data stream corresponding to the fault code can be obtained from the database according to the fault code, and based on the comparison result between the real-time bus signal and the reference bus signal, as well as the comparison result between the real-time diagnostic data stream and the reference diagnostic data stream, it is comprehensively determined whether a fault has occurred, and a corresponding fault information is generated when it is determined that a fault has occurred.

[0128] 309. Generate a diagnostic report before maintenance according to the full-system diagnosis result.

[0129] Specifically, since it is an initial diagnosis, the server generates a diagnostic report before maintenance according to the full-system diagnosis result to provide a reference for the subsequent maintenance process.

[0130] 310. Repair the target vehicle according to the full-system diagnosis result.

[0131] The server determines the maintenance service requirements according to the full-system diagnosis result and feeds them back to the client, and provides maintenance assistance operations according to the maintenance instructions of the client, such as reading data streams, clearing fault codes, action testing, online programming, etc.

[0132] 311. After the repair is completed, perform a full-system diagnosis on the target vehicle again to generate a diagnostic report after maintenance.

[0133] Specifically, after the repair is completed, according to the instruction of the client, the server performs a one-by-one full-system diagnosis on the target vehicle again through the target in-vehicle device, and outputs a diagnostic report after maintenance according to the diagnosis result.

[0134] In this embodiment, after the server determines that the user category of the client is a professional user category according to the diagnostic request sent by the client, it controls the target vehicle-mounted device to diagnose the target vehicle according to the professional diagnostic process. In the professional diagnostic process, the entire system of the vehicle is diagnosed and maintenance assistance is provided, and two diagnostic reports before and after maintenance are provided, enabling professional users to perform vehicle diagnostic analysis based on the two diagnostic reports, ensuring that vehicle faults are completely repaired, and thus improving the user experience.

[0135] II. Ordinary diagnostic process for ordinary users:

[0136] Please refer to Figure 4 , Figure 4 which is another embodiment of the vehicle diagnostic method provided by the embodiment of the present application. This method is applied to a server, which can be a cloud server, a cluster server, a distributed server, a workstation, etc. This method includes:

[0137] 401. Receive a registration request sent by the client. The registration request carries the user identifier and user category of the client.

[0138] 402. Establish a mapping relationship between the user identifier and user category of the client.

[0139] 403. Obtain a diagnostic request sent by the client. The diagnostic request contains the user identifier of the client.

[0140] 404. Establish a communication connection with the vehicle-mounted device according to the diagnostic request.

[0141] In this embodiment, steps 401 to 404 are similar to steps 301 to 304 in the foregoing embodiment, and will not be elaborated here.

[0142] 405. Determine that the user category of the client is an ordinary user category according to the user identifier.

[0143] After the server obtains the diagnostic request, it analyzes the user identifier therein, searches for the user identifier in the professional user list and the ordinary user list respectively. When the user identifier is found in the ordinary user list, it determines that the user category corresponding to the client is an ordinary user category. For example, when the user identifier is user02, the server finds the user identifier user02 in the ordinary user list, and then determines that the user category of the client corresponding to user02 is an ordinary user category.

[0144] It should be noted that the ordinary user category refers to users who are vehicle users and do not have diagnostic and maintenance skills, such as individual car owners.

[0145] In some possible embodiments, if the user does not set the user category during registration, the server can also determine the user category of the client by sending a user category selection pop-up window to the corresponding client after receiving the diagnostic request sent by the client, as follows:

[0146] The server sends a user category selection pop-up window to the client according to the user identification;

[0147] The server determines the user category of the client according to the user category selection result returned by the client.

[0148] In this way, even if the user does not set the corresponding user category during registration, the server can also inquire about the user category from the client before diagnosis, so as to implement vehicle diagnosis with different focuses based on different user categories of the client.

[0149] 406. Determine the general diagnosis process corresponding to the general user category according to the general user category.

[0150] After determining that the identity of the client is a general user, that is, a user without professional skills, such as an individual car owner, the server can therefore determine that the target diagnosis process is the general diagnosis process. The server controls the in-vehicle device to diagnose the target vehicle according to the general diagnosis process.

[0151] Since users in the general user category do not have professional skills, the general diagnosis process focuses on detecting specific systems of the vehicle and providing repair suggestions or professional remote assistance services, that is, it does not provide the diagnostic function of direct repair. Steps 407 to 410 are an implementation manner of the general diagnosis process, which will be described in detail below:

[0152] 407. Obtain the historical information of the target vehicle, where the historical information includes historical diagnosis record information, maintenance information record, and vehicle mileage information.

[0153] Specifically, in order to further determine the target diagnosis process of the general user, the server first needs to obtain the historical information of the target vehicle, including historical diagnosis record information, maintenance information record, and vehicle mileage information. The server can obtain the VIN code information of the vehicle through the in-vehicle device, and then obtain the historical diagnosis record information and maintenance information record of the target vehicle in the vehicle history database based on the VIN code information. At the same time, by communicating with the target in-vehicle device, the server reads the mileage data of the target vehicle to obtain the vehicle mileage information. The server can also send a historical information acquisition request to the client, so as to obtain historical information such as historical diagnosis record information, maintenance information record, and vehicle mileage information through the input of the user on the client. No specific limitation is made here.

[0154] 408. Determine the vehicle system to be detected according to the historical information.

[0155] After the server obtains the historical information of the target vehicle, it can determine the vehicle systems to be detected according to the historical information. In some specific embodiments, first, it is determined whether there are vehicle systems with historical faults according to the historical diagnostic record information. If so, the vehicle systems with historical faults are used as the first target vehicle systems to be detected. At the same time, according to the maintenance information record and the vehicle mileage information, the vehicle systems without historical faults that need to be maintained currently are determined, and the vehicle systems without historical faults that need to be maintained currently are used as the second target vehicle systems to be detected. Then, the first target vehicle systems to be detected and the second target vehicle systems to be detected are combined to obtain the vehicle systems to be detected. For example, in some specific embodiments, if it is found in the historical information of the target vehicle that there are historical faults and historical maintenance records in the ABS system and the airbag system, then the ABS system and the airbag system are first determined as the first target systems to be detected. Then, according to the current mileage information and maintenance record information of the target vehicle, it is determined that the ABS system, the engine system, and the transmission system need to be maintained. Then, the ABS system, the engine system, and the transmission system are determined as the second target systems to be detected. The first target systems to be detected and the second target systems to be detected are combined, and the systems to be detected are obtained as the ABS system, the airbag system, the engine system, and the transmission system.

[0156] It should be noted that different from the professional diagnosis process, in the ordinary diagnosis process, the server controls the in-vehicle device to diagnose only the vehicle systems that need to be detected, rather than the whole system. This can save the time for ordinary users to diagnose the vehicle and provide a more targeted vehicle diagnosis service for ordinary users.

[0157] 409. Diagnose the vehicle systems to be detected.

[0158] After the server determines the vehicle systems to be detected, it controls the target in-vehicle device to diagnose them one by one, reads the fault codes of the vehicle systems to be detected, generates corresponding fault information according to the fault codes, executes the corresponding fault analysis strategy, and generates a fault repair guide.

[0159] 410. Generate a diagnostic report according to the diagnostic results.

[0160] Specifically, the server generates a diagnostic report according to the fault codes, fault information, and fault repair guide of the system to be detected, and then sends the diagnostic report to the client. The user can understand whether the target vehicle needs to be repaired according to the fault repair guide in the diagnostic report, and can also provide professional remote assistance services for the user when the repair suggestion indicates that repair is needed, such as detailed consultation on repair suggestions and query of repair points.

[0161] In this embodiment, after the server determines that the user category of the client is the general user category according to the diagnostic request sent by the client, it controls the target vehicle-mounted device to diagnose the target vehicle according to the general diagnostic process. In the general diagnostic process, the entire system of the target vehicle is not diagnosed and repaired, but only the vehicle systems that need to be detected are detected, and repair suggestions are provided, enabling general users to perform vehicle diagnosis in a more concise and efficient manner, thereby improving the user experience.

[0162] The vehicle diagnosis method provided by the embodiment of the present application is described above. The vehicle diagnosis device provided by the embodiment of the present application is described below. Please refer to Figure 5 , Figure 5 This is an embodiment of the vehicle diagnosis device provided by the embodiment of the present application. The diagnosis device includes:

[0163] An acquisition unit 501, configured to acquire a diagnostic request sent by the client, where the diagnostic request includes the user identifier of the client;

[0164] A first determination unit 502, configured to determine the user category of the client according to the user identifier;

[0165] A second determination unit 503, configured to determine a target diagnostic process corresponding to the user category according to the user category;

[0166] A diagnosis unit 504, configured to diagnose the target vehicle according to the target diagnostic process.

[0167] In this embodiment, before a user performs an automotive diagnosis through the client, the user can first set their own user category. After the acquisition unit 501 acquires the diagnostic request sent by the client, the first determination unit 502 and the second determination unit 503 will determine different target diagnostic processes based on the different client user categories. The diagnosis unit 504 then diagnoses the vehicle according to the target diagnostic process. The diagnostic items involved in different target diagnostic processes are different, so that users with different identities can diagnose the vehicle with different focuses, thereby improving the user experience.

[0168] The vehicle diagnosis device provided by the embodiment of the present application is described in detail below. Please refer to Figure 6 , Figure 6 This is another embodiment of the vehicle diagnosis device provided by the embodiment of the present application. The diagnosis device includes:

[0169] An acquisition unit 601, configured to acquire a diagnostic request sent by the client, where the diagnostic request includes the user identifier of the client;

[0170] A first determination unit 602, configured to determine the user category of the client according to the user identifier;

[0171] The second determination unit 603 is configured to determine a target diagnostic process corresponding to the user category according to the user category;

[0172] The diagnostic unit 604 is configured to diagnose the target vehicle according to the target diagnostic process.

[0173] In this embodiment, further, the user categories of the client include a professional user category and an ordinary user category;

[0174] When the user category of the client is the professional user category, the target diagnostic process is the professional diagnostic process;

[0175] When the user category of the client is the ordinary user category, the target diagnostic process is the ordinary diagnostic process.

[0176] In this embodiment, further, the professional diagnostic process includes:

[0177] Obtain the basic information of the target vehicle;

[0178] Perform a full-system diagnosis on the target vehicle to obtain a full-system diagnosis result;

[0179] Generate a diagnostic report before maintenance according to the full-system diagnosis result;

[0180] Repair the target vehicle according to the full-system diagnosis result;

[0181] After the repair is completed, perform a full-system diagnosis on the target vehicle again to generate a diagnostic report after maintenance.

[0182] In this embodiment, further, the ordinary diagnostic process includes:

[0183] Obtain the historical information of the target vehicle, where the historical information includes historical diagnostic record information, maintenance information record, and vehicle mileage information;

[0184] Determine the vehicle system to be detected according to the historical information;

[0185] Diagnose the vehicle system to be detected;

[0186] Generate a diagnostic report according to the diagnostic result.

[0187] In this embodiment, further, the diagnostic device further includes:

[0188] The registration unit 605 is configured to receive a registration request sent by the client, where the registration request carries the user identifier and user category of the client;

[0189] The establishment unit 606 is configured to establish a mapping relationship between the user identifier and user category of the client;

[0190] The first determination unit 602 is specifically configured to:

[0191] Determine the user category of the client according to the user identification and the mapping relationship.

[0192] In this embodiment, further, the first determination unit 602 is specifically further configured to:

[0193] Send a user category selection pop-up window to the client according to the user identification;

[0194] Determine the user category of the client according to the user category selection result returned by the client.

[0195] In this embodiment, further, the diagnostic device further includes:

[0196] A communication unit 607, configured to establish a communication connection with the in-vehicle device according to the diagnostic request;

[0197] The diagnostic unit 604 is specifically configured to:

[0198] Control the in-vehicle device to diagnose the target vehicle according to the target diagnostic process;

[0199] Receive the diagnostic result sent by the in-vehicle device.

[0200] In the device of this embodiment, the functions of each unit correspond to the steps in the foregoing Figure 3 or Figure 4 The method embodiments shown will not be elaborated here.

[0201] This application embodiment also provides a server. Please refer to Figure 7 , Figure 7 This is an embodiment of the server provided by this application embodiment. The server includes:

[0202] A processor 701, a memory 702, an input / output unit 703, and a bus 704;

[0203] The processor 701 is connected to the memory 702, the input / output unit 703, and the bus 704;

[0204] The memory 702 stores a program, and the processor 701 calls the program to execute the following method:

[0205] Obtain the diagnostic request sent by the client, and the diagnostic request includes the user identification of the client;

[0206] Determine the user category of the client according to the user identification;

[0207] Determine the target diagnostic process corresponding to the user category according to the user category;

[0208] Diagnose the target vehicle according to the target diagnostic process.

[0209] Optionally, the user categories of the client include a professional user category and a general user category;

[0210] When the user category of the client is the professional user category, the target diagnosis process is the professional diagnosis process;

[0211] When the user category of the client is the general user category, the target diagnosis process is the general diagnosis process.

[0212] Optionally, the professional diagnosis process includes:

[0213] Obtain the basic information of the target vehicle;

[0214] Conduct a full-system diagnosis on the target vehicle to obtain a full-system diagnosis result;

[0215] Generate a diagnosis report before repair based on the full-system diagnosis result;

[0216] Repair the target vehicle according to the full-system diagnosis result;

[0217] After the repair is completed, conduct a full-system diagnosis on the target vehicle again to generate a diagnosis report after repair.

[0218] Optionally, the general diagnosis process includes:

[0219] Obtain the historical information of the target vehicle, where the historical information includes historical diagnosis record information, maintenance information records, and vehicle mileage information;

[0220] Determine the vehicle systems to be detected based on the historical information;

[0221] Conduct a diagnosis on the vehicle systems to be detected;

[0222] Generate a diagnosis report based on the diagnosis result.

[0223] Optionally, before obtaining the diagnosis request sent by the client, the method further includes:

[0224] Receive the registration request sent by the client, where the registration request carries the user identifier and user category of the client;

[0225] Establish a mapping relationship between the user identifier and user category of the client;

[0226] Determining the user category of the client based on the user identifier includes:

[0227] Determine the user category of the client based on the user identifier and the mapping relationship.

[0228] Optionally, determining the user category of the client based on the user identifier includes:

[0229] Send a user category selection pop-up window to the client according to the user identification;

[0230] Determine the user category of the client according to the user category selection result returned by the client.

[0231] Optionally, after receiving the diagnostic request sent by the client, the method further includes:

[0232] Establish a communication connection with the in-vehicle device according to the diagnostic request;

[0233] Diagnosing the vehicle according to the target diagnostic process includes:

[0234] Control the in-vehicle device to diagnose the target vehicle according to the target diagnostic process;

[0235] Receive the diagnostic result sent by the in-vehicle device.

[0236] An embodiment of the present application also relates to a computer-readable storage medium, on which a program is stored. When the program runs on a computer, it causes the computer to execute any of the above vehicle diagnostic methods.

[0237] Those skilled in the art can clearly understand that for the convenience and simplicity of description, the specific working processes of the above-described systems, devices, and units can refer to the corresponding processes in the foregoing method embodiments, and will not be elaborated herein.

[0238] In several embodiments provided by the present application, it should be understood that the disclosed systems, devices, and methods can be implemented in other ways. For example, the device embodiments described above are merely illustrative. For example, the division of the units is only a logical function division, and there may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the displayed or discussed mutual coupling or direct coupling or communication connection can be through some interfaces, and the indirect coupling or communication connection of the devices or units can be in an electrical, mechanical, or other form.

[0239] The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or may be distributed to multiple network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0240] In addition, each functional unit in various embodiments of the present application may be integrated into one processing unit, may exist separately as individual physical units, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of a software functional unit.

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

Claims

1. A vehicle diagnosis method, characterized in that, The described diagnostic method includes: Obtaining a diagnostic request sent by the client, where the diagnostic request contains the user identification of the client; Determining the user category of the client according to the user identification; Determining the target diagnostic process corresponding to the user category according to the user category; Diagnosing the target vehicle according to the target diagnostic process; The user category of the client includes a professional user category and an ordinary user category; When the user category of the client is the professional user category, the target diagnostic process is a professional diagnostic process, and the professional diagnostic process is used to diagnose the faults of the entire target vehicle and perform repairs according to the repair requirements during the diagnosis process; When the user category of the client is the ordinary user category, the target diagnostic process is an ordinary diagnostic process, and the ordinary diagnostic process is used to detect a specific system of the target vehicle and provide repair suggestions and remote assistance services.

2. The diagnostic method according to claim 1, characterized in that The professional diagnostic process includes: Obtaining the basic information of the target vehicle; Performing a full-system diagnosis on the target vehicle to obtain a full-system diagnosis result; Generating a diagnostic report before repair according to the full-system diagnosis result; Repairing the target vehicle according to the full-system diagnosis result; Performing a full-system diagnosis on the target vehicle again after the repair is completed to generate a diagnostic report after repair.

3. The diagnostic method according to claim 1, characterized in that The ordinary diagnostic process includes: Obtaining the historical information of the target vehicle, where the historical information includes historical diagnostic record information, maintenance information record, and vehicle mileage information; Determining the vehicle system to be detected according to the historical information; Diagnosing the vehicle system to be detected; Generating a diagnostic report according to the result of the diagnosis.

4. The diagnostic method according to claim 1, wherein Before obtaining the diagnostic request sent by the client, the method further includes: Receiving a registration request sent by the client, where the registration request carries the user identification and user category of the client; Establishing a mapping relationship between the user identification of the client and the user category; The determining the user category of the client according to the user identification includes: Determining the user category of the client according to the user identification and the mapping relationship.

5. The diagnostic method according to claim 1, wherein The determining the user category of the client according to the user identification includes: Sending a user category selection pop-up window to the client according to the user identification; Determining the user category of the client according to the user category selection result returned by the client.

6. The diagnostic method according to any one of claims 1 to 5, characterized in that, After obtaining the diagnostic request sent by the client, the method further includes: Establishing a communication connection with the in-vehicle device according to the diagnostic request; The diagnosing the target vehicle according to the target diagnostic process includes: Controlling the in-vehicle device to diagnose the target vehicle according to the target diagnostic process; Receiving the diagnostic result sent by the in-vehicle device.

7. A vehicle diagnostic device, characterized in that, The diagnostic device includes: An obtaining unit, configured to obtain a diagnostic request sent by the client, where the diagnostic request contains the user identification of the client; A first determining unit, configured to determine the user category of the client according to the user identification; A second determining unit, configured to determine the target diagnostic process corresponding to the user category according to the user category; A diagnostic unit for diagnosing a target vehicle according to the target diagnostic process; The user categories of the client include a professional user category and an ordinary user category; When the user category of the client is the professional user category, the target diagnostic process is a professional diagnostic process, and the professional diagnostic process is used to diagnose faults in the entire vehicle of the target vehicle and perform repairs according to maintenance requirements during the diagnosis; When the user category of the client is the ordinary user category, the target diagnostic process is an ordinary diagnostic process, and the ordinary diagnostic process is used to detect a specific system of the target vehicle and provide maintenance suggestions and remote assistance services.

8. A server, characterized in that, The server includes: A processor, a memory, an input / output unit, and a bus; The processor is connected to the memory, the input / output unit, and the bus; The memory stores a program, and the processor calls the program to execute the diagnostic method according to any one of claims 1 to 6.

9. A computer-readable storage medium, on which a program is stored, and when the program is executed on a computer, it executes the diagnostic method according to any one of claims 1 to 6.

Images