CN111552268B

CN111552268B - Vehicle remote diagnosis method, equipment connector and vehicle connector

Info

Publication number: CN111552268B
Application number: CN202010321688.9A
Authority: CN
Inventors: 刘均; 陈质健
Original assignee: Shenzhen Launch Technology Co Ltd
Current assignee: Shenzhen Launch Technology Co Ltd
Priority date: 2020-04-22
Filing date: 2020-04-22
Publication date: 2023-10-24
Anticipated expiration: 2040-04-22
Also published as: CN111552268A

Abstract

The application discloses a vehicle remote diagnosis method, a device connector, a vehicle connector and a computer readable storage medium. In the scheme of the application, the vehicle to be diagnosed and the diagnostic equipment are not directly connected by the K line, but the vehicle to be diagnosed and the vehicle connector are connected by the K line, the diagnostic equipment and the equipment connector are connected by the K line, and then the vehicle connector and the equipment connector are connected by remote communication. That is, the vehicle connector and the device connector are used as a data transfer station to realize data interaction between the vehicle to be diagnosed and the diagnostic device. According to the scheme, the vehicle to be diagnosed and the diagnosis equipment are decoupled, so that the diagnosis equipment can remotely diagnose the vehicle to be diagnosed, and the application range of the diagnosis equipment based on the K line is improved.

Description

Vehicle remote diagnosis method, equipment connector and vehicle connector

Technical Field

The application belongs to the technical field of automobile communication, and particularly relates to a vehicle remote diagnosis method, a device connector, a vehicle connector and a computer readable storage medium.

Background

Currently, in the vehicle industry, K is used for diagnosis, specifically, operations such as querying, calibrating, programming, etc. are performed on an electronic control unit (Electronic Control Unit, ECU) of the vehicle through K wires, and data interaction between diagnostic equipment and the ECU is performed through K wires, so as to realize diagnosis of a vehicle fault, according to standards of a vehicle diagnostic system defined by the american society of automotive engineers (Society of Automotive Engineers, SAE). However, the diagnosis between the diagnosis device and the vehicle can only be performed by using the K-wire in a short distance in a wired connection manner of the local cable, which brings much inconvenience to the diagnosis of the vehicle.

Disclosure of Invention

The application provides a vehicle remote diagnosis method, a device connector, a vehicle connector and a computer readable storage medium, so that diagnosis equipment can remotely diagnose a vehicle to be diagnosed, and the application range of the diagnosis equipment based on K lines is improved.

In a first aspect, the present application provides a vehicle remote diagnosis method applied to a vehicle remote diagnosis system, the vehicle remote diagnosis system including a diagnosis device, a device connector, a vehicle connector, and a vehicle to be diagnosed, the vehicle remote diagnosis method including:

the device connector receives a diagnosis instruction generated by the diagnosis device based on a K line protocol, encapsulates the diagnosis instruction into a first data packet and transmits the first data packet to the vehicle connector through remote communication, wherein the first data packet uses a data format suitable for the remote communication;

the vehicle connector receives the first data packet, analyzes the first data packet to obtain the diagnosis instruction, and sends the diagnosis instruction to the vehicle to be diagnosed so that the vehicle to be diagnosed generates diagnosis response data according to the diagnosis instruction;

the vehicle connector receiving the diagnostic response data of the vehicle to be diagnosed, and encapsulating the diagnostic response data into a second data packet, the second data packet being transmitted to the device connector by remote communication, the second data packet using a data format suitable for the remote communication;

The device connector receives the second data packet, analyzes the second data packet to obtain the diagnosis response data, and sends the diagnosis response data to the diagnosis device so that the diagnosis device analyzes and processes the diagnosis response data to obtain a diagnosis result.

In a second aspect, the present application provides a vehicle remote diagnosis method applied to a device connector, comprising:

receiving a diagnosis instruction generated by the diagnosis equipment based on a K line protocol;

packaging the diagnosis instruction into a first data packet;

the first data packet is sent to a vehicle connector in a remote communication mode, so that the vehicle connector analyzes the first data packet to obtain the diagnosis instruction, and then sends the diagnosis instruction to a vehicle to be diagnosed, receives diagnosis response data generated by the vehicle to be diagnosed according to the diagnosis instruction, and packages the diagnosis response data into a second data packet;

receiving the second data packet transmitted by the vehicle connector through remote communication;

analyzing the second data packet to obtain the diagnosis response data;

and sending the diagnosis response data to the diagnosis equipment so that the diagnosis equipment analyzes and processes the diagnosis response data to obtain a diagnosis result.

Optionally, before the receiving the diagnosis instruction generated by the diagnosis device based on the K-wire protocol, the vehicle remote diagnosis method further includes:

acquiring vehicle information of a vehicle to be diagnosed;

determining corresponding K line configuration information according to the vehicle information;

and establishing K line connection with the diagnostic equipment according to the configuration information.

Optionally, the determining the corresponding K-wire configuration information according to the vehicle information specifically includes:

determining the vehicle type information in the vehicle information;

and determining corresponding K line configuration information in a preset configuration table according to the vehicle type information.

In a third aspect, the present application provides a vehicle remote diagnosis method applied to a vehicle connector, comprising:

receiving a first data packet sent by the device connector through remote communication;

analyzing the first data packet to obtain a diagnosis instruction, wherein the diagnosis instruction is generated by a diagnosis device based on a K line protocol and is packaged into the first data packet after being sent to a device connector;

the diagnosis instruction is sent to a vehicle to be diagnosed, so that the vehicle to be diagnosed generates diagnosis response data according to the diagnosis instruction;

receiving the diagnosis response data sent by the vehicle to be diagnosed;

Encapsulating the diagnostic response data into a second data packet;

and sending the second data packet to the equipment connector through remote communication so that the equipment connector analyzes the second data packet to obtain diagnosis response data, and sending the diagnosis response data to the diagnosis equipment through the equipment connector so that the diagnosis equipment analyzes and processes the diagnosis response data to obtain a diagnosis result.

Optionally, before the receiving the first data packet sent by the device connector through remote communication, the vehicle remote diagnosis method further includes:

acquiring vehicle information of the vehicle to be diagnosed;

and establishing K line connection with the vehicle to be diagnosed according to the K line configuration information.

determining the vehicle type information and the vehicle electronic control unit ECU information in the vehicle information;

determining corresponding K line configuration information according to the vehicle type information and the ECU information;

the establishing a K-wire connection with the vehicle to be diagnosed according to the K-wire configuration information specifically includes:

Carrying out BPS configuration on the K line communication data transmission rate according to the K line configuration information;

and establishing K line connection with the vehicle to be diagnosed according to the K line configuration information and the BPS.

Optionally, the diagnostic command is a K line level signal;

the analyzing the first data packet to obtain a diagnostic instruction specifically includes:

analyzing the first data packet to obtain a K line level signal;

processing the K line level signal to obtain a first level signal and a second level signal;

and forming a diagnosis command by the first level signal and the second level signal according to time sequence.

Optionally, the processing the K line level signal to obtain a first level signal and a second level signal specifically includes:

separating the K line level signals to obtain initial first level signals and initial second level signals;

converting a regular signal in the initial first level signal into a newly added second level signal;

determining a part of the initial first level signal except the regular signal as a first level signal; the initial second level signal and the newly added second level signal are combined to form a second level signal.

In a fourth aspect, the present application provides a device connector comprising a memory, a processor and a computer program stored in the memory and executable on the processor, the processor implementing the steps of the method of the second aspect when executing the computer program.

In a fifth aspect, the present application provides a vehicle connector comprising a memory, a processor and a computer program stored in the memory and executable on the processor, the processor implementing the steps of the method of the third aspect when the computer program is executed.

In a sixth aspect, the present application provides a computer readable storage medium storing a computer program which when executed by a processor performs the steps of the method of the second aspect as described above; alternatively, the computer program as described above implements the steps of the method as described in the third aspect when executed by a processor.

In a seventh aspect, the present application provides a computer program product comprising a computer program which, when executed by one or more processors, implements the steps of the method of the second aspect as described above; alternatively, the computer program as described above may implement the steps of the method of the third aspect as described above when executed by one or more processors.

From the above, according to the scheme of the application, the diagnosis equipment does not directly establish K-wire connection with the vehicle to be diagnosed, but establishes K-wire connection with the equipment connector, and sends a diagnosis instruction to the equipment connector; the device connector encapsulates the received diagnostic instructions into a first data packet, then sends the first data packet to the vehicle connector, and after the vehicle connector analyzes the first data packet to obtain the diagnostic instructions, sends the diagnostic instructions to the vehicle. The process decouples the diagnosis device from the vehicle to be diagnosed through the device connector and the vehicle connector, and realizes remote data interaction of the diagnosis device and the vehicle to be diagnosed based on the K line. It will be appreciated that the advantages of the second to seventh aspects may be found in the relevant description of the first aspect, and are not described here again.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings used in the embodiments or the description of the prior art will be briefly described, and it is possible for a person skilled in the art to obtain other drawings from these drawings without inventive effort.

FIG. 1 is a network architecture diagram of a vehicle remote diagnostic system provided by an embodiment of the present application;

FIG. 2 is a schematic diagram of a flow chart for implementing a vehicle remote diagnosis method according to an embodiment of the present application;

FIG. 3 is a schematic flow chart of another implementation of a vehicle remote diagnosis method according to an embodiment of the present application;

FIG. 4 is a schematic flow chart of another implementation of a vehicle remote diagnosis method according to an embodiment of the present application;

fig. 5 is a schematic diagram of a data format of a regular signal in the vehicle remote diagnosis method according to the embodiment of the present application;

fig. 6 is a block diagram of a vehicle remote diagnosis apparatus according to an embodiment of the present application;

FIG. 7 is a block diagram of another vehicle remote diagnosis apparatus according to an embodiment of the present application;

fig. 8 is a schematic structural view of a device connector according to an embodiment of the present application;

fig. 9 is a schematic structural view of a vehicle connector according to an embodiment of the present application.

Detailed Description

In the following description, for purposes of explanation and not limitation, specific details are set forth such as the particular system architecture, techniques, etc., in order to provide a thorough understanding of the embodiments of the present application. It will be apparent, however, to one skilled in the art that the present application may be practiced in other embodiments that depart from these specific details. In other instances, detailed descriptions of well-known systems, devices, circuits, and methods are omitted so as not to obscure the description of the present application with unnecessary detail.

Currently, when a K-wire connection is established with a vehicle to be diagnosed to perform K-wire diagnosis, considering that the K-wire connection often depends on a local cable, the transmission distance of the local cable is often limited, which requires that the diagnostic device can perform diagnostic operations on the vehicle to be diagnosed only within a limited distance through the local cable. Once the diagnostic equipment is far away from the vehicle to be diagnosed, the K line diagnosis cannot be performed in the mode, so that the application scene of the K line diagnosis is greatly limited. Based on the above, the embodiment of the application provides a vehicle remote diagnosis method, a device connector, a network connector and a computer readable storage medium, and decoupling of a vehicle to be diagnosed and a diagnosis device can be realized through the device connector and the network connector, so that the diagnosis device can remotely diagnose the vehicle to be diagnosed based on K lines. In order to illustrate the technical scheme provided by the embodiment of the application, the following description is made by specific embodiments.

The following describes a vehicle remote diagnosis method provided by the embodiment of the application. Referring to fig. 1, the vehicle remote diagnosis method is applied to a vehicle remote diagnosis system, and the vehicle remote diagnosis system comprises a vehicle to be diagnosed, a vehicle connector, an equipment connector and diagnosis equipment; the vehicle to be diagnosed and the vehicle connector perform data interaction in a K-wire communication mode; the vehicle connector and the equipment connector interact data in a remote communication mode; the device connector and the diagnostic device also perform data interaction in a K-wire communication mode.

In the vehicle remote diagnosis system, the vehicle to be diagnosed is a vehicle with a diagnosis requirement at present, that is, any vehicle with a diagnosis requirement can be used as the vehicle to be diagnosed to be connected to the vehicle remote diagnosis system; the vehicle connector can serve as a data transfer station and transfer data to the vehicle or equipment connector to be diagnosed; the device connector can also be used as a data transfer station to transfer data to the vehicle connector or the diagnostic device; the diagnostic device includes, but is not limited to, various vehicle scanning tools such as a handheld diagnostic instrument or a PC, and a diagnostic database is stored on the diagnostic device, through which diagnostic response data sent by a vehicle to be diagnosed can be diagnosed and a diagnostic result of the vehicle to be diagnosed can be fed back.

Referring to fig. 2, fig. 2 shows a schematic diagram of an interaction flow among a vehicle to be diagnosed, a vehicle connector, a device connector and a diagnostic device, and the vehicle remote diagnosis method includes:

step 201, the device connector receives a diagnosis instruction generated by the diagnosis device based on a K-wire protocol;

in the embodiment of the application, when a vehicle needing diagnosis exists, namely, when the vehicle to be diagnosed exists, the diagnosis equipment can start the data interaction of the wheel. The diagnostic device may generate diagnostic instructions based on the K-wire protocol and send the diagnostic instructions into the device connector via the K-wire protocol. Specifically, the above diagnostic instructions are represented as K line level signals.

Step 202, the device connector encapsulates the diagnostic instructions into a first data packet;

in the embodiment of the application, after receiving the diagnostic command, the device connector further encapsulates the diagnostic command to encapsulate the diagnostic command into the first data packet. Specifically, the encapsulation mode used in encapsulating the first data packet is related to the transmission protocol used in subsequent remote communications. For example, if the transmission is performed by the hypertext transfer protocol (HyperText Transfer Protocol, HTTP) later, the diagnostic command will be encapsulated based on the HTTP protocol in this step, that is, the first packet will be embodied in the form of an HTTP packet, which is not limited herein.

Step 203, the device connector sends the first data packet to the vehicle connector through remote communication;

in the embodiment of the application, after the device connector encapsulates the diagnosis instruction into the first data packet, the first data packet may be sent to a vehicle connector connected to the vehicle to be diagnosed through remote communication. It should be noted that, between the vehicle connector and the device connector, remote communication may be implemented by using a preset server as a data transfer station; alternatively, the remote communication may be implemented by a peer-to-peer (P2P) technology; alternatively, the remote communication may be realized by a wired network; alternatively, the remote communication may be implemented through a cellular mobile network such as 2G, 3G, 4G, or 5G, and the specific manner in which the remote communication is implemented is not limited herein.

Step 204, the vehicle connector receives the first data packet, analyzes the first data packet, and obtains the diagnostic command;

in the embodiment of the application, when the vehicle connector receives the first data packet sent by the equipment connector through remote communication, the first data packet can be analyzed to obtain the diagnosis instruction carried by the first data packet.

Step 205, the vehicle connector sends the diagnostic command to the vehicle to be diagnosed;

in the embodiment of the application, the vehicle connector can send the diagnosis instruction to the vehicle to be diagnosed through a K-wire protocol.

Step 206, the vehicle to be diagnosed generates diagnosis response data according to the diagnosis instruction;

in the embodiment of the application, the vehicle to be diagnosed can generate corresponding diagnosis response data under the indication of the diagnosis instruction, wherein the diagnosis response data comprises, but is not limited to, various parameters related to vehicle diagnosis, such as the current running speed of the vehicle, the engine displacement, and/or the transmission parameters.

Step 207, the vehicle to be diagnosed feeds back the diagnosis response data to the vehicle connector;

in the embodiment of the application, the vehicle to be diagnosed can send the diagnosis response data to the vehicle connector through a K-wire protocol.

Step 208, the vehicle connector receives the diagnosis response data and encapsulates the diagnosis response data into a second data packet;

in an embodiment of the present application, after receiving the diagnosis response data, the vehicle connector further encapsulates the diagnosis response data to encapsulate the diagnosis instruction into a second data packet. Specifically, the encapsulation mode used in encapsulating the second data packet is related to the transmission protocol used in the subsequent remote communication. For example, if the transmission is performed by the HTTP protocol, the diagnostic response data will be encapsulated based on the HTTP protocol in this step, that is, the second packet will be embodied in the form of an HTTP packet, which is not limited herein. It should be noted that, since the transmission protocol adopted when the vehicle connector and the device connector interact data is always kept unchanged, the data format of the second data packet is always the same as the data format of the first data packet.

Step 209, the vehicle connector sends the second data packet to the device connector through remote communication;

in the embodiment of the present application, the implementation manner of step 209 is similar to that of step 203, except that the transmitting end is changed by the device connector to the vehicle connector, the receiving end is changed by the vehicle connector to the device connector, and the transmitted data is changed by the first data packet to the second data packet, so the relevant explanation and description of this step can refer to step 203.

Step 210, the device connector receives the second data packet and parses the second data packet to obtain the diagnosis response data;

in the embodiment of the application, when the device connector receives the second data packet sent by the vehicle connector through remote communication, the second data packet can be parsed to obtain the diagnosis response data carried by the second data packet.

Step 211, the device connector transmits the diagnosis response data to the diagnosis device;

in the embodiment of the application, the device connector can send the diagnosis response data to the diagnosis device through a K-wire protocol.

In step 212, the diagnostic device analyzes and processes the diagnostic response data to obtain a diagnostic result.

In the embodiment of the application, the diagnosis equipment analyzes and processes the diagnosis response data through the locally stored diagnosis database so as to obtain a diagnosis result obtained by diagnosing the vehicle to be diagnosed. The diagnosis result can be output through a display screen, and a diagnostician can be informed of possible problems of the vehicle to be diagnosed in time and intuitively; alternatively, the above diagnosis result may be output to a mobile client associated with the vehicle to be diagnosed, and the manner of outputting the above diagnosis result is not limited herein. The diagnostic equipment completes one round of data interaction with the vehicle to be diagnosed. It should be noted that in embodiments of the present application, each round of data interaction needs to be initiated by the diagnostic device side.

From the above, in the embodiment of the present application, the diagnostic device no longer directly establishes K-wire connection with the vehicle to be diagnosed, but establishes K-wire connection with the device connector, and sends a diagnostic instruction to the device connector; the device connector packages the received diagnosis instruction into a first data packet, then sends the first data packet to the vehicle connector, the vehicle connector analyzes the first data packet to obtain the diagnosis instruction, then sends the diagnosis instruction to the vehicle, and the vehicle feeds back diagnosis response data to the diagnosis device through the vehicle connector and the device connector according to the diagnosis instruction, so that the diagnosis device obtains a diagnosis result of the vehicle based on the diagnosis response data analysis. The process decouples the diagnosis device from the vehicle to be diagnosed through the device connector and the vehicle connector, and realizes remote data interaction of the diagnosis device and the vehicle to be diagnosed based on the K line.

Another vehicle remote diagnosis method provided in the embodiment of the present application is described below, and the vehicle remote diagnosis method is applied to a device connector. Referring to fig. 3, fig. 3 shows a specific implementation flow of the vehicle remote diagnosis method, which is described in detail as follows:

step 301, receiving a diagnosis instruction generated by a diagnosis device based on a K line protocol;

step 302, encapsulating the diagnostic instruction into a first data packet;

step 303, transmitting the first data packet to a vehicle connector through a remote communication manner, so that the vehicle connector analyzes the first data packet to obtain the diagnosis instruction, and then transmits the diagnosis instruction to a vehicle to be diagnosed, receives diagnosis response data generated by the vehicle to be diagnosed according to the diagnosis instruction, and encapsulates the diagnosis response data into a second data packet;

step 304, receiving the second data packet sent by the vehicle connector through remote communication;

step 305, analyzing the second data packet to obtain the diagnosis response data;

and 306, transmitting the diagnosis response data to the diagnosis equipment so that the diagnosis equipment analyzes and processes the diagnosis response data to obtain a diagnosis result.

Step 301 is the same as or similar to step 201, step 302 is the same as or similar to step 202, step 303 is the same as or similar to step 203, steps 304 and 305 are the same as or similar to step 210, and step 306 is the same as or similar to step 211, which will not be described herein.

Optionally, before the step 301, the vehicle remote diagnosis method further includes:

acquiring vehicle information of a vehicle to be diagnosed;

In the embodiment of the application, the vehicle information is specifically used for identifying the vehicle to be diagnosed. Because the number of the current automobile manufacturers is large, in order to better establish the K-wire connection between the equipment connector and the diagnostic equipment, the vehicle information of the vehicle to be diagnosed can be acquired first, and then the corresponding K-wire configuration information is determined according to the vehicle information, so that the equipment connector can establish the K-wire connection with the diagnostic equipment according to the configuration information. Specifically, since the differences between different vehicles are often represented in the vehicle types, that is, the vehicles of the same vehicle type may often adopt the same data processing flow, a diagnostician may create a configuration table in advance according to different vehicle types, and set K line configuration information associated with each vehicle type in the configuration table; the manner of determining the K-wire configuration information employed by the device connector may be: and determining the vehicle type information in the vehicle information, and determining corresponding K line configuration information in a preset configuration table according to the vehicle type information.

In some embodiments, the vehicle type of the vehicle to be diagnosed may be obtained by analyzing a vehicle identification code (Vehicle Identification Number, VIN) of the vehicle to be diagnosed after the vehicle connector reads the vehicle identification code; alternatively, the vehicle type of the vehicle to be diagnosed may be directly input into the vehicle connector by the owner of the vehicle to be diagnosed, which is not limited herein. After the vehicle connector acquires the vehicle type of the vehicle to be diagnosed, the vehicle type of the vehicle to be diagnosed can be synchronized into the device connector through remote communication, and the device connector can then determine corresponding K line configuration information according to the acquired vehicle type of the vehicle to be diagnosed.

In some embodiments, the K-line configuration information specifically includes: the K line pin used for data transmission by the K line protocol, the data transmission rate (BPS) used for data transmission by the K line protocol, and the like are not limited herein.

It is noted that the K-wire connection is established by means of a local cable, i.e. a wired connection between the device connector and the diagnostic device. The K-wire protocol includes, but is not limited to, ISO 14230, ISO 9421, SAE J2740, SAE J281, and the like, and is not described herein.

From the above, in the embodiment of the present application, the diagnostic device no longer directly establishes K-wire connection with the vehicle to be diagnosed, but establishes K-wire connection with the device connector, and sends a diagnostic instruction to the device connector; the device connector also packages the received diagnosis instruction into a first data packet and sends the first data packet to the vehicle connector, and the vehicle connector analyzes the first data packet to obtain the diagnosis instruction and then sends the diagnosis instruction to the vehicle. The process decouples the diagnosis device from the vehicle to be diagnosed through the device connector and the vehicle connector, and realizes remote data interaction of the diagnosis device and the vehicle to be diagnosed based on the K line.

A further vehicle remote diagnosis method provided in the embodiment of the present application is described below, and the vehicle remote diagnosis method is applied to a vehicle connector. Referring to fig. 4, fig. 4 shows a specific implementation flow of the vehicle remote diagnosis method, which is described in detail as follows:

step 401, receiving a first data packet sent by a device connector through remote communication;

step 402, analyzing the first data packet to obtain a diagnosis instruction, wherein the diagnosis instruction is generated by a diagnosis device based on a K line protocol and is packaged into the first data packet after being sent to a device connector;

Step 403, sending the diagnosis instruction to a vehicle to be diagnosed, so that the vehicle to be diagnosed generates diagnosis response data according to the diagnosis instruction;

step 404, receiving the diagnosis response data sent by the vehicle to be diagnosed;

step 405, encapsulating the diagnosis response data into a second data packet;

and step 406, transmitting the second data packet to the device connector through remote communication, so that the device connector analyzes the second data packet to obtain diagnosis response data, and transmitting the diagnosis response data to the diagnosis device through the device connector, so that the diagnosis device analyzes and processes the diagnosis response data to obtain a diagnosis result.

Wherein steps 401 and 402 are the same as or similar to step 204, step 403 is the same as or similar to step 205, steps 404 and 405 are the same as or similar to step 208, and step 406 is the same as or similar to step 209, which are not described herein.

Optionally, before the step 401, the vehicle remote diagnosis method further includes:

acquiring vehicle information of the vehicle to be diagnosed;

In the embodiment of the application, the vehicle information is specifically used for identifying the vehicle to be diagnosed. Because the number of the current automobile manufacturers is large, in order to better establish the K-wire connection between the vehicle connector and the vehicle to be diagnosed, vehicle information of the vehicle to be diagnosed can be acquired first, and then corresponding K-wire configuration information is determined according to the vehicle information, so that the equipment connector can establish the K-wire connection with the diagnostic equipment according to the configuration information. Specifically, the vehicle connector is connected to the vehicle to be diagnosed through the ECU of the vehicle to be diagnosed, so the determination manner of the K-wire configuration information may be: and determining the vehicle type information and the ECU information in the vehicle information, and then determining corresponding K line configuration information according to the vehicle type information and the ECU information.

In some embodiments, the vehicle type of the vehicle to be diagnosed may be obtained by analyzing a vehicle identification code of the vehicle to be diagnosed after the vehicle connector reads the vehicle identification code; alternatively, the vehicle type of the vehicle to be diagnosed may be directly input into the vehicle connector by the owner of the vehicle to be diagnosed, which is not limited herein. After the vehicle connector acquires the vehicle type of the vehicle to be diagnosed, the vehicle type of the vehicle to be diagnosed can be synchronized into the equipment connector through remote communication.

In some embodiments, the K-line configuration information specifically includes: the K line pin used in data transmission by the K line protocol, the data transmission rate used in data transmission by the K line protocol, and the like are not limited herein. Based on the above, the K-wire connection with the vehicle to be diagnosed is established according to the K-wire configuration information, which is specifically expressed as follows: and performing K line communication BPS configuration according to the K line configuration information, and establishing K line connection with the vehicle to be diagnosed according to the K line configuration information and the BPS.

It is noted that the K-wire connection is established by means of a local cable, i.e. a wired connection between the vehicle connector and the vehicle to be diagnosed. The K-wire protocol includes, but is not limited to, ISO 14230, ISO 9421, SAE J2740, SAE J281, and the like, and is not described herein.

Specifically, the diagnostic command is a K line level signal; accordingly, the step 402 specifically includes:

analyzing the first data packet to obtain a K line level signal;

In the embodiment of the application, the vehicle connector can send the diagnosis instruction which is represented as the level signal to the vehicle to be diagnosed through the K line protocol. According to the K-wire protocol, the diagnostic command generated and transmitted by the diagnostic device includes level data and serial port data, and the level data and serial port data are represented by level signals, that is, the data carried by the first data packet are actually K-wire level signals; based on this, the vehicle connector first obtains only the K-line level signal after analyzing the first packet; the vehicle connector can then process the K-wire level signal according to a preset K-wire data transmission format to obtain a first level signal and a second level signal, wherein the first level signal is used for representing the real level (i.e., level data) of the K-wire pin of the diagnostic device, and the second level signal is used for representing the K-wire serial port data of the diagnostic device; then, in order to avoid the error of signal reading caused by the error time sequence of the vehicle to be diagnosed, the vehicle connector also needs to form the diagnosis instruction by the first level signal and the second level signal according to the time sequence, and at this time, the vehicle connector finishes analyzing the first data packet and obtains the diagnosis instruction carried by the first data packet.

Specifically, the step of processing the K line level signal to obtain a first level signal and a second level signal includes:

In the embodiment of the application, the K line level signal can be subjected to signal separation according to the data structure adopted by the K line protocol so as to obtain the initial first level signal and the initial second level signal. Wherein the initial first level signal carries a regular signal. The data format of the regular signal is shown in fig. 5: it is composed of a start bit, seven data bits, a check bit and a stop bit; that is, the signal satisfying the data format shown in fig. 5 is a regular signal. The data bits of the regular signal are related to the K-line serial data. Therefore, a regular signal in the initial first level signal can be converted into a new level signal and recorded as a newly added second level signal, then a signal remaining after the initial first level signal is removed from the regular signal can be determined as a first level signal, and a signal obtained by combining the initial second level signal and the newly added second level signal can be determined as a second level signal. It should be noted that when converting the regular signal into the newly added second level signal, conversion is performed based on the configured BPS, so as to avoid a conversion error caused by a read signal misalignment.

From the above, in the embodiment of the present application, the vehicle to be diagnosed no longer directly establishes K-wire connection with the diagnostic device, but establishes K-wire connection with the vehicle connector, and receives the diagnostic instruction sent by the diagnostic device through the vehicle connector; and the vehicle connector packages the diagnosis response data fed back by the vehicle to be diagnosed into a diagnosis response data packet and then sends the diagnosis response data packet to the equipment connector, and the equipment connector analyzes the diagnosis response data packet to obtain diagnosis response data and then sends the diagnosis response data to the diagnosis equipment. The process decouples the vehicle to be diagnosed from the diagnosis equipment through the vehicle connector and the equipment connector, and realizes remote data interaction of the vehicle to be diagnosed and the diagnosis equipment based on the K line.

Corresponding to the vehicle remote diagnosis method applied to the equipment connector, the embodiment of the application provides a vehicle remote diagnosis device applied to the equipment connector. As shown in fig. 6, the vehicle remote diagnosis device 600 includes:

a diagnostic instruction receiving unit 601, configured to receive a diagnostic instruction generated by a diagnostic device based on a K-wire protocol;

a first packet encapsulation unit 602, configured to encapsulate the diagnostic instruction into a first packet;

A first data packet sending unit 603, configured to send the first data packet to a vehicle connector through a remote communication manner, so that the vehicle connector parses the first data packet to obtain the diagnostic instruction, and then send the diagnostic instruction to a vehicle to be diagnosed, receive diagnostic response data generated by the vehicle to be diagnosed according to the diagnostic instruction, and package the diagnostic response data into a second data packet;

a second packet receiving unit 604 for receiving the second packet transmitted by the vehicle connector through remote communication;

a second packet parsing unit 605 for parsing the second packet to obtain the diagnosis response data;

and a diagnostic response data transmitting unit 606 configured to transmit the diagnostic response data to the diagnostic device, so that the diagnostic device performs an analysis process on the diagnostic response data to obtain a diagnostic result.

Optionally, the vehicle remote diagnosis device 600 further includes:

a vehicle information acquisition unit configured to acquire vehicle information of a vehicle to be diagnosed;

a configuration information determining unit, configured to determine corresponding K-line configuration information according to the vehicle information;

and the connection establishing unit is used for establishing K line connection with the diagnostic equipment according to the configuration information.

Optionally, the configuration information determining unit is specifically configured to determine vehicle type information in the vehicle information, and determine corresponding K-line configuration information in a preset configuration table according to the vehicle type information.

Corresponding to the vehicle remote diagnosis method applied to the vehicle connector, the embodiment of the application provides a vehicle remote diagnosis device applied to the vehicle connector. As shown in fig. 7, the vehicle remote diagnosis device 700 includes:

a first packet receiving unit 701 for receiving a first packet transmitted by the device connector through remote communication;

A first data packet parsing unit 702, configured to parse the first data packet to obtain a diagnostic instruction, where the diagnostic instruction is generated by a diagnostic device based on a K-wire protocol, and is encapsulated into the first data packet after being sent to a device connector;

a diagnostic instruction transmitting unit 703 configured to transmit the diagnostic instruction to a vehicle to be diagnosed, so that the vehicle to be diagnosed generates diagnostic response data according to the diagnostic instruction;

a diagnosis response data receiving unit 704 configured to receive the diagnosis response data transmitted from the vehicle to be diagnosed;

a second packet encapsulation unit 705 for encapsulating the diagnosis response data into a second packet;

and a second data packet sending unit 706, configured to send the second data packet to the device connector through remote communication, so that the device connector parses the second data packet to obtain diagnostic response data, and send the diagnostic response data to the diagnostic device through the device connector, so that the diagnostic device performs analysis processing on the diagnostic response data to obtain a diagnostic result.

Optionally, the vehicle remote diagnosis device 700 further includes:

a vehicle information acquisition unit configured to acquire vehicle information of the vehicle to be diagnosed;

and the connection establishment unit is used for establishing K-wire connection with the vehicle to be diagnosed according to the K-wire configuration information.

Optionally, the configuration information determining unit is specifically configured to determine vehicle type information and vehicle electronic control unit ECU information in the vehicle information, and determine corresponding K line configuration information according to the vehicle type information and the ECU information;

the connection establishing unit is specifically configured to perform K-wire communication data transmission rate BPS configuration according to the K-wire configuration information, and establish K-wire connection with the vehicle to be diagnosed according to the K-wire configuration information and the BPS.

Optionally, the diagnostic command is a K line level signal; the first packet parsing unit includes:

the analysis subunit is used for analyzing the first data packet to obtain a K line level signal;

the processing subunit is used for processing the K line level signal to obtain a first level signal and a second level signal;

and the composition subunit is used for composing the first level signal and the second level signal into a diagnosis instruction according to time sequence.

Optionally, the processing subunit includes:

A separation subunit, configured to separate the K-line level signal to obtain an initial first level signal and an initial second level signal;

a conversion subunit, configured to convert a regular signal in the initial first level signal into a newly added second level signal;

and the determining subunit is used for determining the part of the initial first level signal except the regular signal as a first level signal and combining the initial second level signal and the newly added second level signal into a second level signal.

The embodiment of the application also provides a device connector. Referring to fig. 8, fig. 8 is a schematic structural diagram of a device connector according to an embodiment of the application. As shown in fig. 8, the device connector 8 of this embodiment includes: at least one processor 80 (only one processor is shown in fig. 8), a memory 81 and a computer program 82 stored in the memory 81 and executable on the at least one processor 80, the processor 80 implementing the steps in the method embodiments applied to the device connector when executing the computer program 82, for example, may be implemented:

packaging the diagnosis instruction into a first data packet;

analyzing the second data packet to obtain the diagnosis response data;

The device connector may include, but is not limited to, a processor 80, a memory 81. It will be appreciated by those skilled in the art that fig. 8 is merely an example of the device connector 8 and is not meant to be limiting of the device connector 8, and may include more or fewer components than shown, or may combine certain components, or different components, such as may also include input-output devices, network access devices, etc.

The processor 80 may be a central processing unit (Central Processing Unit, CPU), the processor 80 may also be other general purpose processors, digital signal processors (Digital Signal Processor, DSP), application specific integrated circuits (Application Specific Integrated Circuit, ASIC), field-programmable gate arrays (Field-Programmable Gate Array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.

The memory 81 may in some embodiments be an internal storage unit of the device connector 8, such as a hard disk or a memory of the device connector 8. The memory 81 may also be an external storage device of the device connector 8, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card) or the like, which are provided on the device connector 8 in other embodiments. Further, the memory 81 may include both the internal storage unit and the external storage device of the device connector 8. The memory 81 is used for storing an operating system, an application program, a boot loader (BootLoader), data, other programs, and the like, such as program codes of the computer programs. The above-described memory 81 may also be used to temporarily store data that has been output or is to be output.

From the above, in the embodiment of the present application, the vehicle to be diagnosed no longer directly establishes K-wire connection with the diagnostic device, but establishes K-wire connection with the vehicle device connector, and receives the diagnostic instruction sent by the diagnostic device through the vehicle device connector; and the vehicle equipment connector packages the diagnosis response data fed back by the vehicle to be diagnosed into a diagnosis response data packet, then sends the diagnosis response data packet to the equipment connector, and after the equipment connector analyzes the diagnosis response data packet to obtain diagnosis response data, sends the diagnosis response data to the diagnosis equipment. The process decouples the vehicle to be diagnosed and the diagnosis equipment through the vehicle equipment connector and the equipment connector, and realizes remote data interaction of the vehicle to be diagnosed and the diagnosis equipment based on K lines.

The embodiment of the application also provides a vehicle connector. Referring to fig. 9, fig. 9 is a schematic structural diagram of a vehicle connector according to an embodiment of the application. As shown in fig. 9, the vehicle connector 9 of this embodiment includes: at least one processor 90 (only one processor is shown in fig. 9), a memory 91, and a computer program 92 stored in the memory 91 and executable on the at least one processor 90, the processor 90 implementing steps in an embodiment of a method applied to a vehicle connector when executing the computer program 92, for example, may be implemented:

receiving the diagnosis response data sent by the vehicle to be diagnosed;

encapsulating the diagnostic response data into a second data packet;

The vehicle connector may include, but is not limited to, a processor 90, a memory 91. It will be appreciated by those skilled in the art that fig. 9 is merely an example of the vehicle connector 9 and is not intended to be limiting of the vehicle connector 9, and may include more or fewer components than shown, or may combine certain components, or may include different components, such as input-output devices, network access devices, etc.

The processor 90 may be a central processing unit (Central Processing Unit, CPU), the processor 90 may also be other general purpose processors, digital signal processors (Digital Signal Processor, DSP), application specific integrated circuits (Application Specific Integrated Circuit, ASIC), field-programmable gate arrays (Field-Programmable Gate Array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.

The memory 91 may in some embodiments be an internal storage unit of the vehicle connector 9, such as a hard disk or a memory of the vehicle connector 9. The memory 91 may also be an external storage device of the vehicle connector 9, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash Card (Flash Card) or the like, which are provided on the vehicle connector 9 in other embodiments. Further, the memory 91 may include both the internal storage unit and the external storage device of the vehicle connector 9. The memory 91 is used for storing an operating system, an application program, a boot loader (BootLoader), data, other programs, and the like, such as program codes of the computer programs. The above-described memory 91 may also be used to temporarily store data that has been output or is to be output.

It will be apparent to those skilled in the art that, for convenience and brevity of description, only the above-described division of the functional units and modules is illustrated, and in practical application, the above-described functional distribution may be performed by different functional units and modules according to needs, i.e. the internal structure of the apparatus is divided into different functional units or modules to perform all or part of the above-described functions. The functional units and modules in the embodiment may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit, where the integrated units may be implemented in a form of hardware or a form of a software functional unit. In addition, the specific names of the functional units and modules are only for distinguishing from each other, and are not used for limiting the protection scope of the present application. The specific working process of the units and modules in the above system may refer to the corresponding process in the foregoing method embodiment, which is not described herein again.

The embodiment of the application also provides a computer readable storage medium, wherein the computer readable storage medium stores a computer program, and the computer program realizes the steps in the embodiment of the method when being executed by a processor.

Embodiments of the present application provide a computer program product which, when run on a connector, causes the connector to perform steps that enable the implementation of the method embodiments described above.

The integrated units described above, if implemented in the form of software functional units and sold or used as stand-alone products, may be stored in a computer readable storage medium. Based on such understanding, the present application may implement all or part of the flow of the method of the above embodiment, and may be implemented by a computer program to instruct related hardware, where the computer program may be stored in a computer readable storage medium, where the computer program, when executed by a processor, may implement the steps of each of the method embodiments described above. The computer program comprises computer program code, and the computer program code can be in a source code form, an object code form, an executable file or some intermediate form and the like. The computer readable medium may include at least: any entity or device capable of carrying computer program code to the camera device/connector, recording medium, computer Memory, read-Only Memory (ROM), random access Memory (RAM, random Access Memory), electrical carrier signals, telecommunications signals, and software distribution media. Such as a U-disk, removable hard disk, magnetic or optical disk, etc. In some jurisdictions, computer readable media may not be electrical carrier signals and telecommunications signals in accordance with legislation and patent practice.

In the foregoing embodiments, the descriptions of the embodiments are emphasized, and in part, not described or illustrated in any particular embodiment, reference is made to the related descriptions of other embodiments.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

In the embodiments provided in the present application, it should be understood that the disclosed apparatus/network device and method may be implemented in other manners. For example, the apparatus/network device embodiments described above are merely illustrative, e.g., the division of modules or elements described above is merely a logical functional division, and there may be additional divisions in actual implementation, e.g., multiple elements or components may be combined or integrated into another system, or some features may be omitted, or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection via interfaces, devices or units, which may be in electrical, mechanical or other forms.

The units described above as separate components may or may not be physically separate, and components shown as units may or may not be physical units, may be located in one place, or may be distributed over a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

The above embodiments are only for illustrating the technical solution of the present application, and not for limiting the same; although the application has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical scheme described in the foregoing embodiments can be modified or some technical features thereof can be replaced by equivalents; such modifications and substitutions do not depart from the spirit and scope of the technical solutions of the embodiments of the present application, and are intended to be included in the scope of the present application.

Claims

1. A vehicle remote diagnosis method, characterized in that the vehicle remote diagnosis method is applied to a vehicle remote diagnosis system including a diagnosis device, a device connector, a vehicle connector, and a vehicle to be diagnosed, the vehicle remote diagnosis method comprising:

the vehicle connector receives the first data packet, analyzes the first data packet to obtain the diagnosis instruction, and sends the diagnosis instruction to the vehicle to be diagnosed so that the vehicle to be diagnosed generates diagnosis response data according to the diagnosis instruction; the diagnostic response data is a parameter related to vehicle diagnosis, comprising: speed at which the vehicle is currently operating, engine displacement, and/or transmission parameters;

the vehicle connector receives the diagnosis response data of the vehicle to be diagnosed, encapsulates the diagnosis response data into a second data packet, and transmits the second data packet to the device connector through remote communication, wherein the second data packet uses a data format suitable for the remote communication;

the equipment connector receives the second data packet, analyzes the second data packet to obtain the diagnosis response data, and sends the diagnosis response data to the diagnosis equipment so that the diagnosis equipment analyzes and processes the diagnosis response data to obtain a diagnosis result; the diagnosis result can be output to a mobile client associated with the vehicle to be diagnosed;

The device connector is connected with the diagnosis device and the vehicle connector is connected with the vehicle to be diagnosed through K wires, and the K wires are wired connections established through a local cable;

the diagnosis instruction is a K line level signal;

analyzing the first data packet to obtain a diagnosis instruction, including:

analyzing the first data packet to obtain a K line level signal;

forming a diagnosis instruction by the first level signal and the second level signal according to time sequence;

the processing the K-line level signal to obtain a first level signal and a second level signal includes:

determining the part of the initial first level signal except the regular signal as a first level signal; the initial second level signal and the newly added second level signal are combined into a second level signal.

2. A vehicle remote diagnosis method, characterized in that the vehicle remote diagnosis method is applied to a device connector, the vehicle remote diagnosis method comprising:

encapsulating the diagnostic instructions into a first data packet;

the first data packet is sent to a vehicle connector in a remote communication mode, so that the vehicle connector analyzes the first data packet to obtain the diagnosis instruction, and then the diagnosis instruction is sent to a vehicle to be diagnosed, diagnosis response data generated by the vehicle to be diagnosed according to the diagnosis instruction is received, and the diagnosis response data is packaged into a second data packet; the diagnostic response data is a parameter related to vehicle diagnosis, comprising: speed at which the vehicle is currently operating, engine displacement, and/or transmission parameters;

receiving the second data packet transmitted by the vehicle connector by remote communication;

analyzing the second data packet to obtain the diagnosis response data;

sending the diagnosis response data to the diagnosis equipment so that the diagnosis equipment analyzes and processes the diagnosis response data to obtain a diagnosis result; the diagnosis result can be output to a mobile client associated with the vehicle to be diagnosed;

The diagnosis instruction is a K line level signal;

analyzing the first data packet to obtain a diagnosis instruction, including:

analyzing the first data packet to obtain a K line level signal;

3. The vehicle remote diagnosis method according to claim 2, characterized in that, before the reception of the diagnosis instruction generated by the diagnosis device based on the K-wire protocol, the vehicle remote diagnosis method further comprises:

acquiring vehicle information of a vehicle to be diagnosed;

And establishing K-wire connection with the diagnostic equipment according to the configuration information.

4. The vehicle remote diagnosis method according to claim 3, wherein the determining the corresponding K-wire configuration information according to the vehicle information includes:

determining vehicle type information in the vehicle information;

5. A vehicle remote diagnosis method, characterized in that the vehicle remote diagnosis method is applied to a vehicle connector, the vehicle remote diagnosis method comprising:

analyzing the first data packet to obtain a diagnosis instruction, wherein the diagnosis instruction is generated by a diagnosis device based on a K-wire protocol and is packaged into the first data packet after being sent to a device connector;

sending the diagnosis instruction to a vehicle to be diagnosed so that the vehicle to be diagnosed generates diagnosis response data according to the diagnosis instruction; the diagnostic response data is a parameter related to vehicle diagnosis, comprising: speed at which the vehicle is currently operating, engine displacement, and/or transmission parameters;

receiving the diagnosis response data transmitted by the vehicle to be diagnosed;

Encapsulating the diagnostic response data into a second data packet;

the second data packet is sent to the equipment connector through remote communication, so that the equipment connector analyzes the second data packet to obtain diagnosis response data, and the equipment connector sends the diagnosis response data to the diagnosis equipment, so that the diagnosis equipment analyzes and processes the diagnosis response data to obtain a diagnosis result; the diagnosis result can be output to a mobile client associated with the vehicle to be diagnosed;

the diagnosis instruction is a K line level signal;

the parsing the first data packet to obtain a diagnostic instruction includes:

analyzing the first data packet to obtain a K line level signal;

6. The vehicle remote diagnosis method according to claim 5, further comprising, before the first data packet transmitted by the receiving device connector by remote communication:

acquiring vehicle information of the vehicle to be diagnosed;

7. The vehicle remote diagnosis method according to claim 6, wherein the determining the corresponding K-wire configuration information according to the vehicle information includes:

determining vehicle type information and vehicle electronic control unit ECU information in the vehicle information;

The establishing the K line connection with the vehicle to be diagnosed according to the K line configuration information comprises the following steps:

8. A device connector, the device connector comprising:

a memory for storing an executable computer program;

a processor for executing the executable computer program to implement the method of any of claims 2-4.

9. A vehicle connector, the vehicle connector comprising:

a memory for storing an executable computer program;

a processor for executing the executable computer program to implement the method of any of claims 5-7.