WO2018040357A1

WO2018040357A1 - Method for realizing cloud diagnosis of vehicle and related device

Info

Publication number: WO2018040357A1
Application number: PCT/CN2016/108946
Authority: WO
Inventors: 刘均; 谢飞虹
Original assignee: 深圳市元征科技股份有限公司
Priority date: 2016-08-31
Filing date: 2016-12-07
Publication date: 2018-03-08
Also published as: CN106372189B; CN106372189A

Abstract

Disclosed are a method for realizing cloud diagnosis of a vehicle and a related device. The present invention relates to when a query result is that a history record corresponding to an identifier of a vehicle exists, at least scanning a fault point in the history record carried in the query result to obtain scanning data and thus carry out cloud diagnosis on the vehicle; and when the query result is that a history record corresponding to an identifier of a vehicle does not exist, performing comprehensive scanning on the vehicle to carry out cloud diagnosis on the vehicle. That is, in embodiments of the present invention, when a vehicle is located at different geographic positions or is diagnosed by different people, the overall condition of a vehicle can be evaluated by making effective use of history diagnosis data of the vehicle.

Description

Method for implementing vehicle cloud diagnosis and related device

Technical field

The present invention relates to the field of communication technologies, and in particular, to a method and a related device for implementing vehicle cloud diagnosis.

Background technique

Vehicles bring great convenience to our lives. Nowadays, the vehicles we use are cars, buses, trains, ships, airplanes, etc. The use of vehicles is frequent and the safety of vehicles is extremely important. Therefore, transportation Need to check the repair regularly.

The maintenance records of the vehicles are usually kept on the computer of the repair shop. However, the time and place of the vehicle failure are uncontrollable. When the vehicle fails, it can only be repaired nearby. Therefore, the vehicle Most of the maintenance is in different geographical locations, and maintenance personnel have no way of knowing the previous maintenance records of the vehicle. Therefore, the traditional vehicle diagnosis method can only re-inspect the entire vehicle, reducing the efficiency of diagnosis of the vehicle.

Summary of the invention

Embodiments of the present invention provide a method and a related device for implementing vehicle cloud diagnosis, which solves the problem that the efficiency of vehicle diagnosis in the prior art is not high.

In a first aspect, the present invention provides a method for implementing a vehicle cloud diagnosis, including:

The terminal acquires or creates an identifier of the vehicle, and sends a history query request to the cloud server, where the history query request includes an identifier of the vehicle; the terminal receives a query result returned by the cloud server, where The query result is a result obtained by the cloud server querying the historical record of the vehicle according to the identifier of the vehicle; if the query result is a history record corresponding to the identifier of the vehicle, And scanning at least the fault point in the history record carried in the query result to obtain scan data to perform cloud diagnosis on the vehicle; if the query result is not corresponding to the identifier of the vehicle The history records a full scan of the vehicle to perform a cloud diagnosis of the vehicle.

Wherein, the identification of the vehicle may include: a vehicle license plate number, a car VIN code or the like Uniquely identifies the identity feature of the vehicle.

With reference to the first aspect, in a first possible implementation manner, the terminal returns the result of the current cloud diagnosis to the cloud server, where the cloud server sends the result of the current cloud diagnosis and the vehicle Identifies the associated store.

With reference to the first aspect, in a second possible implementation manner, when the identifier of the vehicle is a license plate number and/or a VIN code, the obtaining the identifier of the vehicle by the terminal specifically includes:

The terminal scans the license plate and/or VIN code location of the vehicle for scan data, the scan data including the license plate number and/or VIN code.

With reference to the first aspect, in a third possible implementation manner, when the identifier of the vehicle is a license plate number and/or a VIN code, the obtaining the identifier of the vehicle by the terminal specifically includes:

Transmitting, by the terminal, a license plate number request and/or a VIN code request to a device in the vehicle;

The terminal receives a license plate number and/or a VIN code transmitted by the device in the vehicle based on the license plate number request and/or the VIN code request.

With reference to the first aspect, in a fourth possible implementation manner, before the terminal creates the identifier of the vehicle, the terminal further includes: the terminal acquiring the identifier of the vehicle; and the identifying the identifier of the vehicle by the terminal specifically includes: If the terminal fails to obtain the identifier of the vehicle, the terminal creates an identifier of the vehicle.

A second aspect of the present invention provides a terminal, including: an acquiring unit, configured to acquire or create an identifier of a vehicle.

And a sending unit, configured to send a history query request to the cloud server, where the history query request includes an identifier of the vehicle.

And a receiving unit, configured to receive a query result returned by the cloud server, where the query result is a result obtained by the cloud server querying the historical record of the vehicle according to the identifier of the vehicle.

a scanning unit, configured to scan at least a fault point in the history record carried in the query result, where the query result is a history record corresponding to the identifier of the vehicle, thereby Obtaining scan data to perform cloud diagnosis on the vehicle; in the case where the query result is a history that does not have an identifier corresponding to the vehicle, the scanning unit is The vehicle is scanned comprehensively to perform a cloud diagnosis of the vehicle.

The identification of the vehicle may include: a vehicle license plate number, a car VIN code, or other identification feature that can uniquely identify the vehicle.

In a first possible implementation manner, the sending unit is further configured to: return a result of the current cloud diagnosis to the cloud server, where the cloud server sends the result of the current cloud diagnosis and the vehicle Identifies the associated store.

In combination with the second aspect, in a second possible implementation manner, the scanning unit is further configured to: when the identifier of the vehicle is a license plate number and/or a VIN code, the scanning unit is for the vehicle Scanning is performed at the location of the license plate and/or VIN code to obtain scanned data, including the license plate number and/or VIN code.

In combination with the second aspect, in a third possible implementation manner, the sending unit is further configured to: when the identifier of the vehicle is a license plate number and/or a VIN code, the sending unit to a device in the vehicle Send a license plate number request and/or VIN code request;

The receiving unit is further configured to receive a license plate number and/or a VIN code sent by the device in the vehicle based on the license plate number request and/or the VIN code request.

With reference to the second aspect, in a fourth possible implementation manner, the acquiring unit is further configured to: before the terminal creates the identifier of the vehicle, the acquiring unit acquires the identifier of the vehicle;

The obtaining unit is specifically configured to: if the terminal acquires the identifier of the vehicle fails, the acquiring unit creates an identifier of the vehicle.

It can be seen that, after the terminal receives the query result returned by the cloud server, if the query result is a history record corresponding to the identifier of the vehicle, at least the history record carried in the query result is included in the history record. The fault point is scanned to obtain scan data to perform cloud diagnosis on the vehicle; if the query result is that there is no history corresponding to the identifier of the vehicle, the vehicle is fully scanned, In order to perform cloud diagnosis on the vehicle, the historical diagnostic data can be effectively used to scan possible fault points of the vehicle, and the maintenance personnel can perform effective maintenance and evaluation on the vehicle according to possible fault points, and the whole process can be performed. It can be completed without a full scan of the vehicle; when the vehicle is in a different geographical location or is inspected and repaired by different maintenance personnel, the cloud service data can be used to obtain the vehicle association data to help the dimension. Repairers better maintain and maintain the vehicle, which greatly simplifies the complexity of vehicle maintenance and repair, and also facilitates more effective vehicle diagnosis.

DRAWINGS

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the embodiments or the description of the prior art will be briefly described below. Obviously, the drawings in the following description are only It is a certain embodiment of the present invention, and other drawings can be obtained from those skilled in the art without any creative work.

1 is a schematic structural diagram of a vehicle cloud diagnostic system according to an embodiment of the present invention;

2 is a schematic structural diagram of a terminal according to an embodiment of the present invention;

3 is a schematic structural diagram of a diagnostic terminal according to an embodiment of the present invention;

4 is a schematic structural diagram of a cloud server according to an embodiment of the present invention;

FIG. 5 is a schematic flowchart diagram of a method for implementing vehicle cloud diagnosis according to an embodiment of the present invention; FIG.

FIG. 6 is a schematic structural diagram of an embodiment of a terminal according to an embodiment of the present disclosure;

FIG. 7 is a schematic structural diagram of another embodiment of a terminal according to an embodiment of the present invention.

detailed description

The technical solutions in the embodiments of the present invention are clearly and completely described in the following with reference to the accompanying drawings in the embodiments of the present invention. It is obvious that the described embodiments are only a part of the embodiments of the present invention, but not all embodiments. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention without creative efforts are within the scope of the present invention.

It is to be understood that the terminology used in the embodiments of the present invention is for the purpose of describing the particular embodiments, and is not intended to limit the invention. The singular forms "a", "the" and "the" It should also be understood that the term "and/or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items.

The embodiment of the invention discloses a method for implementing vehicle cloud diagnosis, which comprises the terminal acquiring or creating an identifier of a vehicle, and sending a history query request to the cloud server, wherein the history query request includes the vehicle Identifying, by the terminal, a query result returned by the cloud server, where the query result is that the cloud server compares the traffic according to the identifier of the vehicle The history of the tool is queried to obtain a result; if the query result is a history corresponding to the identifier of the vehicle, at least the fault point in the history carried in the query result is scanned to obtain Scanning data to perform cloud diagnosis on the vehicle; if the query result is that there is no history corresponding to the identification of the vehicle, then the vehicle is fully scanned to perform on the vehicle Cloud diagnosis.

In order to facilitate the understanding of the present invention, a vehicle cloud diagnostic system related to the implementation method of the vehicle cloud diagnosis of the present invention will be described in detail first. Vehicles in the present invention include, but are not limited to, automobiles, ships, airplanes, trains, high-speed rails, and new types of vehicles that will emerge in the future. Referring to FIG. 1 , a vehicle cloud diagnosis system according to an embodiment of the present invention includes: a terminal 110, a diagnosis terminal 120, and a cloud server 130. In practice, the terminal 110 can be integrated with the vehicle or set up separately from the vehicle, and the terminal 110 moves with the vehicle. The cloud server 130 can be placed away from the vehicle. The terminal 110 performs data communication with the cloud server 130 in a wireless manner. The diagnostic terminal 120 may be provided separately or may be integrally provided with the terminal 110 or the cloud server 130. When the diagnostic terminal 120 is separately set, data communication is performed with the terminal 110 and the cloud server 130 by wireless means, thereby implementing third-party diagnosis.

In the embodiment of the present invention, referring to FIG. 2, the terminal 110 may include a processor 111, a receiver 112, and a transmitter 113. The processor 111 is a control center of the terminal 110, and connects various parts of the entire terminal by using various interfaces and lines, and executes the terminal by running or executing software programs and/or modules stored in the memory, and calling data stored in the memory. The various functions and processing data to monitor the terminal as a whole. Optionally, the processor 111 may include one or more processing cores; optionally, the processor 111 may integrate an application processor and a modem processor. Optionally, the terminal may further include a scanning device, wherein the scanning device may include a camera, and the camera may be a CMOS camera or a CCD camera. By way of example, the terminal can be a cellular phone, a smart phone, a tablet computer, a personal digital assistant (PDA), a handheld device, a laptop computer, a smartbook, a netbook, a cordless phone, a Bluetooth device, an in-vehicle device, and the like.

In the embodiment of the present invention, referring to FIG. 3, the diagnostic terminal 120 may include a processor 121, a receiving module 122, and a sending module 123. When the diagnostic terminal 120 is separately set, it performs data communication with the cloud server 130 and the terminal 110 in a wireless manner, respectively, by using the scan data sent by the received cloud server 130. The cloud diagnosis is performed, and the sending module 123 sends the diagnosis result to the terminal 110 to implement third-party diagnosis.

In the embodiment of the present invention, the cloud server 130 is a computing service with flexible processing capability, and provides comprehensive service capabilities for various Internet users. The management method is simpler and more efficient than the physical server, and the cloud server can help to build a more stable and fast. Safe application. The cloud server's distributed storage technology is used to consolidate a large number of servers into one supercomputer, providing massive data storage and processing services. The distributed file system and distributed database of the cloud server allow access to common storage resources and realize input and output sharing of application data files. Referring to FIG. 4, the cloud server 130 can include a processor 131, a memory 132, a transmitter 133, and a receiver 134. The memory of the cloud server 130 provides a massive amount of data storage using a distributed file system, distributed file repository storage resources.

In order to solve the problem that the prior art vehicle diagnosis is not efficient, referring to FIG. 5, the present invention provides a schematic flowchart of a method for implementing vehicle cloud diagnosis. The embodiment of the present invention is described from the perspective of a terminal, and the implementation method of the vehicle cloud diagnosis according to the embodiment of the present invention includes:

501: The terminal acquires or creates an identifier of the vehicle, and sends a history query request to the cloud server, where the history query request includes an identifier of the vehicle.

In an embodiment of the invention, the identification of the vehicle is a unique identification of the vehicle, and the identification of the vehicle may be a 2D number, letter, symbol, pattern, or a combination therebetween. The identity of the vehicle may also be a 3D or higher dimensional logo. For example, a vehicle license plate number or a car VIN code or the like, the identification of the vehicle may be stored in a storable medium of the terminal, the identification of the vehicle may also be engraved on the body of the vehicle, or the traffic sign may also be set, for example. On the license plate and other pendants. The identification of the vehicle may use an identity that already exists, such as the license plate number of the vehicle, etc., or the identity of the vehicle may also be a newly created identity.

In a specific implementation, if the identifier of the vehicle is stored in a storable medium of the terminal, the terminal may read the identifier of the vehicle from the storable medium and send a history query request carrying the identifier of the vehicle to the cloud server. .

In a specific implementation, if the identification of the vehicle is engraved on the main body of the vehicle, or the traffic sign is set on a pendant such as a license plate, the terminal may scan the identification of the vehicle through the camera to obtain scan data. The scan data includes the identity of the vehicle. After obtaining the identification of the vehicle, the terminal sends a history query request to the cloud server that carries the identity of the vehicle.

In a specific implementation, if the identification of the vehicle is stored in a related device of the vehicle, the terminal may acquire the vehicle identification sent by the related device after transmitting the vehicle identification request to the related device.

Further, in order to use the originally existing identifier as the identifier of the vehicle as much as possible, the terminal may first try to obtain the identifier of the vehicle, and further, in order to make the result of the diagnosis better integrated with other information, the terminal obtains as much as possible The identity of the vehicle that already exists, such as the license plate number, etc., is used as the identity of the vehicle. After the failure to obtain the identification of the vehicle, an identification of the new vehicle is created.

502: The terminal receives the query result returned by the cloud server, where the query result is a result obtained by the cloud server querying the historical record of the vehicle according to the identifier of the vehicle.

In the embodiment of the present invention, if the query result is a history record corresponding to the identifier of the vehicle, the query result returned by the cloud server carries the history record. The history record may include the specific time of each cloud diagnosis, the fault point, the fault point scan data, the solution, the number of failures of the fault point, the cloud diagnosis count statistics, and the like, all of which may be stored in the cloud server and the vehicle cloud. Diagnose related information.

If the result of the query is that there is a history corresponding to the identity of the vehicle, proceed to step 503; if the result of the query is a history that does not correspond to the identity of the vehicle, proceed to step 504.

503: When the query result is a history record corresponding to the identifier of the vehicle, at least the fault point in the history record carried in the query result is scanned to obtain scan data to perform cloud diagnosis on the vehicle.

In the embodiment of the present invention, since the place where the vehicle has a problem is usually a place where a problem has occurred before, if the result of the inquiry is a history record corresponding to the identification of the vehicle, the history record can be obtained from the history record. The fault point in the middle, and at least the fault point in the history carried in the query result is scanned to obtain scan data to perform cloud diagnosis on the vehicle. In this embodiment, at least the fault point can be scanned in a targeted manner and sent to the diagnostic terminal for fault diagnosis, thereby improving the efficiency of the cloud diagnosis.

504: When the query result is that there is no history corresponding to the identifier of the vehicle, the vehicle is comprehensively scanned to perform cloud diagnosis on the vehicle.

In the embodiment of the present invention, if the query result is that there is no history corresponding to the identification of the vehicle, a comprehensive scan of the vehicle is required to perform cloud diagnosis on the vehicle.

It can be understood that, when performing cloud diagnosis, the diagnosis terminal can also perform cloud diagnosis in combination with historical records, thereby improving the accuracy and efficiency of diagnosis.

In a specific implementation, after the terminal scans the vehicle, the maintenance personnel may perform maintenance on a possible fault point for the cloud diagnosis result, and after the repair is completed, the terminal returns the result of the current cloud diagnosis to the a cloud server, wherein the cloud server stores the result of the current cloud diagnosis and the identifier of the vehicle, wherein the result of the current cloud diagnosis may include a specific time, a fault point, and a fault of the current cloud diagnosis. Point scan data and solutions, etc. All information related to this vehicle cloud diagnosis.

It can be seen that the method of the embodiment of the present invention can obtain the possible fault point information of the vehicle from the historical record stored in the cloud server when the maintenance personnel inspects the maintenance vehicle, and the maintenance personnel can take the lead to check the possible fault point of the repair. Improve the efficiency and accuracy of inspection and maintenance; when the vehicles are in different geographical locations and are inspected and repaired by different maintenance personnel, the maintenance personnel can use the cloud service data to obtain the vehicle association data, which overcomes the geographical location and The inconvenience of different maintenance vehicles for maintenance personnel.

On the basis of the foregoing method embodiments, the embodiment of the present invention further provides a terminal that can be used to implement the foregoing method embodiment. The following describes an embodiment of the terminal in the embodiment of the present invention.

FIG. 6 is a schematic structural diagram of an embodiment of a terminal according to an embodiment of the present invention. As shown in FIG. 6 , a terminal 600 provided by an embodiment of the present invention may include: an obtaining unit 610, a sending unit 620, a receiving unit 630, a scanning unit 640, a memory 650, a processor 660, and a power management unit 670. , charging unit 680, wherein

The obtaining unit 610 is configured to acquire or create an identifier of the vehicle.

In a particular implementation, if the identification of the vehicle is stored in a storable medium of the terminal, the acquisition unit 610 can read the identification of the vehicle from the storable medium.

In a specific implementation, if the identifier of the vehicle is engraved on the main body of the vehicle, or the traffic sign is set on a pendant such as a license plate, the acquiring unit 610 may scan the identifier of the vehicle by using the scanning unit 640. Scan data is obtained, the scan data including an identification of the vehicle.

In a specific implementation, if the identifier of the vehicle is stored in the related device of the vehicle, the obtaining unit 610 may acquire the vehicle identifier sent by the related device after the sending unit 620 sends the vehicle identification request to the related device. .

Further, in order to use the originally existing identifier as the identifier of the vehicle as much as possible, the obtaining unit 610 may first attempt to acquire the identifier of the vehicle, and further, in order to make the result of the diagnosis better merge with other information, obtain The unit 610 tries to obtain an identity that the vehicle originally exists, such as a license plate number or the like as an identification of the vehicle. After the failure to obtain the identification of the vehicle, an identification of the new vehicle is created.

The sending unit 620 is configured to send a history query request to the cloud server, where the history query request includes an identifier of the vehicle.

The cloud server according to the embodiment of the present invention is a computing service with flexible processing capability, and provides comprehensive service capabilities for various Internet users. The management method is simpler and more efficient than the physical server, and the cloud server can help to quickly build more. Stable and safe application. The cloud server's distributed storage technology is used to consolidate a large number of servers into one supercomputer, providing massive data storage and processing services. The distributed file system and distributed database of the cloud server allow access to common storage resources and realize input and output sharing of application data files.

In a specific implementation, the history record may include a specific time, a fault point, a fault point scan data, a solution, a fault number of the fault point, and a cloud diagnosis count statistics information of the vehicle for each cloud diagnosis, and may be stored in the cloud. Information in the server related to the vehicle cloud diagnosis.

In a specific implementation, the sending unit is further configured to return the result of the current cloud diagnosis to the cloud server, so that the cloud server associates the result of the current cloud diagnosis with the identifier of the vehicle.

The receiving unit 630 is configured to receive a query result returned by the cloud server, where the query result is a result obtained by the cloud server querying the historical record of the vehicle according to the identifier of the vehicle. .

In a specific implementation, if the query result is a history record corresponding to the identifier of the vehicle, the query result returned by the cloud server received by the receiving unit 630 carries the history record. The history record may include the specific time of each cloud diagnosis, the fault point, the fault point scan data, the solution, the number of failures of the fault point, the cloud diagnosis count statistics, and the like, all of which may be stored in the cloud server and the vehicle cloud. Diagnose related information.

The scanning unit 640 is configured to: when the query result is a history record corresponding to the identifier of the vehicle, the scanning unit 640 at least points a fault point in the history record carried in the query result Scanning is performed to obtain scan data for cloud diagnosis of the vehicle; in the case where the query result is a history that does not have an identifier corresponding to the vehicle, the scanning unit is for the vehicle A full scan is performed to perform a cloud diagnosis of the vehicle.

In a specific implementation, the scanning unit is further configured to: if the identifier of the vehicle is engraved on the main body of the vehicle, or the traffic sign is set on a pendant such as a license plate, the scanning unit 540 may pass the identification of the vehicle A scan is performed to obtain scan data, the scan data including an identification of the vehicle.

The memory 650 is configured to store the vehicle identifier acquired by the acquiring unit 610, and the received history query result and history record.

The processor 660 is configured to connect various parts of the entire terminal by using various interfaces and lines, and execute each terminal by running or executing a software program and/or a module stored in the memory, and calling data stored in the memory. Functions and processing data to monitor the terminal as a whole.

The power management unit 670 is configured to perform management supervision on the power of the terminal.

The charging unit 680 is configured to charge the terminal to ensure that the terminal is in a state of sufficient power when working.

FIG. 7 is a schematic structural diagram of another embodiment of a terminal according to an embodiment of the present invention. As shown in FIG. 7, another terminal 700 provided by an embodiment of the present invention may include: an input device 710, an output device 720, a communication device 730, a transceiver device 740, a memory 750, and a processor 760, where:

The input device 710 is configured to receive input data of an external input terminal. In a specific implementation, the input device 710 according to the embodiment of the present invention may include a keyboard, a mouse, a photoelectric input device, a sound input device, a touch input device, a scanner, and the like.

The input device 710 is configured to acquire or create an identifier of the vehicle.

In a particular implementation, if the identification of the vehicle is stored in a storable medium of the terminal, the input device 710 can read the identification of the vehicle from the storable medium.

In a specific implementation, if the identification of the vehicle is engraved on the main body of the vehicle, or the traffic sign is set on a pendant such as a license plate, the input device 710 can scan the identification of the vehicle to obtain a scan. Data, and image recognition of the image to obtain the identity of the vehicle.

Further, in order to use the originally existing logo as the identity of the vehicle as much as possible, the input device 710 may first attempt to acquire the identity of the vehicle, and further, in order to make the result of the diagnosis better merge with other information, input The device 710 tries to obtain an identity that the vehicle originally exists, such as a license plate number or the like as an identification of the vehicle. After the failure to obtain the identification of the vehicle, an identification of the new vehicle is created.

The output device 720 is configured to output output data of the terminal, where the output data includes a received history record from a cloud server, and the like. In a specific implementation, the output device 720 according to the embodiment of the present invention may include a display, a speaker, a printer, and the like.

The communication device 730 is configured to communicate with other devices and a cloud server, and other devices include devices of other vehicles or other terminal devices. In a specific implementation, the communication device 730 of the embodiment of the present invention may be used to log in to the cloud server and send a history query request to the cloud server.

The transceiver 740 can be configured to send data or receive data to other devices or cloud servers through the communication device 730. The transceiver device is specifically configured to receive a history query result from the cloud server, and return the result of the current cloud diagnosis to the cloud server, where the cloud server sends the result of the current cloud diagnosis and the vehicle Identifies the associated store. In a specific implementation, the transceiver 740 of the embodiment of the present invention may include a transceiver device such as a radio frequency antenna.

The memory 750 is configured to store program data with various functions. The data stored by memory 750 in embodiments of the present invention may include vehicle identification, received history, and other program data that may be invoked and executed. In a specific implementation, the memory 750 of the embodiments of the present invention may be a system memory such as volatile (such as RAM), non-volatile (such as ROM, flash memory, etc.), or a combination of the two. In a specific implementation, the memory 750 of the embodiment of the present invention may also be an external memory outside the system, such as a magnetic disk, an optical disk, a magnetic tape, or the like.

The processor 760 is configured to invoke program data stored in the memory 750 and perform the following operations:

If the history query result received by the transceiver device 740 is a history record corresponding to the identifier of the vehicle, the input device 710 scans at least the fault point in the history record carried in the query result to obtain Scanning data to perform cloud diagnosis on the vehicle; if the history query result received by the transceiver 740 is a history that does not correspond to the identification of the vehicle, the input device 710 performs the vehicle on the vehicle A full scan to perform a cloud diagnosis of the vehicle.

It can be seen that, when the received query result is a history record corresponding to the identifier of the vehicle, the terminal in the embodiment of the present invention scans at least the fault point in the history record carried in the query result. Obtaining scan data to perform cloud diagnosis on the vehicle; when the received query result is that there is no history corresponding to the identifier of the vehicle, performing comprehensive scanning on the vehicle to The vehicle performs cloud diagnosis, which can effectively use the historical diagnostic data to scan the possible fault points of the vehicle, and the maintenance personnel can perform effective maintenance and evaluation on the vehicle according to the possible fault points, and the whole process does not need to be used for the vehicle. A comprehensive scan can be completed; when the vehicle is in a different geographical location or is inspected and repaired by different maintenance personnel, the cloud service data can be used to obtain the vehicle associated data to help the maintenance personnel to better maintain and maintain the service. By means of tools, this greatly simplifies the complexity of vehicle maintenance and repair, and also facilitates more efficient vehicle diagnostics.

One of ordinary skill in the art can understand that all or part of the process of implementing the foregoing embodiments can be completed by a computer program to instruct related hardware, and the program can be stored in a computer readable storage medium. When executed, the flow of an embodiment of the methods as described above may be included. The storage medium may be a magnetic disk, an optical disk, a read-only memory (ROM), or a random access memory (RAM).

The above disclosure is only a preferred embodiment of the present invention, and of course, the scope of the present invention is not limited thereto, and those skilled in the art can understand all or part of the process of implementing the above embodiments, and according to the present invention. The equivalent changes required are still within the scope of the invention.

technical problem

Problem solution

Advantageous effects of the invention

Claims

A method for implementing cloud diagnosis of a vehicle, comprising:

The terminal acquires or creates an identifier of the vehicle, and sends a history query request to the cloud server, where the history query request includes an identifier of the vehicle;

The terminal receives the query result returned by the cloud server, where the query result is a result obtained by the cloud server querying the historical record of the vehicle according to the identifier of the vehicle;

If the query result is a history record corresponding to the identifier of the vehicle, at least a fault point in the history record carried in the query result is scanned to obtain scan data to perform cloud on the vehicle Diagnosing; if the result of the query is that there is no history corresponding to the identity of the vehicle, then the vehicle is scanned comprehensively to perform cloud diagnostics on the vehicle.
The method of claim 1 further comprising:

The terminal returns the result of the current cloud diagnosis to the cloud server, so that the cloud server associates the result of the current cloud diagnosis with the identifier of the vehicle.
The method according to claim 1, wherein when the identifier of the vehicle is a license plate number and/or a VIN code, the obtaining the identifier of the vehicle by the terminal specifically includes:

The terminal scans the license plate and/or VIN code location of the vehicle for scan data, the scan data including the license plate number and/or VIN code.
The method according to claim 1, wherein when the identifier of the vehicle is a license plate number and/or a VIN code, the obtaining the identifier of the vehicle by the terminal specifically includes:

Transmitting, by the terminal, a license plate number request and/or a VIN code request to a device in the vehicle;

The terminal receives a license plate number and/or a VIN code transmitted by the device in the vehicle based on the license plate number request and/or the VIN code request.
The method according to claim 1, wherein the terminal further comprises:

The terminal acquires an identifier of the vehicle;

The identifier of the terminal for creating the vehicle specifically includes:

If the terminal fails to obtain the identification of the vehicle, the terminal creates an identification of the vehicle.
A terminal, comprising:

An acquisition unit for acquiring or creating an identification of a vehicle;

a sending unit, configured to send a history query request to the cloud server, where the history query request includes an identifier of the vehicle;

a receiving unit, configured to receive a query result returned by the cloud server, where the query result is a result obtained by the cloud server querying the historical record of the vehicle according to the identifier of the vehicle;

a scanning unit, configured to scan at least a fault point in the history record carried in the query result, where the query result is a history record corresponding to the identifier of the vehicle, thereby Obtaining scan data to perform cloud diagnosis on the vehicle; in a case where the query result is a history that does not have an identifier corresponding to the vehicle, the scanning unit performs a full scan on the vehicle, To perform cloud diagnosis on the vehicle.
The terminal according to claim 6, wherein the sending unit is further configured to return the result of the current cloud diagnosis to the cloud server, for the cloud server to use the result of the current cloud diagnosis and the The identity of the vehicle is associated with the storage.
The terminal according to claim 6, wherein the scanning unit is further configured to: when the identifier of the vehicle is a license plate number and/or a VIN code, the scanning unit and the license plate of the vehicle Scanning at the VIN code location to obtain scan data, the scan data including the license plate number and/or VIN code.
The terminal according to claim 6, wherein the sending unit is further configured to: When the identifier of the vehicle is a license plate number and/or a VIN code, the sending unit sends a license plate number request and/or a VIN code request to the device in the vehicle;

The receiving unit is further configured to receive a license plate number and/or a VIN code sent by the device in the vehicle based on the license plate number request and/or the VIN code request.
The terminal according to claim 6, wherein the obtaining unit is further configured to: before the terminal creates the identifier of the vehicle, the acquiring unit acquires the identifier of the vehicle;

The acquiring unit is specifically configured to: if the terminal acquires the identifier of the vehicle fails, the terminal creates an identifier of the vehicle.