Vehicle Wi-Fi diagnostic method, device and system

Abstract

The present application provides a vehicle WIFI diagnostic method, device, and system. The vehicle is connected to the local area network where the diagnostic client is located through the vehicle's own WIFI module, enabling users to diagnose the vehicle remotely. The diagnostic client connects to multiple vehicles through multiple TCP ports and performs simultaneous fault diagnosis. The TLS protocol and USD 29 authentication service are used to protect the data in the diagnostic session, and the USD 29 service is used to manage the diagnostic client. The vehicle can grant different UDS service permissions to different diagnostic sources. Through this solution, the cost of maintaining wired interfaces is saved, the workspace is increased, work efficiency is improved, and information security risks are reduced.

Description

Technical Field

[0001] The present application relates to the field of automotive intelligent technology, and in particular to a vehicle WIFI diagnostic method, device and system. Background Art

[0002] In recent years, automotive technology has rapidly advanced, with vehicles becoming increasingly intelligent and incorporating a growing number of electronic controllers. This has resulted in improvements in vehicle performance and comfort, but also in increased complexity. This has led to a variety of faults, necessitating a preliminary diagnosis. However, these fault diagnosis procedures are difficult for the average user, who lacks relevant knowledge and is unable to determine the specific problem. To address this, vehicle diagnostics have gradually become increasingly common.

[0003] In the prior art, the existing automobile diagnostic method is to connect the diagnostic client to the vehicle through a diagnostic box with a wiring harness, obtain vehicle information from the vehicle's Electronic Control Unit (ECU), determine the vehicle's technical status, and achieve the purpose of vehicle diagnosis.

[0004] However, the above solution has the problem that users can only perform diagnosis on a diagnostic vehicle at a specific location, which results in low diagnostic efficiency, limited space, and is time-consuming and labor-intensive. Summary of the Invention

[0005] The present application provides a vehicle Wi-Fi diagnostic method, device, and system to solve the problems of long working hours, high maintenance costs, low efficiency ceiling, and high information security risks.

[0006] In a first aspect, the present application provides a vehicle Wi-Fi diagnostic method, which is applied to a diagnostic client in a diagnostic device, and the method includes:

[0007] In response to a first operation by a user, a diagnosis trigger signal is sent to a vehicle to be diagnosed, where the vehicle to be diagnosed and the diagnostic device are within the coverage range of the same WIFI;

[0008] Obtaining a vehicle list of vehicles to be diagnosed within the coverage of the WIFI, wherein the vehicle list includes information of at least one vehicle to be diagnosed;

[0009] In response to a second operation of the user on the vehicle list, selecting a target vehicle from the vehicle list, and initiating a handshake with a TLS port of the target vehicle via a WIFI network;

[0010] After successfully handshaking with the TLS port of the target vehicle, initiating a DoIP routing activation request to the target vehicle, wherein the DoIP routing activation request is used to establish a DoIP diagnostic session with the target vehicle;

[0011] After establishing a DoIP diagnostic session with the target vehicle, obtaining authorization to provide UDS services to the target vehicle;

[0012] Perform WIFI diagnosis on the target vehicle based on the UDS service and obtain a diagnosis message response.

[0013] In combination with the first aspect, in some embodiments, initiating a handshake with the TLS port of the target vehicle through the WIFI network includes:

[0014] Authenticate the target vehicle using a CA certificate chain, and query an OCSP server to see if the CA certificate of the target vehicle has been revoked;

[0015] If the CA certificate of the target vehicle is not revoked and the certificate authentication is passed, the handshake with the TLS port of the target vehicle is successful.

[0016] In conjunction with the first aspect, in some embodiments, after establishing a DoIP diagnostic session with the target vehicle, obtaining authorization to provide a UDS service to the target vehicle includes:

[0017] After establishing a DoIP diagnostic session with the target vehicle, initiating a UDS 29 identity authentication request to the target vehicle;

[0018] Binding the CA certificate of the diagnostic client, the public keys of the encryption algorithms of the network layer and the transport layer, and the revocation status of the CA certificate of the diagnostic client to the target vehicle through OCSP;

[0019] receiving an authentication result of the diagnostic client returned by the target vehicle;

[0020] When the authentication result indicates that the diagnosis client is authenticated, authorization to provide the UDS service to the target vehicle is obtained.

[0021] In conjunction with the first aspect, in some embodiments, obtaining a vehicle list of vehicles to be diagnosed within the coverage of the WIFI includes:

[0022] receiving vehicle information declared by at least one vehicle to be diagnosed within the range of the WIFI local area network;

[0023] The vehicle information of the at least one vehicle to be diagnosed is parsed to obtain the vehicle list.

[0024] In combination with the first aspect, in some embodiments, performing WIFI diagnosis on the target vehicle based on the UDS service and obtaining a diagnostic message response includes:

[0025] In response to a third operation by the user, generating a diagnostic message for the target vehicle, wherein the diagnostic message includes content of diagnosing the target vehicle;

[0026] Based on the UDS service, the diagnostic message is sent to the target vehicle;

[0027] The diagnostic message response of the target vehicle is received based on a UDS service.

[0028] In a second aspect, the present application provides a vehicle Wi-Fi diagnostic method, which is applied to a vehicle to be diagnosed, and the method includes:

[0029] Receiving a diagnostic trigger signal sent by the diagnostic client, wherein the diagnostic client is set in a diagnostic device, and the diagnostic device and the vehicle to be diagnosed are within the same Wi-Fi coverage range;

[0030] Switch to the WIFI diagnostic mode according to the diagnostic trigger signal, and access the WIFI according to the pre-configured SSID;

[0031] After successfully handshaking with the diagnostic client through the TLS port, receiving a DoIP routing activation request sent by the diagnostic client;

[0032] Establishing a DoIP diagnostic session with the diagnostic client according to the DoIP routing activation request;

[0033] After establishing a DoIP diagnostic session with the diagnostic client, sending a UDS service authorization to the diagnostic client;

[0034] In response to the WIFI diagnosis performed by the diagnostic client based on the UDS service, obtaining a diagnostic message response;

[0035] The diagnostic message response is sent to the diagnostic client.

[0036] In conjunction with the second aspect, in some embodiments, before successfully handshaking with the diagnostic client through the TLS port, the method further includes:

[0037] Initialize the TLS service and declare the vehicle information of the vehicle to be diagnosed in the WIFI local area network.

[0038] In conjunction with the second aspect, in some embodiments, establishing a DoIP diagnostic session with the diagnostic client according to the DoIP routing activation request includes:

[0039] The routing is activated according to the DoIP routing activation request, and the WIFI link of the vehicle to be diagnosed is controlled and maintained, thereby establishing a DoIP diagnostic session with the diagnostic client.

[0040] In conjunction with the second aspect, in some embodiments, the step of authorizing the diagnostic client to provide a UDS service includes:

[0041] Receiving a UDS 29 identity authentication request sent by the diagnostic client;

[0042] Receive the CA certificate, the public key of the encryption algorithm of the network layer and the transport layer, and the revocation status of the CA certificate sent by the diagnostic client according to the UDS 29 identity authentication request;

[0043] Authenticating the CA certificate of the diagnostic client using a CA certificate chain;

[0044] After the CA certificate of the diagnosis client is authenticated, the diagnosis client is authorized to provide the UDS service.

[0045] In conjunction with the second aspect, in some embodiments, obtaining a diagnostic message response in response to the WIFI diagnosis performed by the diagnostic client based on the UDS includes:

[0046] receiving a diagnostic message sent by the diagnostic client based on the UDS service, wherein the diagnostic message includes content of diagnosing the vehicle;

[0047] Performing WIFI diagnosis on the vehicle according to the diagnostic message to obtain the diagnostic message response;

[0048] The diagnostic message response is sent to the diagnostic client.

[0049] In a third aspect, the present application provides a vehicle Wi-Fi diagnostic device, which is applied to a diagnostic client in a diagnostic device, and the device includes:

[0050] a first sending module, configured to send a diagnosis trigger signal to the vehicle to be diagnosed in response to a first operation of the user;

[0051] A first acquisition module is used to obtain a vehicle list of vehicles to be diagnosed within the coverage area of ​​the WIFI;

[0052] a processing module, configured to select a target vehicle from the vehicle list in response to a second operation of the user on the vehicle list;

[0053] A communication processing module, configured to initiate a handshake with the TLS port of the target vehicle via a WIFI network;

[0054] A second sending module is used to initiate a DoIP routing activation request to the target vehicle after successfully handshaking with the TLS port of the target vehicle;

[0055] A second acquisition module is used to obtain authorization for performing UDS services on the target vehicle after establishing a DoIP diagnostic session with the target vehicle;

[0056] The diagnostic module is used to perform Wi-Fi diagnosis on the target vehicle based on the UDS service and obtain a diagnostic message response.

[0057] In a fourth aspect, the present application provides a vehicle Wi-Fi diagnostic device, which is applied to a vehicle to be diagnosed, and the device includes:

[0058] A first receiving module: configured to receive a diagnosis trigger signal sent by the diagnosis client;

[0059] WIFI module: switches to WIFI diagnostic mode according to the diagnostic trigger signal, and accesses the WIFI according to the pre-configured SSID;

[0060] A second receiving module is configured to receive a DoIP routing activation request sent by the diagnostic client after a successful handshake with the diagnostic client via the TLS port;

[0061] Communication processing module: used for establishing a DoIP diagnostic session with the diagnostic client according to the DoIP routing activation request;

[0062] A first sending module is used to send a UDS service authorization to the diagnostic client after establishing a DoIP diagnostic session with the diagnostic client;

[0063] Diagnostic module: used for obtaining a diagnostic message response in response to the Wi-Fi diagnosis performed by the diagnostic client based on the UDS service;

[0064] The second sending module is configured to send the diagnostic message response to the diagnostic client.

[0065] In a fifth aspect, the present application provides a diagnostic device, comprising:

[0066] Processor, memory, wireless access port, TCP port

[0067] The memory stores computer instructions;

[0068] The processor executes the computer instructions stored in the memory, so that the diagnostic device performs the vehicle WIFI diagnostic method according to the first aspect;

[0069] In a sixth aspect, the present application provides a vehicle, comprising:

[0070] Memory, processor, WIFI module, communication interface, diagnostic controller, ECU;

[0071] The memory stores computer instructions;

[0072] The processor executes the computer instructions stored in the memory, so that the vehicle device to be diagnosed performs the vehicle WIFI diagnosis method according to the second aspect;

[0073] In a seventh aspect, the present application provides a storage medium storing a computer program;

[0074] When the computer program is executed, the vehicle WIFI diagnostic method described in the first aspect and the second aspect is implemented.

[0075] In an eighth aspect, the present application provides a vehicle Wi-Fi diagnostic system, comprising:

[0076] A diagnostic device and at least one vehicle to be diagnosed, wherein the diagnostic device and the vehicle to be diagnosed are connected via a WIFI network mode;

[0077] The diagnostic device is used to perform the vehicle WIFI diagnostic method described in the first aspect;

[0078] The vehicle to be diagnosed is used to perform the vehicle WIFI diagnostic method described in the second aspect;

[0079] The vehicle Wi-Fi diagnostic method, device, and system provided in the embodiments of this application differ from existing technologies in that, when a vehicle malfunctions or requires regular diagnostic upgrades, this solution places the diagnostic vehicle and diagnostic equipment within the same Wi-Fi coverage area, eliminating the need for an intermediate diagnostic box and the vehicle's OBD interface. Instead, the diagnostic client connects to the vehicle to be diagnosed via a Wi-Fi link and initiates DOIP diagnosis over the Wi-Fi link, enabling remote vehicle diagnosis. This effectively avoids maintenance costs, space constraints, low efficiency, and long work hours. BRIEF DESCRIPTION OF THE DRAWINGS

[0080] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.

[0081] Figure 1 This is an application scenario diagram of the vehicle Wi-Fi diagnostic method provided in an embodiment of the present application;

[0082] Figure 2 A flowchart of a first embodiment of a vehicle Wi-Fi diagnostic method according to an embodiment of the present application;

[0083] Figure 3A flow chart of a second embodiment of the vehicle Wi-Fi diagnostic method provided in an embodiment of the present application;

[0084] Figure 4 This is a flowchart of Example 3 of the vehicle WIFI diagnostic method proposed in the embodiment of the present application;

[0085] Figure 5 This is a flow chart of Example 4 of the vehicle WIFI diagnostic method proposed in the embodiments of the present application;

[0086] Figure 6 This is a flowchart illustrating the vehicle Wi-Fi diagnostic method proposed in an embodiment of the present application;

[0087] Figure 7 This is a flowchart of a specific example of the vehicle WIFI diagnostic method proposed in an embodiment of the present application;

[0088] Figure 8 This is a diagnostic timing diagram of the vehicle WIFI diagnostic method proposed in an embodiment of the present application;

[0089] Figure 9 This is a schematic diagram of the structure of a first embodiment of a vehicle Wi-Fi diagnostic device provided in an embodiment of the present application;

[0090] Figure 10 This is a schematic diagram of the structure of a second embodiment of a vehicle Wi-Fi diagnostic device provided in an embodiment of the present application;

[0091] Figure 11 This is a schematic diagram of the structure of a third embodiment of a vehicle Wi-Fi diagnostic device provided in an embodiment of the present application;

[0092] Figure 12 This is a schematic diagram of the structure of a fourth embodiment of a vehicle Wi-Fi diagnostic device provided in an embodiment of the present application;

[0093] Figure 13 A schematic diagram of the structure of a fifth embodiment of a vehicle Wi-Fi diagnostic device provided in an embodiment of the present application;

[0094] Figure 14 This is a schematic diagram of the structure of a sixth embodiment of a vehicle Wi-Fi diagnostic device provided in an embodiment of the present application;

[0095] Figure 15 This is a structural diagram of a seventh embodiment of a vehicle Wi-Fi diagnostic device provided in an embodiment of the present application;

[0096] Figure 16 This is a schematic diagram of the structure of an eighth embodiment of a vehicle Wi-Fi diagnostic device provided in an embodiment of the present application;

[0097] Figure 17A schematic diagram of the structure of the diagnostic device provided in an embodiment of the present application;

[0098] Figure 18 A schematic diagram of the structure of a vehicle provided in an embodiment of the present application;

[0099] Figure 19 A schematic diagram of the architecture of a vehicle Wi-Fi diagnostic system provided in an embodiment of the present application.

[0100] The above drawings illustrate specific embodiments of the present application, which will be described in more detail below. These drawings and the textual description are not intended to limit the scope of the present application in any way, but rather to illustrate the concepts of the present application to those skilled in the art by reference to specific embodiments. DETAILED DESCRIPTION

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

[0102] First, let’s explain the terms involved in this application:

[0103] A Service Set Identifier (SSID) is a device that divides a wireless LAN into several subnets, each requiring different authentication levels. Each subnet requires independent authentication, allowing only authenticated users to access the corresponding subnet, preventing unauthorized access. The SSID is the name of a LAN, and only computers with the same SSID can communicate.

[0104] The Pre-Shard Key (PSK) is a Unicode string used to authenticate L2TP / IPSec connections.

[0105] The Diagnostic Over Internet Protocol (DoIP) is based on the diagnosis of in-vehicle Ethernet, and the diagnostic data it transmits is also based on the Unified Diagnostic Services (UDS). That is, DoIP is a transmission protocol for transmitting UDS data on the Ethernet network.

[0106] Online Certificate Status Protocol (OCSP) is one of two common modes for maintaining the security of servers and other network resources.

[0107] The Transmission Control Protocol (TCP) enables communication between two computers. During communication, the client must first connect to the server. The server cannot actively connect to the client, and the server program needs to be started in advance and wait for the client to connect.

[0108] Public Key Infrastructure (PKI) is a technology and specification that uses public key cryptography to provide a secure foundation for e-commerce. PKI is a standard-compliant key management platform built on encryption technology and centered around certificate services. It supports centralized and automated key management and distribution, providing cryptographic services like encryption and digital signatures, as well as the required key and certificate management systems, for all network applications.

[0109] As people's living standards continue to improve, the demand for cars is also increasing. The development of automobiles has advanced by leaps and bounds, resulting in increasingly intelligent vehicles, but also increasing complexity and a corresponding increase in faults. Users use a physical wiring harness to connect the diagnostic vehicle to the diagnostic client through a diagnostic box to diagnose faults. However, the physical wiring harness can only connect to the diagnostic box through the vehicle's on-board diagnostics (OBD) port, requiring the user to get in the vehicle, find the OBD interface, and connect the diagnostic device to establish a diagnostic communication connection. This connection method is cumbersome to operate, and the OBD connector is also prone to damage. Furthermore, flashing the vehicle's electronic control unit (ECU) software takes a long time, occupies the diagnostic equipment, and further limits user work efficiency. If the diagnostic box's extended wireless communication network (Wi-Fi) hotspot module is used to enable remote control of the diagnostic box from the diagnostic client, replacing the existing wired connection between the diagnostic client and the diagnostic box, remote diagnosis can be achieved for the user. However, there are still problems such as the OBD interface being easily damaged and the inefficiency of one-to-one diagnosis. In addition, the WiFi module antenna of the diagnostic box has a small coverage area and can only achieve short-range local wireless communication. Moreover, during the diagnosis process, the WiFi link between the diagnostic box and the diagnostic client can be easily cracked and captured, and information may be stolen and tampered with, thus posing a high information security risk.

[0110] In response to the above problems, the present application provides a vehicle WIFI diagnostic method that realizes remote wireless diagnosis and one-to-many diagnosis. Specifically, at present, when a vehicle breaks down or undergoes regular maintenance, the user needs to connect the diagnostic box to the vehicle through the OBD interface to realize diagnosis. During the research process, the inventor found that when there are too many vehicles to be diagnosed and there is a lack of user personnel, the user's work efficiency is seriously limited. If the diagnostic box is remotely controlled by the diagnostic client through the WIFI hotspot module extended by the diagnostic box, the user can realize remote diagnosis, but the user can still only diagnose the vehicle one-to-one through the OBD interface, and the OBD interface is easily damaged and the maintenance cost is high. The WIFI module antenna coverage of the diagnostic box is small and can only realize short-range local wireless communication. Taking these problems into consideration, it is studied whether the vehicle and the diagnostic equipment can be connected to the same local area network, and the functions of the diagnostic box can be migrated to the diagnostic equipment for implementation. Based on this, the technical solution in the present application is proposed.

[0111] Figure 1 This is an application scenario diagram of the vehicle WIFI diagnostic method provided in the embodiment of the present application. The vehicle diagnostic system is a computer information system that includes software and hardware, which can diagnose faulty vehicles. Figure 1 As shown, the vehicle Wi-Fi diagnostic method provided in this application can be applied to a vehicle diagnostic system, which includes at least: diagnostic equipment and at least one vehicle to be diagnosed. The diagnostic equipment can be a computer or other device with a test port. The vehicle to be diagnosed can be of any type, without limitation in this solution.

[0112] This application does not limit the specific form of each device.

[0113] The following specific embodiments describe in detail the technical solution of the present application and how the technical solution of the present application solves the above-mentioned technical problems. The following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments. The embodiments of the present application will be described below in conjunction with the accompanying drawings.

[0114] Figure 2 This is a flow chart of the first embodiment of the vehicle WIFI diagnostic method provided by this application, as shown in FIG. Figure 2 As shown, the vehicle WIFI diagnostic method is applied to the diagnostic client in the diagnostic device, specifically including the following steps:

[0115] S101: Sending a diagnosis trigger signal to the vehicle to be diagnosed.

[0116] In this step, the vehicle to be diagnosed and the diagnostic device are within the coverage of the same WIFI. In response to the user's first operation, the diagnostic client sends a trigger signal to the vehicle to be diagnosed to trigger the WIFI diagnostic function of the vehicle to be diagnosed.

[0117] In a specific embodiment, the diagnostic client sends a trigger signal to the vehicle to be diagnosed in response to the user's first operation, triggering the WIFI diagnostic function of the vehicle to be diagnosed. The specific WIFI triggering implementation includes:

[0118] Remote control key: The user quickly presses the lock button three times within two seconds. The key communicates with the vehicle's central controller via Bluetooth and sends a WIFI connection instruction, which is then forwarded by the central controller to the communication module to connect to WIFI.

[0119] Near Field Communication (NFC) card: The vehicle's communication module can read a specific NFC card and write the SSID and PSK of a preset Wi-Fi network onto the card. After the user swipes the NFC card against the vehicle's body pillar, the communication module connects to the detected Wi-Fi network.

[0120] Mobile phone Bluetooth: Users can authorize and start Wi-Fi diagnosis in the vehicle application (Application, APP) on their mobile phone, and then the mobile phone uses Bluetooth to communicate with the vehicle.

[0121] Vehicle Display Soft Switch: This soft switch provides Wi-Fi diagnostic functionality on the vehicle's large display. When the user turns on Wi-Fi diagnostics, the vehicle controller sends a trigger signal to the vehicle gateway, which forwards it to the communication module to connect to Wi-Fi. The display also provides an interactive method for changing the Wi-Fi SSID and password.

[0122] Physical buttons in the car: Specific physical buttons can directly transmit signals to the communication module to connect to WIFI.

[0123] S102: Obtain a vehicle list of vehicles to be diagnosed within the coverage area of ​​WIFI.

[0124] In this step, after the diagnostic client sends a trigger signal, it successfully connects to the WIFI of the vehicle to be diagnosed, and the WIFI diagnostic communication link is successfully connected. The diagnostic client can obtain the vehicle list of the vehicle to be diagnosed through the vehicle information declared by the vehicle to be diagnosed.

[0125] In one specific implementation, within Wi-Fi coverage, a vehicle to be diagnosed successfully establishes a Wi-Fi communication link with a diagnostic client. The vehicle to be diagnosed can then communicate its vehicle information to the diagnostic client via the Wi-Fi communication link. The client in the diagnostic device can then receive vehicle information from one or more vehicles via Wi-Fi, thereby obtaining information about at least one vehicle to be diagnosed. The diagnostic client then parses the information from the multiple vehicles to generate a vehicle list, which is then displayed on the client's large screen. This list is available to the user for further operations. The list includes the names, models, and remaining battery levels of the multiple vehicles.

[0126] S103: Select a target vehicle from the vehicle list and initiate a handshake with the TLS port of the target vehicle via the WIFI network.

[0127] In this step, after the diagnostic client successfully obtains the vehicle list of the vehicles to be diagnosed, it can display the vehicle list on the diagnostic client's large screen. The user can use the diagnostic client to select the target vehicle and initiate a handshake to the TLS port of the target vehicle via the Wi-Fi communication link.

[0128] In a specific implementation, the diagnostic client obtains a list of vehicles to be diagnosed. The user selects the target vehicle to be diagnosed through the diagnostic client's large screen operation, and initiates a handshake request to the TLS port of the target vehicle via the Wi-Fi communication link. The user can select 1-10 target vehicles through the diagnostic client operation to simultaneously perform TLS port handshakes. The handshake request initiated to the TLS port of the target vehicle includes:

[0129] (1)Supported protocol versions.

[0130] (2) A random number generated by the client, which is later used to generate a "session key".

[0131] (3) Supported encryption methods.

[0132] (4) Supported compression methods.

[0133] S104: Initiate a DOIP routing activation request to the target vehicle.

[0134] In this step, the diagnostic client successfully shakes hands with the target vehicle. In order to establish a diagnostic session with the target vehicle, the diagnostic client needs to initiate a DOIP routing activation request to the target vehicle.

[0135] In the specific implementation of this step, the diagnostic client successfully shakes hands with the target vehicle, indicating that a TCP connection has been successfully established between the diagnostic client and the target vehicle. Among them, the diagnostic client opens multiple TCP ports, indicating that the diagnostic client can establish a communication connection with the DoIP nodes of multiple target vehicles. Before establishing a diagnostic session with the target vehicle, the diagnostic client needs to initiate a DOIP routing activation request to the target vehicle. Unlike the "routing" of a gateway in the traditional sense, the "routing" in the DoIP protocol refers to the message transmission between the diagnostic client and the diagnostic node of the target vehicle. After the diagnostic client successfully establishes a communication connection with the DoIP nodes of multiple target vehicles, the diagnostic client initiates a DOIP routing activation request to the target vehicle.

[0136] S105: Obtain authorization for providing UDS service to the target vehicle.

[0137] In this step, after the diagnostic client sends a DOIP routing activation request to the target vehicle, a DOIP diagnostic session is established. At this time, authorization for UDS services to the target vehicle needs to be obtained.

[0138] In one specific implementation, a successful DoIP routing activation request from the diagnostic client to the target vehicle indicates a successful DoIP diagnostic session with the target vehicle. After successfully establishing the DoIP diagnostic session with the target vehicle, the diagnostic client obtains authorization to provide UDS services to the target vehicle. The UDS service is authenticated through PKI certificate exchange and serves as a security authentication process for the diagnostic client. Users can customize the security authentication algorithm to prevent unauthorized diagnostic devices from performing diagnostics on the ECU.

[0139] S106: Perform Wi-Fi diagnosis on the target vehicle based on the UDS service and obtain a diagnosis message response.

[0140] In this step, the authorization for UDS service of the target vehicle is obtained, indicating that the WIFI diagnosis is successfully entered. During the diagnostic session loop, the diagnostic client finally receives a diagnostic message response, thereby making a preliminary judgment on the vehicle fault.

[0141] In one specific implementation, the diagnostic client is authorized to perform UDS services on the target vehicle, indicating that the diagnostic client and the target vehicle can successfully diagnose each other. At this point, the user issues a diagnostic request to the diagnostic client through the large screen. The diagnostic client sends a diagnostic message to the target vehicle based on the diagnostic request. The target vehicle performs a series of processing based on the diagnostic message, obtains a diagnostic message response, and sends the diagnostic message response to the diagnostic client. The diagnostic client receives the diagnostic message response and displays it on the large screen for the user to perform subsequent processing.

[0142] This embodiment provides a vehicle Wi-Fi diagnostic method, which is applied to a diagnostic client in a diagnostic device. The vehicle to be diagnosed and the diagnostic device are within the same Wi-Fi coverage area. In response to a user operation, the diagnostic client in the diagnostic device sends a diagnostic trigger signal to the vehicle to be diagnosed, thereby obtaining a vehicle list of vehicles to be diagnosed within the Wi-Fi coverage area. In response to the user operation, the diagnostic client selects the target vehicle to be diagnosed, then initiates a handshake with the target vehicle's TLS port via the Wi-Fi network. After a successful handshake, it initiates a DoIP routing activation request to multiple target vehicles via the TCP port. After establishing a DoIP diagnostic session with the target vehicle, it obtains authorization to perform UDS services on the target vehicle, thereby performing Wi-Fi diagnosis on the target vehicle based on the UDS service and obtaining a diagnostic message response. This method enables users to perform wireless remote diagnosis of the vehicle to be diagnosed and simultaneous diagnosis of multiple target vehicles, eliminating the need for physical wiring harnesses, saving costs, and increasing operating space. Diagnosis is performed through the TLS protocol and UDS services, reducing information security risks.

[0143] Figure 3 This is a flow chart of the second embodiment of the vehicle WIFI diagnostic method provided by this application, as shown in FIG. Figure 3 As shown, based on the above embodiment, in the specific implementation of the vehicle WIFI diagnostic method, the handshake is initiated with the TLS port of the target vehicle through the WIFI network in step S103, and the specific implementation further includes the following steps:

[0144] S1031: Authenticate the target vehicle using the CA certificate chain, and query the OCSP server whether the CA certificate of the target vehicle is revoked.

[0145] In this step, the diagnostic client achieves bidirectional authentication with the target vehicle using the CA certificate chain. Each client and the target vehicle queries the OCSP server to determine if the other's CA certificate has been revoked. If either certificate fails authentication, the diagnostic client cannot initiate a handshake with the target vehicle. If both certificates pass authentication, the diagnostic client can successfully initiate a handshake with the target vehicle.

[0146] In the specific implementation of this step, the diagnostic client and the target vehicle apply for a certificate from a third-party authority CA. First, the diagnostic client and the target vehicle generate a public key and a private key pair respectively, and then the diagnostic client and the target vehicle send confirmation information to the CA respectively. Among them, the confirmation information sent by the diagnostic client and the target vehicle to the CA includes: the domain name currently used by the two, the applicant, and the public key. The diagnostic client and the target vehicle will generate a request file with the confirmation information, and then the diagnostic client and the target vehicle will send the request file to the CA. After receiving the request file, the CA must first conduct an online or offline review. After the review is passed, the CA will issue an authentication certificate to the applicant. Among them, the certificate contains the following information:

[0147] The plain text of the applicant's public key, the applicant's organizational and personal information, the issuing authority CA's information, the validity period, the certificate serial number, and other information also includes a signature.

[0148] After the diagnostic client and the target vehicle obtain each other's certificates, they send each other's certificates to the OCSP server, and the OCSP server obtains information about whether the certificate is revoked through query verification.

[0149] S1032: If the CA certificate of the target vehicle is not revoked and the certificate authentication is passed, the handshake with the TLS port of the target vehicle is successful.

[0150] In this step, the diagnostic client queries the OCSP server for the target vehicle certificate. If the authentication is successful, a handshake with the target vehicle TLS port can be successfully completed.

[0151] In a specific implementation, the diagnostic client queries the OCSP server for the target vehicle certificate. After query verification, the OCSP server obtains the authentication information, and sends this information to the diagnostic client. Based on this information, the diagnostic client can successfully handshake with the TLS port of the target vehicle.

[0152] S1033: If the CA certificate of the target vehicle has not been revoked and the certificate authentication has not passed, the diagnostic client pops up a vehicle list on the large screen.

[0153] In this step, the diagnostic client queries the OCSP server for the target vehicle certificate. If the authentication fails, the diagnostic client cannot successfully handshake with the target vehicle TLS port.

[0154] In a specific implementation, the diagnostic client queries the OCSP server for the target vehicle certificate. After query verification, the OCSP server obtains information that the authentication is not passed. The OCSP server sends this information to the diagnostic client. Based on this information, the diagnostic client fails to handshake with the TLS port of the target vehicle. The diagnostic client then pops up a vehicle list on the large screen, prompting the user to reselect the target vehicle.

[0155] In the vehicle Wi-Fi diagnostic method provided in this embodiment, during a handshake between a diagnostic client and the target vehicle's TLS port over the Wi-Fi network, the client authenticates the target vehicle using its CA certificate chain and queries the OCSP server to determine whether the target vehicle's CA certificate has been revoked. If the target vehicle's CA certificate has not been revoked and certificate authentication passes, the handshake between the diagnostic client and the target vehicle's TLS port is successful. This method uses the TLS protocol to achieve bidirectional authentication between the diagnostic client and the target vehicle, ensuring information security between the diagnostic client and the target vehicle and preventing unauthorized access by unauthorized diagnostic clients or vehicles.

[0156] Figure 4 This is a flow chart of the third embodiment of the vehicle WIFI diagnostic method provided by this application, as shown in FIG. Figure 4 As shown, based on the above embodiment 1, in the specific implementation of the vehicle WIFI diagnostic method, the step S105 of obtaining authorization for the UDS service of the target vehicle further includes the following steps:

[0157] S1051: Initiate a UDS 29 identity authentication request to the target vehicle.

[0158] In this step, after establishing a DOIP diagnostic session, the diagnostic client initiates a UDS 29 identity authentication request to the target vehicle. After the diagnostic client obtains authorization from the target vehicle, subsequent diagnostic processing can be performed.

[0159] In one specific implementation, after a diagnostic client successfully establishes a DOIP diagnostic session with the target vehicle, it initiates a UDS 29 identity authentication request to the target vehicle's diagnostic gateway. This authentication is based on a PKI certificate exchange. The diagnostic client must provide a method to prove its identity and obtain permission from the target vehicle before accessing the target vehicle's data or diagnostic services.

[0160] S1052: Transmit the authentication information of the diagnostic client to the target vehicle via OCSP.

[0161] In this step, after the diagnostic client initiates a UDS 29 identity authentication request to the target vehicle, it uses the CA certificate chain to transmit its own identity authentication information to the target vehicle through the OCSP server.

[0162] In one specific implementation, the target vehicle receives a UDS 29 identity authentication request from the diagnostic client and agrees to the authentication. The diagnostic client then transmits the diagnostic client's CA certificate, the public keys for the network and transport layer encryption algorithms, and the revocation status of the diagnostic client's CA certificate to the target vehicle via an OCSP server.

[0163] S1053: Receive the authentication result of the diagnostic client returned by the target vehicle.

[0164] In this step, the target vehicle successfully receives the identity authentication information transmitted by the diagnostic client. The target vehicle obtains the authentication result by authenticating the identity information and then transmits the authentication result to the diagnostic client. The diagnostic client receives the authentication result returned by the target vehicle to the diagnostic client.

[0165] In a specific implementation, the diagnostic client successfully transmits its identity authentication information to the target vehicle, and the target vehicle verifies whether the diagnostic client's certificate is revoked through the CA certificate chain. The authentication process is similar to the process of S1032 in the above embodiment and will not be repeated here.

[0166] S1054: The authentication result indicates whether the diagnosis client authentication is passed.

[0167] In this step, the diagnostic client obtains the authentication result and determines whether it can be authorized based on the authentication result.

[0168] In a specific implementation, the target vehicle transmits the authentication result to the diagnosis client, and the diagnosis client knows whether its own authentication information has passed the authentication based on the authentication result, thereby knowing whether it can obtain authorization to access the target vehicle.

[0169] S1055: Authentication passed, and authorization to provide UDS service to the target vehicle is obtained.

[0170] In this step, the diagnostic client obtains the authentication result transmitted by the target vehicle. If the authentication result is passed, the diagnostic client is authorized to provide UDS services to the target vehicle.

[0171] In a specific implementation, the diagnostic client obtains the authentication result transmitted by the target vehicle. If the authentication result is passed, it means that the diagnostic client certificate is valid and the client can be authorized to provide UDS services to the target vehicle.

[0172] S1056: Authentication failed, and a vehicle list popped up on the large screen of the diagnostic client.

[0173] In this step, the diagnostic client obtains the authentication result transmitted by the target vehicle. If the authentication result fails, a vehicle list pops up on the large screen of the diagnostic client.

[0174] In a specific implementation, the diagnostic client receives the authentication result transmitted by the target vehicle. If the authentication result fails, it means that the diagnostic client certificate is invalid and the diagnostic client cannot obtain authorization to provide UDS services to the target vehicle. At this time, a vehicle list pops up on the large screen of the diagnostic client, prompting the user to reselect the target vehicle.

[0175] In the vehicle Wi-Fi diagnostic method provided in this embodiment, during the diagnostic client's process of obtaining authorization to provide UDS services to a target vehicle, the diagnostic client initiates a UDS 29 identity authentication request to the target vehicle and receives a response from the target vehicle confirming the authentication result. Based on the authentication result, the diagnostic client determines whether it has been authorized to provide UDS services to the target vehicle. This method uses the 29 service to manage the diagnostic client, enabling the target vehicle to grant different UDS service permissions to different diagnostic sources. Furthermore, bidirectional authentication is performed between the target vehicle and the diagnostic client, ensuring mutual recognition of their identities and data encryption, ensuring data integrity and confidentiality.

[0176] Figure 5 This is a flow chart of a fourth embodiment of a vehicle WIFI diagnostic method provided by this application, as shown in FIG. Figure 5 As shown, the vehicle WIFI diagnostic method is applied to the vehicle to be diagnosed, specifically comprising the following steps:

[0177] S201: Receive a diagnosis trigger signal sent by a diagnosis client.

[0178] In this step, the diagnostic client sends a diagnostic trigger signal to the vehicle to be diagnosed in response to the user's operation, and the vehicle to be diagnosed receives the trigger signal sent by the diagnostic client.

[0179] In a specific implementation, the diagnostic client sends a diagnostic trigger signal to the vehicle to be diagnosed according to different triggering modes, and the vehicle to be diagnosed receives the different diagnostic trigger signals sent by the diagnostic client through a WIFI module.

[0180] S202: Switching to a WIFI diagnostic mode according to a diagnostic trigger signal, and accessing WIFI according to a pre-configured SSID.

[0181] In this step, the vehicle to be diagnosed successfully receives the diagnostic trigger signal and switches to the WIFI diagnostic mode according to the received diagnostic trigger signal, accesses the WIFI according to the pre-configured SSID, and selects the WIFI AP access point with the best signal to access the WIFI.

[0182] In one specific implementation, the vehicle to be diagnosed switches to Wi-Fi diagnostic mode upon receiving a diagnostic trigger signal. It then begins searching for a specific Wi-Fi SSID (which can be a single SSID or multiple by default). The vehicle to be diagnosed selects the Wi-Fi access point with the best signal to initiate access. An SSID corresponds to multiple APs, each with a different coverage radius. The vehicle to be diagnosed then selects the AP with the best signal and the largest coverage radius. Finally, it authenticates using a pre-configured PSK password in the vehicle to connect to the Wi-Fi.

[0183] S203: After successfully handshaking with the diagnosis client via the TLS port, a DOIP routing activation request sent by the diagnosis client is received.

[0184] In this step, the vehicle to be diagnosed successfully connects to WIFI, establishes a WIFI communication link with the diagnostic client, and receives a DOIP routing activation request sent by the diagnostic client after successfully handshaking with the diagnostic client through the TLS port.

[0185] In one specific implementation, after the vehicle being diagnosed successfully connects to Wi-Fi, it successfully establishes a Wi-Fi link with the diagnostic client. The vehicle's diagnostic control module then arbitrates the link, identifying whether other communication links exist. If a link with a higher priority exists, DoIP diagnosis over the Wi-Fi link will not be performed. After the arbitration, the vehicle and the diagnostic client successfully handshake over the TLS port, then receive a DoIP routing activation request from the diagnostic client.

[0186] S204: Establishing a DOIP diagnosis session with the diagnosis client according to the DOIP routing activation request.

[0187] In this step, the vehicle to be diagnosed successfully receives the DOIP routing activation request sent by the diagnostic client. According to the routing activation request, the vehicle to be diagnosed establishes a DOIP diagnostic session with the diagnostic client.

[0188] In one specific implementation, after receiving a DOIP routing activation request from a diagnostic client, the vehicle to be diagnosed locks its Wi-Fi link to ensure the stability of the diagnostic network. The vehicle to be diagnosed then generates a routing activation response based on the DOIP routing activation request and sends it to the diagnostic client, thereby establishing a DOIP diagnostic session with the client.

[0189] S205: After establishing a DOIP diagnosis session with the diagnosis client, authorize the diagnosis client to use the UDS service.

[0190] In this step, after the vehicle to be diagnosed successfully establishes a DOIP diagnostic session with the diagnostic client according to the DOIP routing activation request, the vehicle to be diagnosed then authorizes the diagnostic client for UDS services according to the UDS 29 identity authentication request transmitted by the diagnostic client.

[0191] In the specific implementation of this step, the vehicle to be diagnosed successfully establishes a DOIP diagnostic session with the diagnostic client based on the DOIP routing activation request, and receives the UDS 29 identity authentication request transmitted by the client. The identity authentication request includes: the CA certificate of the diagnostic client, the public keys of the encryption algorithms of the network layer and the transport layer, and the revocation status of the CA certificate of the diagnostic client. The vehicle to be diagnosed then verifies whether the identity information of the diagnostic client has been authenticated through the CA certificate chain. The specific authentication process is similar to the principle of S1031 in the previous embodiment and will not be repeated here. If the authentication is successful, the authentication result is transmitted to the diagnostic client, and the diagnostic client is granted UDS service authorization.

[0192] S206: In response to the WIFI diagnosis performed by the diagnosis client based on the UDS service and DOIP, a diagnosis message response is obtained.

[0193] In this step, the vehicle to be diagnosed authorizes the diagnostic client for UDS services. After successfully granting the diagnostic client UDS service authorization, the diagnostic client obtains access to the vehicle to be diagnosed and successfully performs Wi-Fi diagnosis. The vehicle to be diagnosed receives a diagnostic message response based on the diagnostic message sent by the diagnostic client.

[0194] In the specific implementation of this step, the vehicle to be diagnosed successfully authorizes the diagnostic client UDS service, and the vehicle to be diagnosed obtains vehicle information from the EDU of the vehicle to be diagnosed based on the diagnostic message sent by the diagnostic client, and obtains the corresponding diagnostic message response based on the specific content of the diagnostic message.

[0195] S207: Send the diagnosis message response to the diagnosis client.

[0196] In this step, after the vehicle to be diagnosed obtains vehicle information from the EDU of the vehicle to be diagnosed, it obtains a diagnostic message response, and then the vehicle to be diagnosed sends the diagnostic message response to the diagnostic client so that the user can make subsequent operations.

[0197] In the specific implementation of this step, the vehicle to be diagnosed accesses and obtains vehicle information from its own EDU according to the diagnostic message, and then obtains the corresponding diagnostic message response based on the specific content of the diagnostic message, and sends the diagnostic message response to the diagnostic client through the vehicle's WIFI module.

[0198] The vehicle WIFI diagnostic method provided in this embodiment is applied to the vehicle to be diagnosed. After the vehicle to be diagnosed receives the diagnostic trigger signal sent by the diagnostic client, it switches to WIFI diagnostic mode and accesses WIFI according to the pre-configured SSID. After the vehicle to be diagnosed successfully shakes hands with the diagnostic client through the TLS port, it receives the DOIP routing request sent by the diagnostic client, establishes a DOIP diagnostic session with the diagnostic client according to the DOIP routing activation request, and authorizes the diagnostic client for the UDS service. The vehicle to be diagnosed responds to the WIFI diagnosis performed by the diagnostic client based on the UDS service, obtains a diagnostic message response, and sends the diagnostic message response to the diagnostic client. This method realizes remote wireless diagnosis between the two devices, the diagnostic client and the diagnostic vehicle, abandons the physical wiring harness to connect the OBD interface, saves the cost of maintaining the OBD results, and increases the user's operating space. Diagnosis is performed through the TLS protocol and the UDS 29 service, which reduces information security risks and has a sound authorization mechanism.

[0199] Figure 6 This is a flow chart of the third embodiment of the vehicle WIFI diagnostic method provided by this application, as shown in FIG. Figure 6 As shown, based on the above embodiment, in the specific implementation of the vehicle WIFI diagnostic method, after the handshake with the diagnostic client through the TLS port is successful in step S203, the DOIP routing request sent by the diagnostic client is received. Before the specific implementation, the following steps are also included:

[0200] S2031: Initialize TLS service.

[0201] In this step, the vehicle to be diagnosed successfully establishes a WIFI link with the diagnostic client, and the server of the transport layer security protocol needs to be initialized.

[0202] In a specific implementation, after successfully establishing a Wi-Fi link, the vehicle starts the DOIP TLS Server, initializes the server side of the transport layer security protocol, and prepares for the TLS handshake.

[0203] S2032: The vehicle to be diagnosed declares vehicle information via the local area network.

[0204] In this step, after initializing the transport layer security protocol server, the vehicle to be diagnosed declares vehicle information in the local area network through the WIFI module.

[0205] In one specific implementation, the vehicle being diagnosed announces its information within the local area network (LAN), allowing the diagnostic client to know that the vehicle being diagnosed is online. Specifically, the diagnostic client sends a broadcast vehicle discovery message over the Wi-Fi link. All ECUs of the vehicles being diagnosed that receive this message will then transmit their identity information. Using the identity information sent back by each ECU, the diagnostic client obtains a list of vehicles being diagnosed.

[0206] In this embodiment of the vehicle Wi-Fi diagnostic method, before the diagnostic client completes the TLS handshake, the vehicle to be diagnosed initiates the TLS service and announces its vehicle information within the local area network via the Wi-Fi module. This method enables the diagnostic client to remotely obtain the vehicle list of the vehicle to be diagnosed, saving the user time for one-on-one verification.

[0207] The following uses the diagnosis of a vehicle by a diagnostic computer in a 4S store as an example to illustrate the vehicle WIFI diagnostic method proposed in this application. Figure 7 This is a flowchart of a specific example of the vehicle WIFI diagnostic method proposed in this application. Figure 8 This is a WIFI diagnostic timing diagram. The specific implementation steps include:

[0208] S301: Drive the vehicle to a dedicated WIFI coverage area.

[0209] In this step, the dedicated WIFI is the WIFI in the 4S store. This WIFI can be customized. Drive the vehicle to the area covered by the WIFI in the 4S store.

[0210] In a specific implementation, the vehicle to be diagnosed may be driven to an area covered by the WIFI of the 4S store, which may be a parking lot inside the store or any place outside the store where a WIFI signal can be received.

[0211] S302: The user triggers the vehicle WIFI connection.

[0212] In this step, the user operates the diagnostic computer, and then the diagnostic computer sends a diagnostic trigger signal to the vehicle, thereby triggering the vehicle's WIFI connection.

[0213] In a specific implementation, the user can trigger the event in the following ways:

[0214] Remote control key: Press the lock button three times quickly within two seconds. The key communicates with the vehicle's central controller via Bluetooth to send a WIFI connection instruction, which is then forwarded by the central controller to the communication module to connect to WIFI.

[0215] NFC card: Specific NFC cards can be read by the vehicle communication module. Such cards are written with the SSID and PSK password of the Wi-Fi network. After the user swipes the NFC card on the vehicle body pillar, the communication module will connect to the read Wi-Fi network.

[0216] Mobile Bluetooth: Users can authorize and initiate Wi-Fi diagnostics via the vehicle app on their phone. The phone then communicates with the vehicle via Bluetooth. The phone's Bluetooth only provides a signal to initiate Wi-Fi diagnostics, known as the diagnostic trigger signal. Subsequent disconnection of the phone's Bluetooth connection with the vehicle will not affect the diagnostics.

[0217] Vehicle Display Soft Switch: A soft switch for Wi-Fi diagnostics is provided on the vehicle's large display. When the user turns on Wi-Fi diagnostics, the vehicle controller sends a diagnostic trigger signal to the vehicle gateway, which forwards it to the communication module for Wi-Fi connection. The large display also provides an interactive method for changing the Wi-Fi SSID and password. The SSID can be entered and selected on the large display.

[0218] Physical buttons in the car: Specific physical buttons can directly transmit signals to the communication module to connect to WIFI.

[0219] S303: The vehicle WIFI module searches for and connects to WIFI.

[0220] In this step, the vehicle's WIFI module receives a diagnostic trigger signal, switches to WIFI diagnostic mode, and connects to WIFI by searching for the 4S store's WIFI SSID.

[0221] In a specific implementation, Figure 8 As shown, upon receiving a diagnostic trigger signal, the vehicle's communication module switches to Wi-Fi diagnostic mode and begins searching for the 4S dealership's specific Wi-Fi SSID. The module then selects the Wi-Fi access point with the best signal and initiates access. An SSID corresponds to multiple access points, each with a different coverage radius. The vehicle selects the one with the best signal and the largest coverage radius. Authentication is performed using the PSK password pre-set in the communication module, and the Wi-Fi status is displayed on the vehicle's screen.

[0222] S304: The vehicle diagnosis controller prepares the DOIP TLS Server.

[0223] In this step, the vehicle is connected to the 4S store's WIFI, and the vehicle communication module notifies the vehicle controller that the WIFI link has been successfully established. At this time, the vehicle diagnosis controller initializes the DOIP TLS Server and prepares for DOIP diagnosis.

[0224] In a specific implementation, Figure 8As shown, the vehicle Wi-Fi module notifies the vehicle controller that the Wi-Fi link has been successfully established. The diagnostic control module arbitrates the link and identifies whether there are other communication links. If there is a link with a higher priority, DoIP diagnosis on the Wi-Fi link will not be performed. Then the vehicle diagnostic controller starts the DoIP TLS Server.

[0225] S305: The diagnostic computer displays a list of connected vehicles.

[0226] In this step, the vehicle diagnostic controller prepares the DOIP TLS Server, initializes the TLS Server, and declares its own vehicle information in the local area network through the Wi-Fi module.

[0227] In a specific implementation, Figure 8 As shown, the vehicle diagnostic gateway sends the vehicle information to the vehicle WIFI module, and then the vehicle WIFI module sends the vehicle information to the diagnostic computer. The diagnostic computer flashes the WIFI connected vehicle list, thereby displaying the connected vehicle list on the large screen.

[0228] S306: The user selects a vehicle and confirms to start diagnosis.

[0229] In this step, the diagnostic computer obtains a list of vehicles, and the user selects a vehicle from the list to confirm and start diagnosis.

[0230] In a specific implementation, the diagnostic computer displays a vehicle list on a large screen. The user can select 1-10 vehicles from the vehicle list on the computer screen to confirm and start diagnosis. The vehicle list includes the remaining battery power of the vehicles. The diagnostic computer can manage the battery power based on the remaining battery power. The specific implementation steps are as follows:

[0231] The vehicle's diagnostic controller obtains power data from the vehicle's central controller. When the power is sufficient, the diagnostic controller allows Wi-Fi diagnostic communication to be established.

[0232] When the vehicle is connected to WIFI, the diagnostic controller will wait for the diagnostic client to connect and count the waiting time. When the waiting time exceeds the preset time, the vehicle will turn off the WIFI module to save power.

[0233] When the vehicle is connected to the diagnostic client, the vehicle diagnostic controller will also count the idle time. When the idle time exceeds the preset time, the vehicle will prompt a diagnostic client disconnection warning. If the user does not operate, the vehicle will disconnect the DoIP diagnostic link and turn off the Wi-Fi module after the operation waiting time to save power.

[0234] For software download tasks, the diagnostic computer uses the size information and download rate of the software package to estimate the download time, and uses the vehicle's power status to estimate the remaining safe flashing time. If the power is insufficient to ensure downloading, it will prompt that the power is low and require charging.

[0235] S307: The diagnostic computer connects to the vehicle's DOIP TLS Server.

[0236] In this step, the user selects the vehicle and confirms to start the diagnosis. The diagnostic computer connects to the vehicle's DOIP TLS Server through the TCP port.

[0237] In a specific implementation, the diagnostic computer opens multiple TCP ports and connects to the vehicle DOIPTLS Server through the ports, and can connect to multiple vehicles for diagnosis at the same time.

[0238] S308: TLS handshake.

[0239] In this step, the diagnostic computer connects to the vehicle's DOIP TLS Server and initiates a TLS handshake with the vehicle.

[0240] In a specific implementation, Figure 8 As shown, the vehicle opens the DOIP TLS Server, the diagnostic computer and the vehicle diagnostic gateway connect to TLS, the diagnostic computer initiates a TLS handshake to the vehicle, both parties use the CA certificate chain to authenticate each other, and query the OCSP server whether the other party's CA certificate is revoked. If the CA certificates of both parties are not revoked and the certificate authentication is passed, the TLS handshake is successful. If the certificate authentication is passed, the TLS handshake fails.

[0241] S309: Routing activation.

[0242] In this step, the TLS handshake between the diagnostic computer and the vehicle is successful, and the diagnostic computer sends a DOIP routing activation request to the vehicle.

[0243] In a specific implementation, Figure 8 As shown in the figure, the diagnostic computer sends a DOIP routing activation request to the vehicle. The vehicle's Wi-Fi module receives the DOIP routing activation request and sends it to the vehicle diagnostic gateway. The vehicle diagnostic gateway processes the request, locks the Wi-Fi link, and then issues a routing activation response, which is then sent to the diagnostic computer, thus activating the DOIP routing.

[0244] S310: UDS 29 identity authentication.

[0245] In this step, after the routing is activated, the vehicle performs UDS 29 authentication on the diagnostic computer.

[0246] In a specific implementation, UDS 29 identity authentication is based on PKI certificate exchange. The specific authentication process includes: the diagnostic computer sends an identity authentication request to the vehicle ECU. The request contains the certificate of the diagnostic computer. After receiving the request message, the vehicle ECU will verify the certificate of the diagnostic computer. If the certificate verification is successful, the ECU will create a challenge and send the challenge back to the diagnostic computer. The diagnostic computer calculates the proof of ownership by signing the challenge ECU. The diagnostic computer sends the proof of ownership to the ECU. The ECU verifies the proof of ownership with the public key in the certificate tester received and sets access rights. If the proof of ownership is verified, the ECU returns a response. Finally, the vehicle ECU responds with a successful authentication, and the UDS 29 identity authentication is completed.

[0247] S311: Entering a diagnostic session, prompting the user that the connection is successful.

[0248] In this step, after passing the UDS 29 identity authentication, the diagnostic computer obtains the UDS service authorization for the vehicle, thereby entering the diagnostic session and prompting the user that the connection is successful.

[0249] In a specific implementation, when entering a diagnostic session, the diagnostic computer prompts the user that the connection is successful, and sends a pop-up window to prompt the user whether to perform the diagnosis.

[0250] S312: Execute diagnosis, and the vehicle prompts that diagnosis is in progress.

[0251] In this step, after the user successfully connects to the diagnostic session, the vehicle will prompt "Diagnosis in Progress" and start the diagnosis.

[0252] In a specific implementation, Figure 8 As shown, the user gives a diagnostic request to the diagnostic computer, the diagnostic computer generates a diagnostic message based on the diagnostic request, and sends the diagnostic message to the vehicle diagnostic gateway. The vehicle diagnostic gateway obtains a diagnostic response from the ECU based on the diagnostic message, and the vehicle diagnostic gateway generates a diagnostic message response based on the diagnostic response, and sends the diagnostic message response to the diagnostic computer.

[0253] S313: Diagnosis completed, disconnection.

[0254] In this step, after completing the diagnosis, the user disconnects from the vehicle through the diagnostic computer client or the vehicle actively disconnects.

[0255] In one specific implementation, after completing the diagnosis, the user disconnects the vehicle from the diagnostic computer client or the vehicle actively disconnects. The diagnostic computer closes the TCP port, and the vehicle diagnostic gateway closes the diagnostic session, unlocks the Wi-Fi link, and issues a diagnostic shutdown warning.

[0256] This embodiment provides an example of a vehicle Wi-Fi diagnostic method. It allows a vehicle to use its controller's Wi-Fi module to connect to a diagnostic computer's local area network (LAN) and broadcast its presence. The diagnostic computer then identifies the vehicle within the LAN and establishes a diagnostic connection. This connection uses the TLS protocol and the UDS 29 service to protect data, and a single computer can support simultaneous diagnosis or software flashing for multiple vehicles. This method eliminates the need for users to manually connect hardwired connections for each vehicle, reducing maintenance costs associated with damage to the OBD port and wiring harness. The one-to-many diagnostic approach improves efficiency and protects data security.

[0257] Figure 9 This is a structural diagram of the first embodiment of the vehicle WIFI diagnostic device provided in the embodiment of the present application, as shown in FIG. Figure 9 As shown, the vehicle WIFI diagnostic device 400 includes:

[0258] The first sending module 401 is configured to send a diagnosis trigger signal to the vehicle to be diagnosed in response to a first operation of the user.

[0259] The first acquisition module 403 is used to acquire a vehicle list of vehicles to be diagnosed within the coverage area of ​​WIFI.

[0260] The processing module 405 is configured to select a target vehicle from the vehicle list in response to a second operation performed by the user on the vehicle list.

[0261] The communication processing module 406 is used to initiate a handshake with the TLS port of the target vehicle via the WIFI network.

[0262] The second sending module 402 is configured to initiate a DoIP routing activation request to the target vehicle after successfully handshaking with the TLS port of the target vehicle.

[0263] The second acquisition module 404 is configured to acquire authorization for providing UDS services to the target vehicle after establishing a DoIP diagnostic session with the target vehicle.

[0264] The diagnosis module 407 is used to perform Wi-Fi diagnosis on the target vehicle based on the UDS service and DoIP, and obtain a diagnosis response message.

[0265] Figure 10 This is a structural diagram of the second embodiment of the vehicle WIFI diagnostic device provided in the embodiment of the present application, as shown in FIG. Figure 10 As shown, the second acquisition module 404 includes: a first sending unit 4041, which is used to initiate a UDS 29 identity authentication request to the target vehicle after establishing a DoIP diagnostic session with the target vehicle.

[0266] The second sending unit 4042 is used to bind the CA certificate of the diagnostic client, the public keys of the encryption algorithms of the network layer and the transport layer, and the revocation status of the CA certificate of the diagnostic client to the target vehicle through OCSP and transmit them.

[0267] The information receiving unit 4043 is used to receive the authentication result of the diagnostic client returned by the target vehicle.

[0268] The processing unit 4044 is configured to obtain authorization for providing the UDS service to the target vehicle when the authentication result indicates that the diagnosis client is authenticated successfully.

[0269] Figure 11 This is a structural diagram of the third embodiment of the vehicle WIFI diagnostic device provided in the embodiment of the present application, as shown in FIG. Figure 11 As shown, the communication processing module 406 includes: an information acquisition unit 4061, which is used to authenticate the target vehicle using the CA certificate chain and query the OCSP server whether the CA certificate of the target vehicle is revoked.

[0270] The processing unit 4062 is configured to successfully handshake with the TLS port of the target vehicle if the CA certificate of the target vehicle is not revoked and the certificate authentication is passed.

[0271] Figure 12 This is a structural diagram of a fourth embodiment of a vehicle WIFI diagnostic device provided in an embodiment of the present application, as shown in FIG. Figure 12 As shown, the diagnosis module 407 includes:

[0272] The information generating unit 4071 is configured to generate a diagnostic message for the target vehicle in response to a third operation of the user.

[0273] The sending unit 4072 is used to send the diagnostic message to the target vehicle based on the UDS service.

[0274] The information receiving unit 4073 is configured to receive a diagnostic message response from the target vehicle based on the UDS service.

[0275] The vehicle WIFI diagnostic devices provided in Examples 1, 2, 3, and 4 are used to achieve the technical effects of Examples 1 and 2 of the aforementioned methods. Their implementation principles and technical effects are similar and will not be described in detail here.

[0276] Figure 13 This is a structural diagram of a fifth embodiment of a vehicle WIFI diagnostic device provided in an embodiment of the present application, as shown in FIG. Figure 13 As shown, the vehicle WIFI diagnostic device 500 includes:

[0277] The first receiving module 501 is configured to receive a diagnosis trigger signal sent by a diagnosis client.

[0278] The WIFI module 503 switches to the WIFI diagnosis mode according to the diagnosis trigger signal, and accesses the WIFI according to the pre-configured SSID.

[0279] The information declaration module 508 is used to initialize the TLS service and declare the vehicle information of the vehicle to be diagnosed in the WIFI local area network.

[0280] The second receiving module 502 is configured to receive a DoIP routing activation request sent by the diagnosis client after successfully handshaking with the diagnosis client via the TLS port.

[0281] The communication processing module 504 is configured to establish a DoIP diagnostic session with the diagnostic client according to the DoIP routing activation request.

[0282] The first sending module 505 is configured to send a UDS service authorization to the diagnostic client after establishing a DoIP diagnostic session with the diagnostic client.

[0283] The diagnosis module 507 is configured to obtain a diagnosis message response in response to the Wi-Fi diagnosis performed by the diagnosis client based on the UDS service.

[0284] The second sending module 506 is configured to send the diagnosis message response to the diagnosis client.

[0285] Figure 14 This is a structural diagram of the sixth embodiment of the vehicle WIFI diagnostic device provided in the embodiment of the present application, as shown in FIG. Figure 14 As shown, the communication processing module 504 includes:

[0286] The control unit 5041 is used to activate the route according to the DoIP route activation request and control and maintain the WIFI link of the vehicle to be diagnosed.

[0287] The processing unit 5042 is configured to establish a DoIP diagnostic session with the diagnostic client after the DoIP route is activated.

[0288] Figure 15 This is a structural diagram of the seventh embodiment of the vehicle WIFI diagnostic device provided in the embodiment of the present application, as shown in FIG. Figure 15 As shown, the first sending module 505 includes:

[0289] The first receiving unit 5051 is configured to receive a UDS 29 identity authentication request sent by a diagnostic client.

[0290] The second receiving unit 5052 is configured to receive the CA certificate, the public keys of the encryption algorithms of the network layer and the transport layer, and the revocation status of the CA certificate sent by the diagnosis client according to the UDS 29 identity authentication request.

[0291] The processing unit 5053 uses the CA certificate chain to authenticate the CA certificate of the diagnosis client, and after the CA certificate of the diagnosis client is authenticated, authorizes the diagnosis client to have the permission to use the UDS service.

[0292] Figure 16 This is a structural diagram of an eighth embodiment of a vehicle WIFI diagnostic device provided in an embodiment of the present application, as shown in FIG. Figure 16 As shown, the diagnosis module 507 includes:

[0293] The first receiving unit 5071 is configured to receive a diagnostic message sent by the diagnostic client based on the UDS service.

[0294] The processing unit 5072 is configured to perform Wi-Fi diagnosis on the vehicle according to the diagnostic message and obtain a diagnostic message response.

[0295] The sending unit 5073 is configured to send the diagnosis message response to the diagnosis client.

[0296] The vehicle WIFI diagnostic devices provided in Examples 5, 6, 7, and 8 are used to achieve the technical effects of Examples 4 and 5 of the aforementioned methods. Their implementation principles and technical effects are similar and will not be repeated here.

[0297] The present embodiment also provides a diagnostic device 600, Figure 17 This is a schematic diagram of the structure of a diagnostic device provided in an embodiment of the present application. The diagnostic device 600 includes:

[0298] The memory 601 is used to store computer instructions.

[0299] The processor 602 is configured to execute computer instructions stored in the memory, so that the diagnostic device executes the vehicle WIFI diagnostic method of the first embodiment.

[0300] The wireless access port 603 is used to access a WIFI network.

[0301] TCP port 604 is used to establish a diagnostic connection with the vehicle to be diagnosed.

[0302] The embodiment of the present application further provides a vehicle 700, Figure 18 This is a schematic diagram of the structure of a vehicle provided in an embodiment of the present application. Vehicle 700 includes:

[0303] The memory 701 is used to store computer instructions.

[0304] The processor 702 is configured to execute computer instructions stored in the memory, so that the vehicle device to be diagnosed executes the vehicle WIFI diagnosis method of the first embodiment.

[0305] The WIFI module 703 is used for the vehicle to be diagnosed to connect to the WIFI network and switch to the WIFI diagnosis mode.

[0306] The communication interface 704 is used for communication connection between the diagnostic device and the vehicle device to be diagnosed.

[0307] The diagnosis controller 705 is used to control the diagnosis of the vehicle to be diagnosed.

[0308] ECU 706 is used to store all vehicle information of the vehicle to be diagnosed.

[0309] An embodiment of the present application further provides a storage medium storing a computer program.

[0310] When the computer program is executed, any one of the method embodiments is implemented.

[0311] The present application also provides a vehicle WIFI diagnostic system. Figure 19 The schematic diagram of the architecture of the vehicle Wi-Fi diagnostic system provided in an embodiment of the present application includes: a diagnostic device and at least one vehicle to be diagnosed.

[0312] The diagnostic equipment is connected to the vehicle to be diagnosed via WIFI network mode.

[0313] The diagnostic device is used to execute the technical solution of diagnosing the client side in any of the above method embodiments. The vehicle to be diagnosed is used to execute the technical solution of the vehicle side in any of the above method embodiments.

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

[0315] It should be understood that the present application is not limited to the exact structure described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present application is limited only by the appended claims.

Claims

1. A vehicle WIFI diagnostic method, characterized in that: A diagnostic client is applied to a diagnostic device, the diagnostic client including multiple TCP ports, the multiple TCP ports being used to establish diagnostic connections with multiple vehicles to be diagnosed; the method comprising: In response to a first operation by a user, a diagnosis trigger signal is sent to a vehicle to be diagnosed, where the vehicle to be diagnosed and the diagnostic device are within the coverage range of the same wireless local area network WIFI; Obtaining a vehicle list of multiple vehicles to be diagnosed within the coverage area of ​​the WIFI, wherein the vehicle list includes information of the multiple vehicles to be diagnosed; In response to a second operation on the vehicle list by the user, selecting a plurality of target vehicles from the vehicle list, and initiating a handshake with a Transport Layer Security (TLS) port of the plurality of target vehicles via a Wi-Fi network; After successfully handshaking with the TLS ports of the multiple target vehicles, initiating diagnostic DoIP routing activation requests based on the vehicle Ethernet to the multiple target vehicles through the multiple TCP ports, wherein the DoIP routing activation requests are used to establish DoIP diagnostic sessions with the multiple target vehicles; After establishing a DoIP diagnostic session with the plurality of target vehicles, obtaining authorization for performing a unified diagnostic service (UDS) service on the plurality of target vehicles; Perform WIFI diagnosis on the multiple target vehicles based on the UDS service and obtain a diagnosis message response.

2. The method according to claim 1, characterized in that The initiating handshake with the TLS ports of the plurality of target vehicles via the WIFI network includes: Authenticating the multiple target vehicles using a certificate authority (CA) certificate chain, and querying an online certificate status protocol (OCSP) server to determine whether the CA certificates of the multiple target vehicles are revoked; If the CA certificates of the multiple target vehicles are not revoked and the certificate authentication is passed, the TLS port handshake with the multiple target vehicles is successful.

3. The method according to claim 2, characterized in that After establishing the DoIP diagnostic session with the multiple target vehicles, obtaining authorization to provide the UDS service to the multiple target vehicles includes: After establishing a DoIP diagnostic session with the multiple target vehicles, initiating a UDS 29 identity authentication request to the multiple target vehicles; binding the CA certificate of the diagnostic client, the public keys of the encryption algorithms of the network layer and the transport layer, and the revocation status of the CA certificate of the diagnostic client to the multiple target vehicles through OCSP; receiving authentication results of the diagnostic client returned by the plurality of target vehicles; When the authentication result indicates that the diagnosis client is authenticated, authorization to provide UDS services to the multiple target vehicles is obtained.

4. The method according to claim 1, wherein The obtaining of a vehicle list of multiple vehicles to be diagnosed within the coverage of the WIFI includes: receiving vehicle information declared by a plurality of vehicles to be diagnosed within the range of the wireless local area network WIFI; The vehicle information of the plurality of vehicles to be diagnosed is parsed to obtain the vehicle list.

5. The method according to any one of claims 1 to 4, characterized in that The performing WIFI diagnosis on the plurality of target vehicles based on the UDS service and obtaining a diagnosis message response includes: In response to a third operation by the user, generating a diagnostic message for the plurality of target vehicles, the diagnostic message including content of diagnosing the plurality of target vehicles; Based on the UDS service, the diagnostic message is sent to the multiple target vehicles; The diagnostic message responses of the plurality of target vehicles are received based on a UDS service.

6. A vehicle WIFI diagnostic method, characterized in that: Applied to a vehicle to be diagnosed, the method includes: Receiving a diagnostic trigger signal sent by a diagnostic client, wherein the diagnostic client is disposed in a diagnostic device, and the diagnostic device and the vehicle to be diagnosed are within the same wireless local area network (WIFI) coverage area; the diagnostic client includes multiple TCP ports, and the multiple TCP ports are used to establish diagnostic connections with the multiple vehicles to be diagnosed to achieve concurrent diagnosis of the multiple vehicles to be diagnosed; Switch to the WIFI diagnostic mode according to the diagnostic trigger signal, and access the WIFI according to the pre-configured service set identifier SSID; After successfully handshaking with the diagnostic client via the secure transport layer protocol TLS port, receiving a diagnostic DoIP routing activation request based on the vehicle Ethernet sent by one of the multiple TCP ports of the diagnostic client; Establishing a DoIP diagnostic session with the diagnostic client according to the DoIP routing activation request; After establishing a DoIP diagnostic session with the diagnostic client, sending a unified diagnostic service (UDS) service authorization to the diagnostic client; In response to the WIFI diagnosis performed by the diagnostic client based on the UDS service, obtaining a diagnostic message response; The diagnostic message response is sent to the diagnostic client.

7. The method according to claim 6, characterized in that Before successfully handshaking with the diagnostic client via the TLS port, the method further includes: Initialize the TLS service and declare the vehicle information of the vehicle to be diagnosed in the wireless local area network WIFI.

8. The method according to claim 6, characterized in that The establishing a DoIP diagnostic session with the diagnostic client according to the DoIP routing activation request includes: The routing is activated according to the DoIP routing activation request, and the WIFI link of the vehicle to be diagnosed is controlled and maintained, thereby establishing a DoIP diagnostic session with the diagnostic client.

9. The method according to claim 8, characterized in that The step of authorizing the diagnostic client to provide a UDS service includes: Receiving a UDS 29 identity authentication request sent by the diagnostic client; According to the UDS 29 identity authentication request, receive the certificate authority CA certificate, the public key of the network layer and transport layer encryption algorithm and the revocation status of the CA certificate sent by the diagnostic client; Authenticating the CA certificate of the diagnostic client using a CA certificate chain; After the CA certificate of the diagnosis client is authenticated, the diagnosis client is authorized to provide the UDS service.

10. The method according to any one of claims 6 to 9, characterized in that The obtaining of a diagnostic message response in response to the WIFI diagnosis performed by the diagnostic client based on the UDS includes: receiving a diagnostic message sent by the diagnostic client based on the UDS service, wherein the diagnostic message includes content of diagnosing the vehicle; Performing WIFI diagnosis on the vehicle according to the diagnostic message to obtain the diagnostic message response; The diagnostic message response is sent to the diagnostic client.

11. A vehicle WIFI diagnostic device, characterized in that: A diagnostic client used in a diagnostic device, the diagnostic client including multiple TCP ports for establishing diagnostic connections with multiple vehicles to be diagnosed; the device comprising: a first sending module, configured to send a diagnosis trigger signal to the vehicle to be diagnosed in response to a first operation of the user; The first acquisition module is used to obtain a vehicle list of multiple vehicles to be diagnosed within the coverage area of ​​the wireless local area network WIFI; the vehicle list includes information of the multiple vehicles to be diagnosed; a processing module, configured to select a plurality of target vehicles from the vehicle list in response to a second operation of the user on the vehicle list; A communication processing module, configured to initiate a handshake with a secure transport layer protocol TLS port of the plurality of target vehicles via a WIFI network; A second sending module is configured to initiate a diagnostic DoIP routing activation request based on the vehicle Ethernet to the multiple target vehicles through the multiple TCP ports after successfully handshaking with the TLS ports of the multiple target vehicles; A second acquisition module is configured to acquire authorization for performing a unified diagnostic service (UDS) on the multiple target vehicles after establishing a DoIP diagnostic session with the multiple target vehicles; The diagnostic module is used to perform Wi-Fi diagnosis on the multiple target vehicles based on the UDS service and obtain a diagnostic message response.

12. A vehicle WIFI diagnostic device, characterized in that: Applied to a vehicle to be diagnosed, the device comprises: a first receiving module, configured to receive a diagnostic trigger signal sent by a diagnostic client; the diagnostic client comprising a plurality of TCP ports, the plurality of TCP ports being configured to establish diagnostic connections with a plurality of vehicles to be diagnosed, thereby enabling concurrent diagnosis of the plurality of vehicles to be diagnosed; A WIFI module is configured to switch to a wireless local area network WIFI diagnostic mode according to the diagnostic trigger signal and access the WIFI according to a pre-configured service set identifier SSID; A second receiving module is configured to receive a diagnostic DoIP routing activation request based on vehicle Ethernet sent by one of the multiple TCP ports of the diagnostic client after successfully handshaking with the diagnostic client through the TLS port; A communication processing module, configured to establish a DoIP diagnostic session with the diagnostic client according to the DoIP routing activation request; A first sending module is used to send a unified diagnostic service UDS service authorization to the diagnostic client after establishing a DoIP diagnostic session with the diagnostic client; A diagnostic module, configured to obtain a diagnostic message response in response to the WIFI diagnosis performed by the diagnostic client based on the UDS service; The second sending module is configured to send the diagnostic message response to the diagnostic client.

13. A diagnostic device, characterized in that include: Processor, memory, wireless access port, Transmission Control Protocol TCP port The memory stores computer instructions; The processor executes the computer instructions stored in the memory, so that the diagnostic device performs the vehicle WIFI diagnostic method according to any one of claims 1 to 5.

14. A vehicle, characterized in that: include: Memory, processor, wireless LAN WIFI module, communication interface, diagnostic controller, vehicle computer control module ECU; The memory stores computer instructions; The processor executes the computer instructions stored in the memory, so that the vehicle device performs the vehicle WIFI diagnostic method according to any one of claims 6 to 10.

15. A storage medium, characterized in that: The storage medium stores a computer program; When the computer program is executed, the vehicle WIFI diagnostic method according to any one of claims 1 to 10 is implemented.

16. A vehicle WIFI diagnostic system, characterized in that: include: A diagnostic device and at least one vehicle to be diagnosed, wherein the diagnostic device and the vehicle to be diagnosed are connected via a wireless local area network (WIFI) network mode; The diagnostic device is used to perform the vehicle WIFI diagnostic method according to any one of claims 1 to 5; The vehicle is used to execute the vehicle WIFI diagnostic method according to any one of claims 6 to 10.

Images