CN113867324A - Vehicle diagnosis method, vehicle-mounted device, terminal, and storage medium - Google Patents
Vehicle diagnosis method, vehicle-mounted device, terminal, and storage medium Download PDFInfo
- Publication number
- CN113867324A CN113867324A CN202111254526.9A CN202111254526A CN113867324A CN 113867324 A CN113867324 A CN 113867324A CN 202111254526 A CN202111254526 A CN 202111254526A CN 113867324 A CN113867324 A CN 113867324A
- Authority
- CN
- China
- Prior art keywords
- diagnosis
- vehicle
- target
- ecu
- request
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G05—CONTROLLING; REGULATING
- G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
- G05B23/00—Testing or monitoring of control systems or parts thereof
- G05B23/02—Electric testing or monitoring
- G05B23/0205—Electric testing or monitoring by means of a monitoring system capable of detecting and responding to faults
- G05B23/0218—Electric testing or monitoring by means of a monitoring system capable of detecting and responding to faults characterised by the fault detection method dealing with either existing or incipient faults
- G05B23/0221—Preprocessing measurements, e.g. data collection rate adjustment; Standardization of measurements; Time series or signal analysis, e.g. frequency analysis or wavelets; Trustworthiness of measurements; Indexes therefor; Measurements using easily measured parameters to estimate parameters difficult to measure; Virtual sensor creation; De-noising; Sensor fusion; Unconventional preprocessing inherently present in specific fault detection methods like PCA-based methods
Abstract
The application is applicable to the technical field of automobile diagnosis, and provides a vehicle diagnosis method, a device, a terminal and a storage medium, wherein the method comprises the following steps: establishing a local network connection with a user terminal; acquiring a diagnosis request sent by the user terminal based on the local network connection, wherein the diagnosis request comprises a target ECU requesting diagnosis and a target diagnosis function; transmitting a diagnosis instruction corresponding to the target diagnosis function to a target ECU of the target vehicle based on the diagnosis request; and acquiring diagnosis result data sent by the target ECU based on the diagnosis instruction, and feeding back the diagnosis result data to the user terminal. The scheme can reduce data transmission delay and ensure data diagnosis communication quality.
Description
Technical Field
The application belongs to the technical field of automobile diagnosis, and particularly relates to a vehicle diagnosis method, a vehicle-mounted device, a terminal and a storage medium.
Background
With increasing intellectualization, networking and digitalization of automobiles, the automobile networking system equipped in the automobile has become a trend of automobile development, and the automobile networking system comprises four parts, namely a host, an on-board T-BOX (Telematics BOX), a mobile phone App and a background system. The main machine is mainly used for audio-video entertainment in a vehicle and vehicle information display, and the vehicle-mounted T-BOX is mainly used for communicating with a background system/mobile phone App to realize vehicle information display and control of the mobile phone App.
After a user sends a Control command through the mobile phone side APP, the background system sends a corresponding command to the vehicle-mounted T-BOX, after the vehicle obtains the Control command through the vehicle-mounted T-BOX, the vehicle sends a Control message to each ECU (Electronic Control Unit) system through the CAN bus, the vehicle is controlled, and finally an operation result is fed back to the mobile phone APP of the user, so that the user CAN be helped to remotely start the vehicle, open an air conditioner, adjust a seat to a proper position and the like through the function.
Since the T-BOX system has the authority of data interaction with each vehicle-mounted MCU system, when the vehicle is subjected to a diagnosis task, the vehicle data is acquired by using the vehicle network system.
However, data interaction between the T-BOX and the APP at the user side in the existing vehicle networking system needs to be realized through a background system, the T-BOX uploads vehicle related information to a background platform, content is checked and acquired from the background platform if the user side needs to acquire the vehicle related data, and the user side also needs to issue a diagnostic data acquisition request to the T-BOX through the background platform to execute when executing a certain diagnostic task. In this way, when a vehicle diagnosis task is executed, the client and the T-BOX system are required to maintain network connection with the background platform, and normal operation of diagnosis operation cannot be ensured when no network exists or network signals are not good, and data delay may occur when the background platform transfers vehicle data, so that real-time performance of vehicle diagnosis data transfer cannot be ensured.
Disclosure of Invention
The embodiment of the application provides a vehicle diagnosis method, a vehicle-mounted device, a terminal and a storage medium, and aims to solve the problems that a background platform and a vehicle-mounted T-BOX in a vehicle networking system are easily interfered by communication signals and data delay is easily caused when vehicle diagnosis is carried out in the prior art.
In a first aspect of an embodiment of the present application, a vehicle diagnosis method is applied to a vehicle-mounted terminal, where the vehicle-mounted terminal establishes a communication connection with a target vehicle, and the method includes:
establishing a local network connection with a user terminal;
acquiring a diagnosis request sent by the user terminal based on the local network connection, wherein the diagnosis request comprises a target ECU requesting diagnosis and a target diagnosis function;
transmitting a diagnosis instruction corresponding to the target diagnosis function to a target ECU of the target vehicle based on the diagnosis request;
and acquiring diagnosis result data sent by the target ECU based on the diagnosis instruction, and feeding back the diagnosis result data to the user terminal.
Optionally, the obtaining a diagnosis request sent by the user terminal based on the local network connection includes:
acquiring a web user side access request sent by the user terminal based on the local network connection;
responding to the web user side access request, and outputting a web user side access page to the user terminal, wherein the web user side access page comprises an ECU list of the target vehicle and different diagnosis function options supported by the ECU;
and acquiring the diagnosis request triggered by the user terminal after the user terminal selects the target ECU from the ECU list and selects the target diagnosis function from the diagnosis function options.
Optionally, the feeding back the diagnosis result data to the user terminal includes:
and filling the diagnosis result data to a target position of the web user side access page.
Optionally, the sending, based on the diagnosis request, a diagnosis instruction corresponding to the target diagnosis function to a target ECU of the target vehicle includes:
analyzing the diagnosis request to obtain the target ECU and the target diagnosis function corresponding to the diagnosis request;
determining a diagnosis protocol corresponding to the target ECU from an ECU diagnosis protocol table based on the target ECU;
establishing communication connection with the target ECU based on the diagnosis protocol, and generating the diagnosis instruction corresponding to the target diagnosis function;
and sending the diagnosis instruction to the target ECU.
Optionally, the acquiring of the diagnosis result data sent by the target ECU based on the diagnosis instruction includes:
and when a feedback message sent by the target ECU based on the diagnosis instruction is obtained, analyzing the feedback message based on a diagnosis protocol corresponding to the target ECU to obtain the diagnosis result data.
Optionally, the storing, in the vehicle-mounted terminal, a mapping relationship table between each ECU of the target vehicle and each corresponding diagnostic protocol, and when a feedback packet sent by the target ECU based on the diagnostic instruction is obtained, analyzing the feedback packet based on the diagnostic protocol corresponding to the target ECU to obtain the diagnostic result data includes:
when a feedback message sent by the target ECU based on the diagnosis instruction is obtained, a diagnosis protocol corresponding to the target ECU is searched based on the mapping relation table;
and analyzing the feedback message based on a diagnosis protocol corresponding to the target ECU to obtain the diagnosis result data.
A second aspect of an embodiment of the present application provides a vehicle diagnosis method, applied to a user terminal, including:
establishing local network connection with the vehicle-mounted terminal;
sending a web user side access request to the vehicle-mounted terminal based on the local network connection;
when a web user side access page returned by the vehicle-mounted terminal based on the web user side access request is received, a diagnosis request is generated according to a target ECU selected by a user from the web user side access page and a target diagnosis function; the web user side access page comprises an ECU list of the target vehicle and different diagnosis function options supported by the ECU;
sending the diagnosis request to the vehicle-mounted terminal;
and receiving the diagnosis result data returned by the vehicle-mounted terminal based on the diagnosis request.
A third aspect of the embodiments of the present application provides a vehicle-mounted terminal, where the vehicle-mounted terminal establishes a communication connection with a target vehicle, and the vehicle-mounted terminal further includes:
the communication establishing module is used for establishing local network connection with the user terminal;
an obtaining module, configured to obtain a diagnosis request sent by the user terminal based on the local network connection, where the diagnosis request includes a target ECU requesting diagnosis and a target diagnosis function;
a sending module, configured to send a diagnosis instruction corresponding to the target diagnosis function to a target ECU of the target vehicle based on the diagnosis request;
and the data feedback module is used for acquiring the diagnosis result data sent by the target ECU based on the diagnosis instruction and feeding back the diagnosis result data to the user terminal.
Optionally, the obtaining module is specifically configured to:
acquiring a web user side access request sent by the user terminal based on the local network connection;
responding to the web user side access request, and outputting a web user side access page to the user terminal, wherein the web user side access page comprises an ECU list of the target vehicle and different diagnosis function options supported by the ECU;
and acquiring the diagnosis request triggered by the user terminal after the user terminal selects the target ECU from the ECU list and selects the target diagnosis function from the diagnosis function options.
Optionally, the data feedback module is specifically configured to:
and filling the diagnosis result data to a target position of the web user side access page.
Optionally, the sending module is specifically configured to:
analyzing the diagnosis request to obtain the target ECU and the target diagnosis function corresponding to the diagnosis request;
determining a diagnosis protocol corresponding to the target ECU from an ECU diagnosis protocol table based on the target ECU;
establishing communication connection with the target ECU based on the diagnosis protocol, and generating the diagnosis instruction corresponding to the target diagnosis function;
and sending the diagnosis instruction to the target ECU.
Optionally, the data feedback module is specifically configured to:
and when a feedback message sent by the target ECU based on the diagnosis instruction is obtained, analyzing the feedback message based on a diagnosis protocol corresponding to the target ECU to obtain the diagnosis result data.
Optionally, the vehicle-mounted terminal stores a mapping table between each ECU of the target vehicle and each corresponding diagnostic protocol, wherein the data feedback module is more specifically configured to:
when a feedback message sent by the target ECU based on the diagnosis instruction is obtained, a diagnosis protocol corresponding to the target ECU is searched based on the mapping relation table;
and analyzing the feedback message based on a diagnosis protocol corresponding to the target ECU to obtain the diagnosis result data.
A fourth aspect of embodiments of the present application provides a terminal, including a memory, a processor, and a computer program stored in the memory and executable on the processor, where the processor implements the steps of the method according to the first and second aspects when executing the computer program.
A fifth aspect of embodiments of the present application provides a computer-readable storage medium, which stores a computer program that, when executed by a processor, implements the steps of the method according to the first and second aspects.
A sixth aspect of the present application provides a computer program product, which, when run on a terminal, causes the terminal to perform the steps of the method of the first and second aspects.
Therefore, according to the embodiment of the application, the communication connection is directly established between the vehicle-mounted terminal and the user terminal, so that the user terminal can directly send the diagnosis request to the vehicle-mounted terminal only by connecting the vehicle-mounted terminal to obtain the diagnosis data, the vehicle-mounted terminal sends the diagnosis instruction to the target ECU of the target vehicle based on the diagnosis request, the diagnosis result data is finally fed back to the user terminal through data interaction with the target ECU, data transfer is not needed through a remote background platform in the internet of vehicles system, data transmission delay is reduced, the communication connection and data transmission can be realized without a mobile network, and the data diagnosis communication quality is ensured.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the embodiments or the prior art descriptions will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings without creative efforts.
FIG. 1 is a flow chart of a vehicle diagnostic method provided by an embodiment of the present application;
FIG. 2 is a flow chart of another vehicle diagnostic method provided by an embodiment of the present application;
fig. 3 is a structural diagram of a vehicle-mounted terminal according to an embodiment of the present application;
fig. 4 is a structural diagram of a user terminal according to an embodiment of the present application;
fig. 5 is a structural diagram of a terminal 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 particular system structures, 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.
It will be understood that the terms "comprises" and/or "comprising," when used in this specification and the appended claims, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
It is also to be understood that the terminology used in the description of the present application herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. As used in the specification of the present application and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise.
It should be further understood that the term "and/or" as used in this specification and the appended claims refers to and includes any and all possible combinations of one or more of the associated listed items.
As used in this specification and the appended claims, the term "if" may be interpreted contextually as "when", "upon" or "in response to a determination" or "in response to a detection". Similarly, the phrase "if it is determined" or "if a [ described condition or event ] is detected" may be interpreted contextually to mean "upon determining" or "in response to determining" or "upon detecting [ described condition or event ]" or "in response to detecting [ described condition or event ]".
In particular implementations, the terminals described in embodiments of the present application include, but are not limited to, other portable devices such as mobile phones, laptop computers, or tablet computers having touch sensitive surfaces (e.g., touch screen displays and/or touch pads). It should also be understood that in some embodiments, the device is not a portable communication device, but is a desktop computer having a touch-sensitive surface (e.g., a touch screen display and/or touchpad).
In the discussion that follows, a terminal that includes a display and a touch-sensitive surface is described. However, it should be understood that the terminal may include one or more other physical user interface devices such as a physical keyboard, mouse, and/or joystick.
The terminal supports various applications, such as one or more of the following: a drawing application, a presentation application, a word processing application, a website creation application, a disc burning application, a spreadsheet application, a gaming application, a telephone application, a video conferencing application, an email application, an instant messaging application, an exercise support application, a photo management application, a digital camera application, a web browsing application, a digital music player application, and/or a digital video player application.
Various applications that may be executed on the terminal may use at least one common physical user interface device, such as a touch-sensitive surface. One or more functions of the touch-sensitive surface and corresponding information displayed on the terminal can be adjusted and/or changed between applications and/or within respective applications. In this way, a common physical architecture (e.g., touch-sensitive surface) of the terminal can support various applications with user interfaces that are intuitive and transparent to the user.
It should be understood that, the sequence numbers of the steps in this embodiment do not mean the execution sequence, and the execution sequence of each process should be determined by the function and the inherent logic of the process, and should not constitute any limitation to the implementation process of the embodiment of the present application.
In order to explain the technical solution described in the present application, the following description will be given by way of specific examples.
The embodiment of the application discloses a vehicle diagnosis method, which is applied to a vehicle-mounted terminal, wherein the vehicle-mounted terminal is in communication connection with a target vehicle.
In the application process, the vehicle-mounted terminal is assembled in a target vehicle and establishes communication connection with the target vehicle, wherein the communication connection is specifically serial communication connection or wireless communication connection. The vehicle-mounted terminal is connected to a bus in the target vehicle in a communication mode, and data communication between the vehicle-mounted terminal and an ECU system in the vehicle is achieved.
The in-vehicle terminal may be a vehicle-mounted terminal having both a local network communication function and a remote communication function, or a vehicle-mounted terminal having only a local network communication function, which is only an exemplary illustration herein and is not limited thereto.
Further, referring to fig. 1, fig. 1 is a flowchart of a vehicle diagnosis method provided in an embodiment of the present application. As shown in fig. 1, a vehicle diagnosis method, applied to a vehicle-mounted terminal, specifically a TBOX, includes the following steps:
102, acquiring a diagnosis request sent by a user terminal based on the local network connection, wherein the diagnosis request comprises a target ECU requesting diagnosis and a target diagnosis function;
and 104, acquiring diagnosis result data sent by the target ECU based on the diagnosis instruction, and feeding back the diagnosis result data to the user terminal.
The individual method steps described above are explained in detail below.
In step 101, a local network connection with the user terminal is established.
Specifically, the user terminal is, for example, a mobile phone, a tablet computer, a laptop computer, a desktop computer, or the like.
When the Local Network connection with the user terminal is established, the Local Network is specifically established through wire harness connection, or the Wireless Local Area Network is established at that time through Wireless Local Area Network (WLAN) direct connection or bluetooth direct connection and the like, so that the Local Network connection between the user terminal and the vehicle-mounted terminal is realized, and a data forwarding processing process of a remote third-party server is bypassed.
Specifically, when establishing the local network connection with the user terminal, the method may specifically include:
opening a wireless access point; acquiring a communication connection request which is sent by a user terminal and is accessed to a wireless access point, wherein the communication connection request comprises a network name and an access password of the wireless access point; and when the network name and the access password are determined to be correct based on the communication connection request, establishing communication connection with the user terminal through the wireless access point.
The wireless access point is specifically a WLAN access point or a bluetooth access point. When receiving the access request of the user terminal, if the access point information is verified to be correct, the user terminal is allowed to access, and the local network connection is established between the user terminal and the access point.
The network name of the wireless access point is specifically an SSID (Service Set Identifier). The SSID technology can divide a wireless local area network into a plurality of sub-networks which need different authentication, each sub-network needs independent authentication, and only users who pass the authentication can enter the corresponding sub-network, so that unauthorized users are prevented from entering the network.
When a user terminal needs to perform vehicle local diagnosis through a vehicle-mounted terminal, the SSID of a wireless access point in the vehicle-mounted terminal is searched through a wireless communication connection operation interface of a mobile phone or a computer, and then a password is input to send a request to the vehicle-mounted terminal for connection.
The wireless access point becomes a key node for enhancing data security and performing user access control. On one hand, the wireless access point is used as an intermediate forwarding node and can acquire all data interacted by the user; on the other hand, a wireless access point is an important basis for network access control as an access point for a user to access a network. The vehicle-mounted terminal supports the opening of the wireless access point, after the vehicle-mounted terminal is opened, other devices can be connected to the vehicle-mounted terminal through the wireless access point, an Ethernet subnet can be established, the wireless access point needs to be configured with the SSID and the password, the direct connection between the vehicle-mounted terminal and the user terminal is achieved, data transfer is not needed through a remote background platform in the vehicle networking system, data transmission delay is reduced, communication connection and data transmission can be achieved without a mobile network, and communication quality is guaranteed.
In step 102, a diagnostic request sent by the user terminal based on the local network connection is obtained.
The diagnosis request includes a target ECU that requests a diagnosis and a target diagnosis function.
After the local network connection is established between the user terminal and the vehicle-mounted terminal, a corresponding diagnosis request can be output to the vehicle-mounted terminal based on the vehicle diagnosis operation which needs to be executed currently, so that the vehicle-mounted terminal can acquire diagnosis data from the vehicle ECU system, and the user terminal can execute specific data diagnosis operation after acquiring the diagnosis data.
Wherein differences may exist between diagnostic data that different diagnostic functions require to be acquired. For example, the diagnostic data required to be acquired by the fault code diagnostic function is fault code data corresponding to an ECU system in the vehicle; the diagnostic data required to be acquired for vehicle operation performance diagnosis may be vehicle operation data acquired by different sensors in an ECU system in the vehicle, such as vehicle speed, electric quantity, level, voltage and other data in vehicle operation.
In step 103, a diagnosis instruction corresponding to the target diagnosis function is transmitted to the target ECU of the target vehicle based on the diagnosis request.
Since there may be a difference between diagnostic data that needs to be acquired by different diagnostic functions, it is necessary to send a diagnostic instruction corresponding to the target diagnostic function to the target ECU.
The corresponding relation or conversion relation between the target diagnosis function and the diagnosis instruction can be recorded through a pre-established relation library, and the diagnosis instruction is determined or generated through the relation library.
In step 104, the diagnosis result data sent by the target ECU based on the diagnosis instruction is acquired, and the diagnosis result data is fed back to the user terminal.
The acquisition of the diagnostic result data may be to analyze a feedback message sent by the target ECU based on the diagnostic instruction to obtain the diagnostic result data carried therein. Specifically, the analysis operation of the feedback message may be implemented according to the acquired diagnostic protocol parameter corresponding to the target ECU, and the diagnostic result data may be obtained by analyzing the protocol type, the message format, the received message identification code of the target ECU, and the like in the diagnostic protocol parameter corresponding to the target ECU.
For example, when the target diagnosis function is a fault code diagnosis function, the diagnosis result data sent by the target ECU based on the diagnosis instruction is specifically:
when the target ECU sends a feedback message based on the diagnosis instruction, analyzing the feedback message based on the diagnosis protocol parameters to obtain a fault code number; and matching to obtain fault code description information based on the fault code number, and taking the fault code number and the fault code description information as diagnosis result data.
Specifically, when the target ECU is an EMS system, the EMS system receives a diagnosis instruction sent by the vehicle-mounted terminal, and then analyzes that the diagnosis instruction needs to obtain a fault code, and then takes out a fault code number in the EMS system, fills the fault code number in a feedback message, and sends the fault code number to the vehicle-mounted terminal, where for example, the reply message is:
0x08fd000659900001ffff；
0x represents the 16-system;
08 indicates that there are several bytes in total except the received message identification code of the EMS system;
fd00 represents the message receiving identification code of EMS system;
06 indicates that the current byte is followed by several valid bytes;
59 is the mark value 0x62 obtained by adding the fixed value 0x40 to the system identification code 0x22 of the EMS system;
9000 is the number of the fault code;
01 represents the state of the fault code, the value of 01 represents the current, and the value of 00 represents the history;
ffff is meaningless for the default padding bytes.
After receiving the feedback message of the EMS system, the vehicle-mounted terminal analyzes the feedback message to analyze the number information of the fault code in the message, then finds out the description of the fault code through the number, for example, the 9000-numbered fault code describes that the voltage of the temperature sensor is too high, and finally, the vehicle-mounted terminal and the fault code are jointly used as diagnosis data to be sent to the user terminal.
According to the embodiment of the application, the communication connection is directly established between the vehicle-mounted terminal and the user terminal, so that the user terminal can directly send the diagnosis request to the vehicle-mounted terminal only by connecting the vehicle-mounted terminal to obtain the diagnosis data, the vehicle-mounted terminal sends the diagnosis instruction to the target ECU of the target vehicle based on the diagnosis request, and finally the diagnosis result data is fed back to the user terminal through data interaction with the target ECU.
Further, more specific embodiments will be specifically described with reference to which the above vehicle diagnosis method will be implemented.
As an optional implementation manner, the step 102 of obtaining the diagnosis request sent by the user terminal based on the local network connection includes:
acquiring a web user side access request sent by a user terminal based on local network connection;
responding to the web user side access request, and outputting a web user side access page to the user terminal, wherein the web user side access page comprises an ECU list of a target vehicle and diagnosis function options supported by different ECUs;
and acquiring a diagnosis request triggered by the user terminal after selecting a target ECU from the ECU list and selecting a target diagnosis function from the diagnosis function options.
In the process, the function of a web server is given to the vehicle-mounted terminal, and the web access page is provided for the user terminal.
When the corresponding function is realized, an operating system, such as LINUX, may be installed in the vehicle-mounted terminal, and web server software may be configured in the vehicle-mounted terminal based on the operating system. The web server may also be referred to as a website server, and may provide documents to a web client such as a browser, place data files, and also place website files for browsing and downloading. The web server software is Apache, Nginx, Lighttpd, Tomcat, etc., and each web page provided for the web client is also stored in the storage area under the configuration path of the vehicle-mounted terminal.
The web user side access page provided for the user terminal comprises an ECU list of the target vehicle and diagnosis function options supported by different ECUs.
After the local network connection is successfully established between the user terminal and the vehicle-mounted terminal, the user terminal can input the web address of the vehicle-mounted terminal to open a web access page of the vehicle-mounted terminal, such as 192.168.1.1\ index. html, wherein 192.168.1.1 is a default IP address of the vehicle-mounted terminal.
Specifically, a web page of the in-vehicle terminal, which is accessed through the browser, displays a list of ECUs supporting diagnosis of the current vehicle, and diagnosis services supported by each ECU, which are stored in a vehicle configuration table of the in-vehicle terminal, and outputs the contents to the user terminal when outputting the web client access page to the user terminal in response to the web client access request.
After the web user side access page is displayed in the user terminal, a user can select contents and options in the page through the user terminal, for example, the user can select an EMS system on the web page when the user wants to obtain current fault code information of the engine ECU, then select a fault code diagnosis function, determine submission after the selection is good, and after the submission of the diagnosis function is selected, a vehicle-mounted terminal background program can obtain the diagnosis function selected by the user, for example, a fault code reading function of the EMS system, namely, the vehicle-mounted terminal obtains an ECU fault diagnosis request triggered by the user terminal.
Correspondingly, as an optional implementation manner, the feeding back the diagnosis result data to the user terminal includes:
and filling the diagnosis result data to a target position of the web user side access page.
Taking the case that the diagnosis result data includes the fault code number and the fault code description content as an example, at this time, the diagnosis data is respectively filled in the preset position fields in the web page, the preset position fields are, for example, two information fields arranged in parallel left and right, and are respectively used for filling the fault code number and the fault code description content, and then the corresponding information is filled in the information fields in the web client access page and fed back to the user terminal.
Further, as an optional implementation manner, the step 103 of sending a diagnosis instruction corresponding to a target diagnosis function to a target ECU of a target vehicle based on a diagnosis request includes:
analyzing the diagnosis request to obtain a target ECU and a target diagnosis function corresponding to the diagnosis request;
determining a diagnosis protocol corresponding to the target ECU from an ECU diagnosis protocol table based on the target ECU;
establishing communication connection with a target ECU based on a diagnosis protocol, and generating a diagnosis instruction corresponding to a target diagnosis function;
the diagnostic instruction is sent to the target ECU.
The ECU diagnosis protocol table records diagnosis protocols corresponding to different vehicle-mounted ECUs and diagnosis protocols corresponding to the diagnosis protocols.
The diagnostic protocol specifies relevant protocol parameters such as: protocol type, message format, system identification code of the target ECU, transmission message identification code of the target ECU, reception message identification code of the target ECU, instruction code for reading fault code, and the like.
The message identification code is used for indicating that the message of the current diagnosis instruction is sent to the target ECU, and the message identification code is used for indicating that the feedback message is sent by the target ECU system based on the diagnosis instruction message containing the message identification code. The identification code of the sending message and the identification code of the receiving message are matched for use to realize the identification of the sending message and the feedback message.
Taking an Engine Management System (EMS) as an example, when the vehicle-mounted terminal obtains an ECU fault diagnosis request, it may search a diagnosis protocol corresponding to the EMS System, for example, the diagnosis protocol corresponding to the EMS is a Controller Area Network (CAN) communication protocol, that is, it may obtain various parameters corresponding to the diagnosis protocol, generate a message of a diagnosis instruction corresponding to a target diagnosis function based on the various parameters, and send the message to the EMS System, for example, generate a diagnosis data obtaining message corresponding to a fault code diagnosis function: 0x08fc0003190208 ffffffffffff;
0x represents the 16-system;
08 indicates that there are a few bytes in total in addition to the engine system sent message identification code;
fc00 represents the message identification code sent by the engine system;
03 indicates that the current byte is followed by several valid bytes;
190208 is a command code for indicating that a fault code needs to be read;
fffffffffff is meaningless for the default stuff byte.
After receiving a diagnosis request triggered by a user terminal, the vehicle-mounted terminal can generate a corresponding diagnosis instruction according to a diagnosis protocol corresponding to a target ECU and send the diagnosis instruction to the target ECU based on the target ECU and a target diagnosis function carried in the diagnosis request.
Correspondingly, in an alternative embodiment, the step 104 of acquiring the diagnosis result data sent by the target ECU based on the diagnosis instruction includes:
and when a feedback message sent by the target ECU based on the diagnosis instruction is obtained, analyzing the feedback message based on a diagnosis protocol corresponding to the target ECU to obtain diagnosis result data.
The method includes the steps that a mapping relation table between each ECU of a target vehicle and each corresponding diagnosis protocol is stored in a vehicle-mounted terminal, when a feedback message sent by the target ECU based on a diagnosis instruction is obtained, the feedback message is analyzed based on the diagnosis protocol corresponding to the target ECU, and diagnosis result data are obtained, and the method specifically includes the following steps:
when a feedback message sent by a target ECU based on a diagnosis instruction is obtained, a diagnosis protocol corresponding to the target ECU is searched based on a mapping relation table; and analyzing the feedback message based on a diagnosis protocol corresponding to the target ECU to obtain diagnosis result data.
Similarly, after receiving the feedback message of the target ECU, the mapping relation table needs to be searched to find the diagnosis protocol matched with the target ECU, and the feedback message is analyzed according to the protocol parameters specified by the diagnosis protocol to obtain the diagnosis result data, so that the accurate acquisition of the diagnosis data is realized.
In the embodiment of the application, the web server function is built in the vehicle-mounted terminal, after the local network connection is established between the vehicle-mounted terminal and the user terminal, the user terminal selects the corresponding function to submit the diagnosis request to the vehicle-mounted terminal in a web access mode to obtain the diagnosis data, the vehicle-mounted terminal generates the diagnosis data acquisition message based on the diagnosis request and sends the diagnosis data acquisition message to the target ECU, the target diagnosis data are finally fed back to the user terminal through data interaction with the target ECU, the user terminal does not need to install any software, data transfer does not need to be carried out through a remote background platform in the vehicle networking system, the local diagnosis operation is realized, data transmission delay is reduced, communication connection and data transmission can be realized without a mobile network, and the data diagnosis communication quality is ensured.
The embodiment of the application also provides another implementation mode of the vehicle diagnosis method.
The vehicle diagnosis method is applied to a user terminal.
The user terminal is, for example, an electronic device such as a mobile phone, a tablet computer, a laptop computer, and a desktop computer. Referring to fig. 2, fig. 2 is a flowchart of another vehicle diagnostic method provided in the embodiments of the present application. As shown in fig. 2, the vehicle diagnosis method includes the steps of:
When the Local Network connection with the vehicle-mounted terminal is established, the Local Area Network is specifically established through wire harness connection, or the Wireless Local Area Network is established at that time through Wireless Local Area Network (WLAN) direct connection or bluetooth direct connection and the like, so that the Local Network connection between the user terminal and the vehicle-mounted terminal is realized, and a data forwarding processing process of a remote third-party server is bypassed.
When the local network connection is realized by establishing the wireless local area network, the local network connection can be realized through a wireless access point opened by the vehicle-mounted terminal, and the wireless access point is specifically a WLAN access point or a Bluetooth access point. And sending an access request to the vehicle-mounted terminal, inputting correct access point verification information, and realizing the establishment of local network connection between the vehicle-mounted terminal and the vehicle-mounted terminal.
After the local network connection is established between the user terminal and the vehicle-mounted terminal, information interaction can be performed based on the local network connection.
Specifically, the user terminal may implement the triggering of the diagnosis request by accessing the page through the web user side.
And step 203, when a web client access page returned by the vehicle-mounted terminal based on the web client access request is received, generating a diagnosis request according to a target ECU selected by the user from the web client access page and a target diagnosis function.
The web client access page comprises an ECU list of the target vehicle and diagnosis function options supported by different ECUs.
In the process, the function of a web server is given to the vehicle-mounted terminal, and the vehicle-mounted terminal provides a web access page for the user terminal.
When the corresponding function is realized, an operating system, such as LINUX, may be installed in the vehicle-mounted terminal, and web server software may be configured in the vehicle-mounted terminal based on the operating system. The web server side software is for example Apache, Nginx, Lighttpd, Tomcat, etc.
The web user side access page provided for the user terminal comprises an ECU list of the target vehicle and diagnosis function options supported by different ECUs.
After the local network connection is successfully established between the user terminal and the vehicle-mounted terminal, the user terminal can input the web address of the vehicle-mounted terminal to open a web access page of the vehicle-mounted terminal, such as 192.168.1.1\ index. html, wherein 192.168.1.1 is a default IP address of the vehicle-mounted terminal.
Specifically, a web page of the in-vehicle terminal, in which a browser is accessed, may display a list of ECUs for which diagnosis is supported by the current vehicle, and diagnosis services supported by each ECU.
After the web user side access page is displayed in the user terminal, a user can select contents and options in the page through the user terminal, for example, the user can select an EMS system on the web page when the user wants to obtain current fault code information of the engine ECU, then select a fault code diagnosis function, determine submission after the selection is good, and after the submission of the diagnosis function is selected, a vehicle-mounted terminal background program can obtain the diagnosis function selected by the user, for example, a fault code reading function of the EMS system, namely, the vehicle-mounted terminal obtains an ECU fault diagnosis request triggered by the user terminal.
And step 204, sending the diagnosis request to the vehicle-mounted terminal.
When the diagnosis request is sent to the vehicle-mounted terminal, the sending of the diagnosis request can be realized through a sending button arranged in an access page of the web user side.
And step 205, receiving the diagnosis result data returned by the vehicle-mounted terminal based on the diagnosis request.
And receiving the diagnosis result data returned by the vehicle-mounted terminal based on the diagnosis request, wherein the diagnosis result data can be obtained by obtaining the web user side access page pushed by the vehicle-mounted terminal after the vehicle-mounted terminal fills the diagnosis result data to the target position of the web user side access page.
In the embodiment of the application, the communication connection is directly established between the vehicle-mounted terminal and the user terminal, so that the user terminal can directly send the diagnosis request to the vehicle-mounted terminal only by connecting the vehicle-mounted terminal to obtain the diagnosis data, the vehicle-mounted terminal sends the diagnosis instruction to the target ECU of the target vehicle based on the diagnosis request, and finally the diagnosis result data is fed back to the user terminal through data interaction with the target ECU, the data transfer is not required to be carried out through a remote background platform in the vehicle networking system, the data transmission delay is reduced, the communication connection and the data transmission can be realized without a mobile network, and the data diagnosis communication quality is ensured.
Referring to fig. 3, fig. 3 is a structural diagram of an in-vehicle terminal according to an embodiment of the present application, and for convenience of description, only a part related to the embodiment of the present application is shown.
Wherein, the vehicle-mounted terminal 300 establishes a communication connection with the target vehicle, and the vehicle-mounted terminal 300 further includes:
a communication establishing module 301, configured to establish a local network connection with a user terminal;
an obtaining module 302, configured to obtain a diagnosis request sent by the user terminal based on the local network connection, where the diagnosis request includes a target ECU requesting diagnosis and a target diagnosis function;
a sending module 303, configured to send a diagnosis instruction corresponding to the target diagnosis function to a target ECU of the target vehicle based on the diagnosis request;
and a data feedback module 304, configured to acquire diagnosis result data sent by the target ECU based on the diagnosis instruction, and feed back the diagnosis result data to the user terminal.
The obtaining module 302 is specifically configured to:
acquiring a web user side access request sent by the user terminal based on the local network connection;
responding to the web user side access request, and outputting a web user side access page to the user terminal, wherein the web user side access page comprises an ECU list of the target vehicle and different diagnosis function options supported by the ECU;
and acquiring the diagnosis request triggered by the user terminal after the user terminal selects the target ECU from the ECU list and selects the target diagnosis function from the diagnosis function options.
The data feedback module 304 is specifically configured to:
and filling the diagnosis result data to a target position of the web user side access page.
The sending module 303 is specifically configured to:
analyzing the diagnosis request to obtain the target ECU and the target diagnosis function corresponding to the diagnosis request;
determining a diagnosis protocol corresponding to the target ECU from an ECU diagnosis protocol table based on the target ECU;
establishing communication connection with the target ECU based on the diagnosis protocol, and generating the diagnosis instruction corresponding to the target diagnosis function;
and sending the diagnosis instruction to the target ECU.
The data feedback module 304 is specifically configured to:
and when a feedback message sent by the target ECU based on the diagnosis instruction is obtained, analyzing the feedback message based on a diagnosis protocol corresponding to the target ECU to obtain the diagnosis result data.
The vehicle-mounted terminal stores a mapping relation table between each ECU of the target vehicle and each corresponding diagnostic protocol, wherein the data feedback module 304 is more specifically configured to:
when a feedback message sent by the target ECU based on the diagnosis instruction is obtained, a diagnosis protocol corresponding to the target ECU is searched based on the mapping relation table;
and analyzing the feedback message based on a diagnosis protocol corresponding to the target ECU to obtain the diagnosis result data.
The vehicle-mounted terminal provided by the embodiment of the application can realize each process of the embodiment of the first vehicle diagnosis method, can achieve the same technical effect, and is not repeated here to avoid repetition.
Referring to fig. 4, fig. 4 is a structural diagram of a user terminal according to an embodiment of the present application, and for convenience of description, only a part related to the embodiment of the present application is shown.
The user terminal 400 includes:
a connection module 401, configured to establish a local network connection with a vehicle-mounted terminal;
a first request sending module 402, configured to send a web client access request to the vehicle-mounted terminal based on the local network connection;
a generating module 403, configured to generate, when a web client access page returned by the vehicle-mounted terminal based on the web client access request is received, a diagnosis request according to a target ECU and a target diagnosis function selected by a user from the web client access page; the web user side access page comprises an ECU list of the target vehicle and different diagnosis function options supported by the ECU;
a second request sending module 404, configured to send the diagnosis request to the vehicle-mounted terminal;
and a receiving module 405, configured to receive the diagnosis result data returned by the vehicle-mounted terminal based on the diagnosis request.
The user terminal provided in the embodiment of the present application can implement each process of the foregoing second vehicle diagnosis method, and can achieve the same technical effect, and is not described here again to avoid repetition.
Fig. 5 is a structural diagram of a terminal according to an embodiment of the present application. As shown in the figure, the terminal 5 of this embodiment includes: at least one processor 50 (only one shown in fig. 5), a memory 51, and a computer program 52 stored in the memory 51 and executable on the at least one processor 50, the steps of any of the various method embodiments described above being implemented when the computer program 52 is executed by the processor 50.
The terminal 5 may be a desktop computer, a notebook, a palm computer, a cloud server, or other computing devices. The terminal 5 may include, but is not limited to, a processor 50, a memory 51. It will be appreciated by those skilled in the art that fig. 5 is only an example of a terminal 5 and does not constitute a limitation of the terminal 5 and may include more or less components than those shown, or some components in combination, or different components, for example the terminal may also include input output devices, network access devices, buses, etc.
The Processor 50 may be a Central Processing Unit (CPU), other general purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other Programmable logic device, discrete Gate or transistor logic device, discrete hardware component, etc. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
The memory 51 may be an internal storage unit of the terminal 5, such as a hard disk or a memory of the terminal 5. The memory 51 may also be an external storage device of the terminal 5, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card) and the like provided on the terminal 5. Further, the memory 51 may also include both an internal storage unit and an external storage device of the terminal 5. The memory 51 is used for storing the computer program and other programs and data required by the terminal. The memory 51 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-mentioned division of the functional units and modules is illustrated, and in practical applications, the above-mentioned function distribution may be performed by different functional units and modules according to needs, that is, the internal structure of the apparatus is divided into different functional units or modules to perform all or part of the above-mentioned functions. Each functional unit and module in the embodiments may be integrated in one processing unit, or each unit may exist alone physically, or two or more units are integrated in one unit, and the integrated unit may be implemented in a form of hardware, or in a form of software functional unit. In addition, specific names of the functional units and modules are only for convenience of distinguishing from each other, and are not used for limiting the protection scope of the present application. The specific working processes of the units and modules in the system may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
In the above embodiments, the descriptions of the respective embodiments have respective emphasis, and reference may be made to the related descriptions of other embodiments for parts that are not described or illustrated in a certain embodiment.
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 implementation. 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/terminal and method may be implemented in other ways. For example, the above-described apparatus/terminal embodiments are merely illustrative, and for example, the division of the modules or units is only one logical division, and there may be other divisions when actually implemented, for example, a plurality of units or components may be combined or may be integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.
The integrated modules/units, if implemented in the form of software functional units and sold or used as separate products, may be stored in a computer readable storage medium. Based on such understanding, all or part of the flow in the method of the embodiments described above can be realized by a computer program, which can be stored in a computer-readable storage medium and can realize the steps of the embodiments of the methods described above when the computer program is executed by a processor. Wherein the computer program comprises computer program code, which may be in the form of source code, object code, an executable file or some intermediate form, etc. The computer-readable medium may include: any entity or device capable of carrying the computer program code, recording medium, usb disk, removable hard disk, magnetic disk, optical disk, computer Memory, Read-Only Memory (ROM), Random Access Memory (RAM), electrical carrier wave signals, telecommunications signals, software distribution medium, and the like. It should be noted that the computer readable medium may contain content that is subject to appropriate increase or decrease as required by legislation and patent practice in jurisdictions, for example, in some jurisdictions, computer readable media does not include electrical carrier signals and telecommunications signals as is required by legislation and patent practice.
The present application realizes all or part of the processes in the method of the above embodiments, and may also be implemented by a computer program product, when the computer program product runs on a terminal, the steps in the above method embodiments may be implemented when the terminal executes the computer program product.
The above-mentioned embodiments are only used for illustrating the technical solutions of the present application, and not for limiting the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; such modifications and substitutions do not substantially depart from the spirit and scope of the embodiments of the present application and are intended to be included within the scope of the present application.
Claims (10)
1. A vehicle diagnosis method is applied to a vehicle-mounted terminal, and the vehicle-mounted terminal establishes communication connection with a target vehicle, and the method comprises the following steps:
establishing a local network connection with a user terminal;
acquiring a diagnosis request sent by the user terminal based on the local network connection, wherein the diagnosis request comprises a target ECU requesting diagnosis and a target diagnosis function;
transmitting a diagnosis instruction corresponding to the target diagnosis function to a target ECU of the target vehicle based on the diagnosis request;
and acquiring diagnosis result data sent by the target ECU based on the diagnosis instruction, and feeding back the diagnosis result data to the user terminal.
2. The method according to claim 1, wherein the obtaining the diagnosis request sent by the user terminal based on the local network connection comprises:
acquiring a web user side access request sent by the user terminal based on the local network connection;
responding to the web user side access request, and outputting a web user side access page to the user terminal, wherein the web user side access page comprises an ECU list of the target vehicle and different diagnosis function options supported by the ECU;
and acquiring the diagnosis request triggered by the user terminal after the user terminal selects the target ECU from the ECU list and selects the target diagnosis function from the diagnosis function options.
3. The method of claim 2, wherein the feeding back the diagnosis result data to the user terminal comprises:
and filling the diagnosis result data to a target position of the web user side access page.
4. The method of claim 1, wherein said sending a diagnostic instruction corresponding to the target diagnostic function to a target ECU of the target vehicle based on the diagnostic request comprises:
analyzing the diagnosis request to obtain the target ECU and the target diagnosis function corresponding to the diagnosis request;
determining a diagnosis protocol corresponding to the target ECU from an ECU diagnosis protocol table based on the target ECU;
establishing communication connection with the target ECU based on the diagnosis protocol, and generating the diagnosis instruction corresponding to the target diagnosis function;
and sending the diagnosis instruction to the target ECU.
5. The method according to claim 4, wherein the acquiring of the diagnosis result data sent by the target ECU based on the diagnosis instruction includes:
and when a feedback message sent by the target ECU based on the diagnosis instruction is obtained, analyzing the feedback message based on a diagnosis protocol corresponding to the target ECU to obtain the diagnosis result data.
6. The method according to claim 5, wherein the vehicle-mounted terminal stores a mapping relation table between each ECU of a target vehicle and each corresponding diagnostic protocol, and when a feedback message sent by the target ECU based on the diagnostic instruction is obtained, the feedback message is analyzed based on the diagnostic protocol corresponding to the target ECU to obtain the diagnostic result data, including:
when a feedback message sent by the target ECU based on the diagnosis instruction is obtained, a diagnosis protocol corresponding to the target ECU is searched based on the mapping relation table;
and analyzing the feedback message based on a diagnosis protocol corresponding to the target ECU to obtain the diagnosis result data.
7. A vehicle diagnosis method is applied to a user terminal and is characterized by comprising the following steps:
establishing local network connection with the vehicle-mounted terminal;
sending a web user side access request to the vehicle-mounted terminal based on the local network connection;
when a web user side access page returned by the vehicle-mounted terminal based on the web user side access request is received, a diagnosis request is generated according to a target ECU selected by a user from the web user side access page and a target diagnosis function; the web user side access page comprises an ECU list of the target vehicle and different diagnosis function options supported by the ECU;
sending the diagnosis request to the vehicle-mounted terminal;
and receiving the diagnosis result data returned by the vehicle-mounted terminal based on the diagnosis request.
8. A vehicle-mounted terminal, characterized in that the vehicle-mounted terminal establishes a communication connection with a target vehicle, the vehicle-mounted terminal further comprising:
the communication establishing module is used for establishing local network connection with the user terminal;
an obtaining module, configured to obtain a diagnosis request sent by the user terminal based on the local network connection, where the diagnosis request includes a target ECU requesting diagnosis and a target diagnosis function;
a sending module, configured to send a diagnosis instruction corresponding to the target diagnosis function to a target ECU of the target vehicle based on the diagnosis request;
and the data feedback module is used for acquiring the diagnosis result data sent by the target ECU based on the diagnosis instruction and feeding back the diagnosis result data to the user terminal.
9. A terminal comprising a memory, a processor and a computer program stored in the memory and executable on the processor, characterized in that the processor implements the steps of the method according to any of claims 1 to 7 when executing the computer program.
10. A computer-readable storage medium, in which a computer program is stored which, when being executed by a processor, carries out the steps of the method according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111254526.9A CN113867324A (en) | 2021-10-27 | 2021-10-27 | Vehicle diagnosis method, vehicle-mounted device, terminal, and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111254526.9A CN113867324A (en) | 2021-10-27 | 2021-10-27 | Vehicle diagnosis method, vehicle-mounted device, terminal, and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113867324A true CN113867324A (en) | 2021-12-31 |
Family
ID=78997892
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111254526.9A Pending CN113867324A (en) | 2021-10-27 | 2021-10-27 | Vehicle diagnosis method, vehicle-mounted device, terminal, and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113867324A (en) |
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114996169A (en) * | 2022-08-04 | 2022-09-02 | 苏州清研精准汽车科技有限公司 | Device diagnosis method, device, electronic device, and storage medium |
| CN115118642A (en) * | 2022-06-09 | 2022-09-27 | 广东省智能网联汽车创新中心有限公司 | Vehicle-mounted bus network diagnosis method and system |
| CN115442767A (en) * | 2022-11-08 | 2022-12-06 | 上海银基信息安全技术股份有限公司 | Vehicle control event correlation method, device, system and medium |
| CN116149304A (en) * | 2023-04-21 | 2023-05-23 | 中国第一汽车股份有限公司 | Vehicle diagnosis system, method, equipment and storage medium |
| CN116224976A (en) * | 2023-05-08 | 2023-06-06 | 北京集度科技有限公司 | Test method and device |
| WO2023174217A1 (en) * | 2022-03-18 | 2023-09-21 | 北京罗克维尔斯科技有限公司 | Vehicle ethernet diagnosis method and apparatus, and device and medium |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108227675A (en) * | 2017-12-27 | 2018-06-29 | 深圳市元征软件开发有限公司 | Vehicular diagnostic method, device, terminal and computer readable storage medium |
| CN110501995A (en) * | 2019-08-28 | 2019-11-26 | 肇庆小鹏汽车有限公司 | A kind of vehicle diagnosing system and method |
| CN111103868A (en) * | 2019-12-27 | 2020-05-05 | 深圳市元征科技股份有限公司 | Vehicle fault diagnosis method and device and related equipment |
| CN113038421A (en) * | 2021-03-25 | 2021-06-25 | 深圳市元征科技股份有限公司 | Automobile diagnosis method, automobile diagnosis device and automobile gateway |
-
2021
- 2021-10-27 CN CN202111254526.9A patent/CN113867324A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108227675A (en) * | 2017-12-27 | 2018-06-29 | 深圳市元征软件开发有限公司 | Vehicular diagnostic method, device, terminal and computer readable storage medium |
| CN110501995A (en) * | 2019-08-28 | 2019-11-26 | 肇庆小鹏汽车有限公司 | A kind of vehicle diagnosing system and method |
| CN111103868A (en) * | 2019-12-27 | 2020-05-05 | 深圳市元征科技股份有限公司 | Vehicle fault diagnosis method and device and related equipment |
| CN113038421A (en) * | 2021-03-25 | 2021-06-25 | 深圳市元征科技股份有限公司 | Automobile diagnosis method, automobile diagnosis device and automobile gateway |
Cited By (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2023174217A1 (en) * | 2022-03-18 | 2023-09-21 | 北京罗克维尔斯科技有限公司 | Vehicle ethernet diagnosis method and apparatus, and device and medium |
| CN115118642A (en) * | 2022-06-09 | 2022-09-27 | 广东省智能网联汽车创新中心有限公司 | Vehicle-mounted bus network diagnosis method and system |
| CN114996169A (en) * | 2022-08-04 | 2022-09-02 | 苏州清研精准汽车科技有限公司 | Device diagnosis method, device, electronic device, and storage medium |
| CN114996169B (en) * | 2022-08-04 | 2022-10-28 | 苏州清研精准汽车科技有限公司 | Device diagnosis method, device, electronic device, and storage medium |
| CN115442767A (en) * | 2022-11-08 | 2022-12-06 | 上海银基信息安全技术股份有限公司 | Vehicle control event correlation method, device, system and medium |
| CN116149304A (en) * | 2023-04-21 | 2023-05-23 | 中国第一汽车股份有限公司 | Vehicle diagnosis system, method, equipment and storage medium |
| CN116224976A (en) * | 2023-05-08 | 2023-06-06 | 北京集度科技有限公司 | Test method and device |
| CN116224976B (en) * | 2023-05-08 | 2023-08-25 | 北京集度科技有限公司 | Test method and device |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN113867324A (en) | Vehicle diagnosis method, vehicle-mounted device, terminal, and storage medium | |
| JP5747981B2 (en) | System and method for remote maintenance of multiple clients in an electronic network using virtual machines | |
| CN112653618B (en) | Gateway registration method and device of micro-service application API (application program interface) endpoint | |
| US8661502B2 (en) | Determining a sensitivity label of document information in real time | |
| CN113872967B (en) | Vehicle information transmission method and device, electronic equipment and storage medium | |
| JP2015505387A (en) | Dynamic service integration system and method | |
| CN110888838A (en) | Object storage based request processing method, device, equipment and storage medium | |
| CN107610723B (en) | Accessing infotainment systems using unpaired devices | |
| CN115943376A (en) | Authenticating interface element interactions | |
| US11882154B2 (en) | Template representation of security resources | |
| US20240103928A1 (en) | Information processing method and apparatus for animation resource, device, medium and product | |
| CN112612977A (en) | Page display method, system, device, equipment and storage medium | |
| CN112818371A (en) | Resource access control method, system, device, equipment and medium | |
| CN114637703B (en) | Data access device, method, readable medium and electronic equipment | |
| CN104836777A (en) | Identity verification method and system | |
| CN114422436B (en) | Gateway, gateway control method, gateway control device, electronic equipment and storage medium | |
| CN114328130B (en) | Server monitoring method, system, equipment and computer readable storage medium | |
| CN114185804A (en) | Interface testing method and device and terminal equipment | |
| CN112688793B (en) | Data packet obtaining method and device and electronic equipment | |
| CN114006757A (en) | GIS service access control method, device, framework, medium and equipment | |
| US20200162636A1 (en) | Information processing system, information processing method, and information processing apparatus | |
| CN111125759A (en) | Database login account shielding method and device and electronic equipment | |
| CN110851185A (en) | Automatic configuration method and device for equipment, electronic equipment and storage medium | |
| CN113568726B (en) | Multi-service system processing method, operation platform, electronic equipment and storage medium | |
| TWI767113B (en) | System for using certificate stored in carrier to conduct online transactions and method thereof |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |