Vehicle diagnosis method and drive recorder

Abstract

The application provides a vehicle diagnosis method and a driving recorder. The vehicle diagnosis method comprises the following steps: the driving recorder acquires a vehicle diagnosis request, and sends the vehicle diagnosis request and a vehicle identification code to a cloud diagnosis system; diagnosis instructions sent by the cloud diagnosis system are acquired, the diagnosis instructions being generated by the cloud diagnosis system according to the vehicle identification code; the diagnosis instructions are sent to a vehicle diagnosis system; diagnosis response data of the vehicle sent by the vehicle diagnosis system are acquired; and the diagnosis response data are sent to the cloud diagnosis system. The complex diagnosis protocol analysis and vehicle model adaptation logic are all moved to the cloud for execution, thereby breaking through the limitation of the local computing power and storage space of the driving recorder, and without preinstalling a large amount of vehicle diagnosis protocol library locally, the driving recorder can support deep diagnosis of the whole system of various mainstream vehicle models.

Description

Technical Field

[0001] This application pertains to the field of vehicle diagnostics, and particularly relates to vehicle diagnostic methods and dashcams. Background Technology

[0002] A dashcam is a device used for recording video. Currently, some dashcams integrate On-Board Diagnostics (OBD) systems, enabling partial data reading, such as retrieving basic vehicle data or OBD fault codes. However, due to limitations in local computing power and storage, dashcams with integrated OBD cannot perform in-depth diagnostics across all vehicle models, especially for proprietary protocol diagnostics of systems like the engine, transmission, and ABS, making it difficult to cover multiple vehicle types. Summary of the Invention

[0003] In view of this, embodiments of this application provide a vehicle diagnostic method and a dashcam to solve the problem that existing dashcams cannot cover vehicle diagnostics for all vehicle models and systems.

[0004] The first aspect of this application provides a vehicle diagnostic method, executed in a dashcam, comprising: Obtain vehicle diagnostic request; Send the vehicle diagnostic request and vehicle identification number to the cloud diagnostic system; Obtain diagnostic instructions sent by the cloud-based diagnostic system, which are generated by the cloud-based diagnostic system based on the vehicle identification code; The diagnostic command is sent to the on-board diagnostic system; Obtain the vehicle's diagnostic response data sent by the on-board diagnostic system; The diagnostic response data is sent to the cloud-based diagnostic system.

[0005] In one embodiment, obtaining a vehicle diagnostic request includes: Get voice commands; The voice command is recognized to obtain the vehicle diagnostic request.

[0006] In one embodiment, the voice command is a preset voice command used to perform a full vehicle inspection, clear fault codes, or read any one of the data streams.

[0007] In one embodiment, obtaining the diagnostic instructions sent by the cloud-based diagnostic system includes: An encrypted communication tunnel is established between the relay server and the cloud diagnostic robot instance allocated by the cloud diagnostic system. The cloud diagnostic robot instance is determined by the cloud diagnostic system based on the vehicle identification code. The diagnostic instructions sent by the cloud-based diagnostic system are obtained through the encrypted communication tunnel.

[0008] In one embodiment, after sending the diagnostic response data to the cloud-based diagnostic system, the method further includes: Obtain and output the diagnostic report generated by the cloud-based diagnostic system based on the diagnostic response data.

[0009] In one embodiment, obtaining and outputting a diagnostic report generated by the cloud-based diagnostic system based on the diagnostic response data includes: Obtain the diagnostic report generated by the cloud-based diagnostic system based on the diagnostic response data; The diagnostic report will be read aloud.

[0010] A second aspect of this application provides a vehicle diagnostic method, including: The dashcam acquires a vehicle diagnostic request and sends the vehicle diagnostic request and vehicle identification number to the cloud diagnostic system. The cloud-based diagnostic system generates diagnostic instructions based on the vehicle identification code and sends the diagnostic instructions to the dashcam. The dashcam sends the diagnostic command to the vehicle diagnostic system; The dashcam acquires the vehicle's diagnostic response data sent by the on-board diagnostic system; The dashcam sends the diagnostic response data to the cloud-based diagnostic system.

[0011] In one embodiment, the cloud-based diagnostic system generates a diagnostic command based on the vehicle diagnostic request and the vehicle identification number, and sends the diagnostic command to the dashcam, including: The cloud diagnostic system allocates a cloud diagnostic robot instance to the vehicle identification code according to the vehicle diagnostic request, and enables the cloud diagnostic robot instance to establish an encrypted communication tunnel with the dashcam through a relay server. The diagnostic command is sent to the vehicle recorder through the encrypted communication tunnel.

[0012] In one embodiment, the dashcam acquires a vehicle diagnostic request and sends the vehicle request and vehicle identification number to a cloud-based diagnostic system, including: The dashcam acquires a vehicle diagnostic request and sends the vehicle diagnostic request and the vehicle identification code to the cloud diagnostic system through the Golo platform.

[0013] A third aspect of this application provides a vehicle diagnostic device, comprising: The diagnostic request acquisition module is used to acquire vehicle diagnostic requests; The diagnostic request sending module is used to send the vehicle diagnostic request and vehicle identification code to the cloud diagnostic system; The diagnostic instruction acquisition module is used to acquire diagnostic instructions sent by the cloud-based diagnostic system, which are generated by the cloud-based diagnostic system based on the vehicle identification code. A diagnostic command sending module is used to send the diagnostic command to the vehicle diagnostic system; The response data acquisition module is used to acquire the vehicle's diagnostic response data sent by the on-board diagnostic system; The response data sending module is used to send the diagnostic response data to the cloud diagnostic system.

[0014] In one embodiment, the diagnostic request acquisition module is specifically used for: Get voice commands; The voice command is recognized to obtain the vehicle diagnostic request.

[0015] In one embodiment, the voice command is a preset voice command used to perform a full vehicle inspection, clear fault codes, or read any one of the data streams.

[0016] In one embodiment, the diagnostic instruction acquisition module is specifically used for: An encrypted communication tunnel is established between the relay server and the cloud diagnostic robot instance allocated by the cloud diagnostic system. The cloud diagnostic robot instance is determined by the cloud diagnostic system based on the vehicle identification code. The diagnostic instructions sent by the cloud-based diagnostic system are obtained through the encrypted communication tunnel.

[0017] In one embodiment, the response data sending module is further configured to: Obtain and output the diagnostic report generated by the cloud-based diagnostic system based on the diagnostic response data.

[0018] In one embodiment, the response data sending module is further configured to: Obtain the diagnostic report generated by the cloud-based diagnostic system based on the diagnostic response data; The diagnostic report will be read aloud.

[0019] A fourth aspect of this application provides a vehicle recorder, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the vehicle diagnostic method as described in the first aspect above.

[0020] A fifth aspect of this application provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the vehicle diagnostic method as described in the first aspect above.

[0021] A sixth aspect of this application provides a computer program product that, when run on a dashcam, causes the dashcam to perform the vehicle diagnostic method described in any one of the first aspects.

[0022] A seventh aspect of this application provides a vehicle diagnostic system, including: a dashcam, an on-board diagnostic system, and a cloud-based diagnostic system as described in the fourth aspect above.

[0023] The beneficial effects of this application embodiment compared with the prior art are as follows: the dashcam acts as a relay node between the vehicle diagnostic system and the cloud diagnostic system, uploading the vehicle diagnostic request and vehicle identification code to the cloud diagnostic system. The cloud diagnostic system generates diagnostic instructions and sends them to the vehicle diagnostic system, and then sends the diagnostic response data back to the cloud diagnostic system. This moves all the complex diagnostic protocol parsing and vehicle model adaptation logic to the cloud for execution, breaking through the limitations of the dashcam's local computing power and storage space. It can support in-depth diagnosis of the entire system of various mainstream vehicles without the need for a massive vehicle model diagnostic protocol library to be pre-installed locally. The diagnostic coverage capability is greatly improved compared with the solution of performing diagnosis locally. Attached Figure Description

[0024] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments or the prior art will be briefly introduced below.

[0025] Figure 1 This is a schematic diagram of a vehicle diagnostic system provided in one embodiment of this application; Figure 2 This is a schematic diagram illustrating the implementation flow of a vehicle diagnostic method provided in an embodiment of this application; Figure 3 This is a schematic diagram illustrating the implementation flow of a vehicle diagnostic method provided in another embodiment of this application; Figure 4 This is a schematic diagram of the structure of the dashcam provided in the embodiment of this application. Detailed Implementation

[0026] In the following description, specific details such as particular system architectures and techniques are set forth for illustrative purposes and not for limitation, in order to provide a thorough understanding of the embodiments of this application. However, those skilled in the art will understand that this application may also be implemented in other embodiments without these specific details. In other instances, detailed descriptions of well-known systems, apparatuses, circuits, and methods have been omitted so as not to obscure the description of this application with unnecessary detail.

[0027] It should be understood that, when used in this specification and the appended claims, the term "comprising" indicates the presence of the described features, integrals, steps, operations, elements and / or components, but does not exclude the presence or addition of one or more other features, integrals, steps, operations, elements, components and / or collections thereof.

[0028] It should also be understood that the terminology used in this specification is for the purpose of describing particular embodiments only and is not intended to limit the scope of the application. As used in this specification and the appended claims, the singular forms “a,” “an,” and “the” are intended to include the plural forms unless the context clearly indicates otherwise.

[0029] It should also be further understood that the term “and / or” as used in this application specification and the appended claims means any combination of one or more of the associated listed items and all possible combinations, and includes such combinations.

[0030] As used in this specification and the appended claims, the term "if" may be interpreted, depending on the context, as "when," "once," "in response to determination," or "in response to detection." Similarly, the phrases "if determined" or "if [described condition or event] is detected" may be interpreted, depending on the context, as "once determined," "in response to determination," "once [described condition or event] is detected," or "in response to detection of [described condition or event]."

[0031] like Figure 1 As shown, this application provides a vehicle diagnostic system, which includes a driving recorder 10, an on-board diagnostic system (OBD) 20, a cloud diagnostic system 30, a relay server 40, and a Golo platform 50.

[0032] The dashcam 10 communicates with the OBD 20 via a Universal Asynchronous Receiver / Transmitter (UART) serial port to achieve bidirectional transparent transmission of diagnostic commands and response data. The dashcam 10 also communicates with the Golo platform 50 via a socket connection. This socket connection uses a persistent connection mode, supporting heartbeat keep-alive and automatic reconnection after disconnection to ensure communication stability. The Golo platform 50 communicates with the cloud-based diagnostic system 30 to enable data forwarding between the cloud-based diagnostic system 30 and the dashcam 10.

[0033] The OBD 20 communicates with the vehicle's Electronic Control Unit (ECU) via the vehicle's OBD interface, supporting both CAN bus and K-line protocols to perform vehicle diagnostics based on the diagnostic instructions from the dashcam.

[0034] The cloud-based diagnostic system 30 includes a cloud-based diagnostic service platform, a cloud-based diagnostic robot pool, and a diagnostic report server. The cloud-based diagnostic service platform manages task queues, monitors the status of cloud-based diagnostic robots, authenticates devices, and queries the vehicle model database. It dynamically allocates idle cloud-based diagnostic robot instances from the pool based on the Vehicle Identification Number (VIN). Each cloud-based diagnostic robot instance includes an Android Application Package (APK), an Advanced Intelligent Technology (AIT) diagnostic engine, and a virtual B-end module, enabling the cloud-based diagnostic robot instances to function as local diagnostic devices. The APK application establishes a one-to-one exclusive secure link with the dashcam 10 via a relay server 40, thereby encrypting the transmission of diagnostic data. The AIT diagnostic engine loads the corresponding diagnostic protocol library based on the vehicle model information and generates a sequence of diagnostic instructions. The virtual B-end module converts the diagnostic instruction sequence output by the AIT diagnostic engine into data frames conforming to the dashcam's transparent transmission protocol. For example, the data frame format is: frame header (0xAA 0x55) + instruction code (1 byte) + data length (2 bytes) + data (N bytes) + checksum (1 byte, using XOR check). The diagnostic report server is used to store diagnostic reports generated by cloud-based diagnostic robot instances and pushes the diagnostic reports to the dashcam.

[0035] The vehicle diagnostic method provided in the embodiments of this application will be described below in conjunction with the above-mentioned vehicle diagnostic system.

[0036] like Figure 2As shown, a vehicle diagnostic method provided in one embodiment of this application is executed on a dashcam, including steps S201 to S206.

[0037] S201: Obtain vehicle diagnostic request.

[0038] In one embodiment, the dashcam's microphone collects voice commands, recognizes the voice commands, and obtains a vehicle diagnostic request.

[0039] For example, when a car owner issues a voice command (such as "I want a full vehicle inspection"), the dashcam's microphone picks up the command, calls the voice recognition module to recognize it, obtains the recognized text, and maps the text to a vehicle diagnostic request. The voice recognition module can use an offline voice recognition engine, completing recognition locally without a network connection, ensuring high availability of the voice-triggered function. Alternatively, the voice recognition module can combine offline and online voice recognition engines, prioritizing the offline engine for voice recognition. When the recognition confidence falls below a preset threshold (e.g., 0.8), it switches to the online voice recognition engine for secondary recognition, improving accuracy in complex voice environments.

[0040] In the above embodiments, vehicle diagnostic requests are triggered by voice commands. Users only need to issue a voice command to start the diagnostic process without manual operation, thus avoiding the safety risks caused by manual operation during driving.

[0041] In one embodiment, the voice command is a preset voice command used for performing a full vehicle check, clearing fault codes, or reading a data stream. Diagnostic requests can be determined through voice matching, improving the response speed of vehicle diagnostics. Specifically, the voice command for performing a full vehicle check could be "Full Vehicle Check," which triggers the reading of diagnostic fault codes from modules such as the Engine Control Module (ECM), Transmission Control Module (TCM), Anti-lock Braking System (ABS) control module, and Supplemental Restraint System (SRS) control module. The voice command for clearing fault codes could be "Clear Fault Codes," which triggers the clearing of already read diagnostic fault codes. The voice command for reading a data stream could be "Read Data Stream," which triggers the continuous acquisition of real-time vehicle operating parameters (such as engine speed, coolant temperature, intake pressure, throttle opening, etc.).

[0042] In another embodiment, the dashcam can also receive vehicle diagnostic requests input by the user through the dashcam's client.

[0043] S202: Send the vehicle diagnostic request and vehicle identification code to the cloud diagnostic system.

[0044] In one embodiment, the dashcam sends a vehicle diagnostic request and the Vehicle Identification Number (VIN) to a cloud-based diagnostic system via the Golo platform.

[0045] Specifically, after receiving a vehicle diagnostic request, the dashcam reads the vehicle's VIN code via OBD, encapsulates the diagnostic request and VIN code into a JSON-formatted data packet, and sends the data packet to the Golo platform client installed on the dashcam via a Socket connection. Upon receiving the data packet from the dashcam, the Golo platform first performs device authentication, such as verifying the dashcam's device ID and digital certificate validity. If authentication fails, vehicle diagnostics are refused. If authentication succeeds, the Golo platform uploads the data packet to the optimal cloud diagnostic system node based on device binding relationships and load balancing strategies. The Golo platform also logs the diagnostic request, including the request timestamp, dashcam's device ID, VIN code, diagnostic type, and other information, for subsequent distribution of the diagnostic report.

[0046] S203: Obtain the diagnostic command sent by the cloud diagnostic system, the diagnostic command being generated by the cloud diagnostic system based on the vehicle identification code.

[0047] Specifically, after receiving a vehicle diagnostic request, the cloud-based diagnostic system queries the vehicle model database based on the VIN code to determine the vehicle's brand, model, year, engine model, transmission type, and other vehicle information. It then selects available cloud-based diagnostic robot instances from the diagnostic robot pool that support the vehicle model information and sorts them according to their current load. For example, the current load is represented by a comprehensive load score, calculated as: Comprehensive Load Score = CPU Utilization × 0.4 + Memory Utilization × 0.3 + Current Number of Tasks × 0.3. Based on the comprehensive load scores, from lowest to highest, the cloud-based diagnostic system assigns the cloud-based diagnostic robot instance with the lowest comprehensive load score to execute the vehicle diagnostic task, achieving dynamic scheduling of diagnostic resources.

[0048] Among them, the cloud-based diagnostic robot instance is a process running on a cloud-based diagnostic system and has the functions of a local diagnostic device.

[0049] After identifying the cloud-based diagnostic robot instance, the instance initiates a connection request to the relay server. Simultaneously, the relay server receives a connection request from the dashcam, establishing a one-to-one encrypted communication tunnel between the cloud-based diagnostic robot instance and the dashcam. For example, the encrypted communication tunnel employs Transport Layer Security (TLS) encryption, uses the Elliptic Curve Diffie-Hellman (ECDH) key exchange algorithm to negotiate the session key, and employs Advanced Encryption Standard (AES) to encrypt data transmission, enhancing data transmission security. Furthermore, the one-to-one encrypted communication tunnel prevents the mixing of diagnostic data from different vehicles, ensuring the accuracy of diagnostic results. Subsequently, the cloud-based diagnostic robot instance calls the diagnostic software to parse the vehicle model information and generates diagnostic instructions based on the parsed information. The dashcam then receives these diagnostic instructions from the cloud-based diagnostic robot instance through the encrypted communication tunnel.

[0050] In one embodiment, the cloud-based diagnostic system can also cache vehicle model information corresponding to the VIN code based on historical diagnostic records. Upon receiving a vehicle diagnostic request, it first checks whether the vehicle model information corresponding to the VIN code exists in the cached records. If it does, the vehicle model information is retrieved directly; otherwise, the vehicle model database is queried, thereby improving the response speed of vehicle diagnostics.

[0051] S204: Send the diagnostic command to the vehicle diagnostic system.

[0052] Specifically, the dashcam transmits diagnostic commands to the OBD via a UART serial port. This transparent transmission reduces the time the dashcam spends parsing these commands, improving vehicle diagnostic efficiency. Furthermore, the dashcam doesn't need complex built-in diagnostic protocol parsing logic, lowering the requirements for local computing power and storage space. Simultaneously, when the cloud-based diagnostic system is updated, the dashcam is compatible with the updated system without any software upgrades, ensuring the real-time nature of diagnostic commands and meeting the needs of real-time vehicle diagnostics.

[0053] S205: Obtain the vehicle diagnostic response data sent by the on-board diagnostic system.

[0054] Specifically, after receiving a diagnostic command, the OBD system converts the command into a vehicle bus signal conforming to the vehicle's ECU communication protocol and sends it to the ECU. It then encapsulates the bus response data returned by the ECU to obtain diagnostic response data, which is transmitted back to the dashcam via the UART serial port. The diagnostic response data includes a list of diagnostic fault codes, data stream values, and operation execution results.

[0055] S206: Send the diagnostic response data to the cloud diagnostic system.

[0056] Specifically, the dashcam sends diagnostic response data to a cloud-based diagnostic robot instance in the cloud diagnostic system via a Socket connection. The cloud-based diagnostic robot instance then generates a diagnostic report based on the diagnostic response data.

[0057] In one embodiment, a cloud-based diagnostic robot instance parses diagnostic response data to obtain a diagnostic report. For example, it parses diagnostic fault codes to obtain fault details; it parses data stream values ​​to obtain parameter values ​​such as engine speed, coolant temperature, intake pressure, and throttle opening, and determines whether the parameter values ​​are abnormal.

[0058] In one embodiment, the cloud-based diagnostic robot instance can also input diagnostic response data into a preset diagnostic model to obtain a diagnostic report output by the diagnostic model. The diagnostic report may include information such as diagnostic fault code number, fault description, fault status, abnormal parameters, and fault level (e.g., severe, moderate, minor).

[0059] In one embodiment, the cloud-based diagnostic robot instance can also determine maintenance recommendations based on the analysis results of the diagnostic response data and add these recommendations to the diagnostic report. For example, maintenance recommendations might include replacing the oxygen sensor, checking the intake system's sealing, or cleaning the throttle body.

[0060] After generating a diagnostic report, the cloud-based diagnostic system sends the report to the dashcam. For example, the cloud-based diagnostic system sends the report to the dashcam's client via the Golo platform for user viewing.

[0061] In one embodiment, the cloud-based diagnostic system can also generate a summary of the diagnostic report based on the diagnostic report, and send the summary to the dashcam. The dashcam is equipped with a speaker, which, upon receiving the summary, converts it into speech and reads it aloud. For example, the voice announcement might say, "Detection complete. Two fault codes were found, one of which is a serious fault. Please check the mobile app for details." Through voice announcements, users can instantly obtain information about the vehicle's health status without needing to check their phones, thus improving the safety of vehicle diagnostics while driving.

[0062] In one embodiment, the dashcam can also receive scheduled diagnostic tasks pushed by the cloud-based diagnostic system through the Golo platform, enabling regular automatic checks of the vehicle's health status (such as automatically triggering a full vehicle check after each day's driving), without requiring manual initiation by the user, further improving the automation level of the diagnostics. Scheduled diagnostic tasks can be automatically triggered according to user-defined time rules (such as 10:00 PM every night, 10:00 AM every Sunday, etc.). After receiving the scheduled task, the dashcam executes the diagnostic process through the cloud-based diagnostic system and receives the diagnostic report pushed by the system.

[0063] In the above embodiments, the dashcam acts as a relay node, sending diagnostic commands from the cloud-based diagnostic system to the vehicle-mounted diagnostic system and sending the diagnostic response data returned by the vehicle-mounted diagnostic system to the cloud-based diagnostic system. This moves all diagnostic logic and protocol parsing to the cloud, breaking through local computing power and storage limitations. It can support in-depth diagnostics of all vehicle models and systems, reducing hardware costs. Furthermore, the dashcam can automatically support new vehicle models without firmware upgrades, reducing dashcam maintenance costs.

[0064] like Figure 3 As shown, a vehicle diagnostic method provided in one embodiment of this application includes steps S301 to S305.

[0065] S301: The dashcam obtains a vehicle diagnostic request and sends the vehicle diagnostic request and vehicle identification code to the cloud diagnostic system.

[0066] Specifically, the dashcam recognizes the acquired voice commands or obtains vehicle diagnostic requests based on client input information, and simultaneously obtains the VIN code through OBD, sending the vehicle diagnostic request and VIN code to the cloud diagnostic system.

[0067] In one embodiment, the dashcam acquires a vehicle diagnostic request and sends the request and vehicle identification number (VIN) to a cloud-based diagnostic system via the Golo platform. Exemplarily, the Golo platform client on the dashcam encapsulates the vehicle diagnostic request and VIN into a data packet and uploads it to the Golo platform via a socket connection. The Golo platform verifies the legitimacy of the dashcam's device ID and digital certificate. If verification fails, vehicle diagnostics are refused; if verification succeeds, the vehicle diagnostic request and VIN are sent to the cloud-based diagnostic system, ensuring system security. The dashcam also records log information such as the timestamp of the vehicle diagnostic request, device ID, VIN, and diagnostic type, providing data for subsequent diagnostic reports.

[0068] The dashcam sends vehicle diagnostic requests and vehicle identification numbers to the cloud-based diagnostic system via the Golo platform. This allows the Golo platform to act as a unified access layer for all dashcams, managing their access and message routing. As the number of dashcams connected to the Golo platform increases, the platform can horizontally scale to add service nodes without requiring downtime for maintenance, thus enhancing system scalability.

[0069] S302: The cloud-based diagnostic system generates diagnostic instructions based on the vehicle identification code and sends the diagnostic instructions to the dashcam.

[0070] Specifically, after receiving the vehicle diagnostic request and VIN code forwarded by the Golo platform, the cloud-based diagnostic system parses the VIN code to obtain vehicle information, calls the vehicle model database to query the vehicle brand, model, year, engine model, transmission type, and other vehicle information corresponding to the VIN code, generates diagnostic instructions corresponding to the vehicle model information, and sends them to the dashcam.

[0071] In one embodiment, the cloud-based diagnostic system allocates a cloud-based diagnostic robot instance to the VIN code based on the vehicle diagnostic request. Specifically, the cloud-based diagnostic system determines the vehicle model information based on the VIN code, filters cloud-based diagnostic robot instances that support the vehicle model information from the diagnostic robot pool, and then selects the cloud-based diagnostic robot instance with the lowest determined load from the cloud-based diagnostic robot instances that support the vehicle model information. This cloud-based diagnostic robot instance is then bound to the dashcam for vehicle diagnostics. By dynamically allocating cloud-based diagnostic robot instances, the resource waste caused by some cloud-based diagnostic robot instances being overloaded while others are idle is avoided, thus improving the system's concurrent processing capability and resource utilization efficiency.

[0072] After binding the cloud diagnostic robot instance to the dashcam, the cloud diagnostic robot instance initiates a connection request to the relay server. The relay server simultaneously accepts connection requests from the dashcam, establishing a one-to-one encrypted communication tunnel between the cloud diagnostic robot instance and the dashcam. This ensures that diagnostic data from different vehicles are isolated from each other, preventing data confusion and leakage.

[0073] After establishing an encrypted communication tunnel, the cloud-based diagnostic robot instance loads the corresponding diagnostic protocol library based on the vehicle model information, generates diagnostic instructions, and sends the diagnostic instructions to the dashcam.

[0074] S303: The dashcam sends the diagnostic command to the vehicle diagnostic system.

[0075] Specifically, after receiving diagnostic commands from the cloud-based diagnostic robot via an encrypted communication tunnel, the dashcam forwards the commands to the OBD connector via the UART serial port. Therefore, the dashcam only forwards diagnostic data without performing data parsing, eliminating the need for a built-in vehicle diagnostic protocol library, thus reducing development complexity and maintenance costs.

[0076] S304: The vehicle recorder acquires the vehicle diagnostic response data sent by the on-board diagnostic system.

[0077] Specifically, after receiving a diagnostic command, the OBD parses the command, extracts its content, and sends it to the vehicle's ECU. Upon receiving the command, the ECU executes the corresponding diagnostic operation and sends the diagnostic response data back to the OBD. The OBD encapsulates the diagnostic response data into a transparent data frame (frame header + response code + data length + response data + checksum) and transmits it back to the dashcam via the UART serial port.

[0078] S305: The vehicle recorder sends the diagnostic response data to the cloud diagnostic system.

[0079] Specifically, the dashcam sends diagnostic response data to a cloud-based diagnostic robot instance via an encrypted communication tunnel, and the cloud-based diagnostic robot instance generates a diagnostic report based on the diagnostic response data.

[0080] After receiving the diagnostic report, the cloud-based diagnostic system sends the report to the dashcam or pushes it to the Golo platform client or a third-party client via the Golo platform. Once the dashcam receives the diagnostic report, it can either read it aloud via voice or display it on the dashcam client.

[0081] In this embodiment, the user only needs to input a voice command, and the dashcam can complete the vehicle diagnostic request triggering and interaction with the cloud diagnostic system, and obtain the vehicle diagnostic report generated by the cloud diagnostic system based on the diagnostic response data, without any manual operation, thus improving the convenience of vehicle diagnostics and driving safety.

[0082] It should be understood that the sequence number of each step in the above embodiments does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0083] Figure 4 This is a schematic diagram of the structure of the dashcam provided in the embodiment of this application.

[0084] like Figure 4As shown, the dashcam in this embodiment includes a processor 11, a memory 12, and a computer program 13 stored in the memory 12 and executable on the processor 11. When the processor 11 executes the computer program 13, it implements the steps described in the vehicle diagnostic method embodiment above, for example... Figure 1 Steps S201 to S206 are shown.

[0085] For example, the computer program 13 may be divided into one or more modules / units, which are stored in the memory 12 and executed by the processor 11 to complete this application. The one or more modules / units may be a series of computer program instruction segments capable of performing specific functions, which describe the execution process of the computer program 13 in the dashcam.

[0086] Those skilled in the art will understand that Figure 4 This is merely an example of a dashcam and does not constitute a limitation on dashcams. It may include more or fewer components than shown, or combine certain components, or different components. For example, the dashcam may also include input / output devices, network access devices, buses, etc.

[0087] The processor 11 can be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor can be a microprocessor or any conventional processor.

[0088] The memory 12 can be an internal storage unit of the dash cam, such as the dash cam's hard drive or RAM. The memory 12 can also be an external storage device of the dash cam, such as a plug-in hard drive, Smart Media Card (SMC), Secure Digital (SD) card, or Flash Card. Furthermore, the memory 12 can include both internal and external storage units of the dash cam. The memory 12 is used to store the computer program and other programs and data required by the dash cam. The memory 12 can also be used to temporarily store data that has been output or will be output.

[0089] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the above-described division of functional units and modules is merely an example. In practical applications, the above functions can be assigned to different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above. The functional units and modules in the embodiments can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit. Furthermore, the specific names of the functional units and modules are only for easy differentiation and are not intended to limit the scope of protection of this application. The specific working process of the units and modules in the above system can be referred to the corresponding process in the foregoing method embodiments, and will not be repeated here.

[0090] In the above embodiments, the descriptions of each embodiment have different focuses. For parts that are not described in detail or recorded in a certain embodiment, please refer to the relevant descriptions of other embodiments.

[0091] In the embodiments provided in this application, it should be understood that the disclosed device / dashcam and method can be implemented in other ways. For example, the device / dashcam embodiments described above are merely illustrative. For instance, the division of modules or units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the displayed or discussed mutual coupling or direct coupling or communication connection may be through some interfaces; the indirect coupling or communication connection between devices or units may be electrical, mechanical, or other forms.

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

[0093] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0094] If an integrated module / unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, all or part of the processes in the methods of the above embodiments can also be implemented by a computer program instructing related hardware. The computer program can be stored in a computer-readable storage medium, and when executed by a processor, it can implement the steps of the various method embodiments described above. The computer program includes computer program code, which can be in the form of source code, object code, executable files, or certain intermediate forms. The computer-readable medium can include: any entity or device capable of carrying the computer program code, a recording medium, a USB flash drive, a portable hard drive, a magnetic disk, an optical disk, a computer memory, a read-only memory (ROM), a random access memory (RAM), an electrical carrier signal, a telecommunication signal, and a software distribution medium, etc.

[0095] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0096] The above-described embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application, and should all be included within the protection scope of this application.

Claims

1. A vehicle diagnostic method, characterized in that, Execution in dashcams, including: Obtain vehicle diagnostic request; Send the vehicle diagnostic request and vehicle identification number to the cloud diagnostic system; Obtain diagnostic instructions sent by the cloud-based diagnostic system, which are generated by the cloud-based diagnostic system based on the vehicle identification code; The diagnostic command is sent to the on-board diagnostic system; Obtain the vehicle's diagnostic response data sent by the on-board diagnostic system; The diagnostic response data is sent to the cloud-based diagnostic system.

2. The vehicle diagnostic method according to claim 1, characterized in that, Obtain vehicle diagnostic requests, including: Get voice commands; The voice command is recognized to obtain the vehicle diagnostic request.

3. The vehicle diagnostic method according to claim 2, characterized in that, The voice commands are preset voice commands used for performing a full vehicle inspection, clearing fault codes, or reading any one of the data streams.

4. The vehicle diagnostic method according to claim 1, characterized in that, Obtaining diagnostic instructions sent by the cloud-based diagnostic system includes: An encrypted communication tunnel is established between the relay server and the cloud diagnostic robot instance allocated by the cloud diagnostic system. The cloud diagnostic robot instance is determined by the cloud diagnostic system based on the vehicle identification code. The diagnostic instructions sent by the cloud-based diagnostic system are obtained through the encrypted communication tunnel.

5. The vehicle diagnostic method according to claim 1, characterized in that, After sending the diagnostic response data to the cloud-based diagnostic system, the process also includes: Obtain and output the diagnostic report generated by the cloud-based diagnostic system based on the diagnostic response data.

6. The vehicle diagnostic method according to claim 5, characterized in that, Obtain and output the diagnostic report generated by the cloud-based diagnostic system based on the diagnostic response data, including: Obtain the diagnostic report generated by the cloud-based diagnostic system based on the diagnostic response data; The diagnostic report will be read aloud.

7. A vehicle diagnostic method, characterized in that, include: The dashcam acquires a vehicle diagnostic request and sends the vehicle diagnostic request and vehicle identification number to the cloud diagnostic system. The cloud-based diagnostic system generates diagnostic instructions based on the vehicle identification code and sends the diagnostic instructions to the dashcam. The dashcam sends the diagnostic command to the vehicle diagnostic system; The dashcam acquires the vehicle's diagnostic response data sent by the on-board diagnostic system; The dashcam sends the diagnostic response data to the cloud-based diagnostic system.

8. The method according to claim 7, characterized in that, The cloud-based diagnostic system generates diagnostic instructions based on the vehicle diagnostic request and the vehicle identification number, and sends the diagnostic instructions to the dashcam, including: The cloud diagnostic system allocates a cloud diagnostic robot instance to the vehicle identification code according to the vehicle diagnostic request, and enables the cloud diagnostic robot instance to establish an encrypted communication tunnel with the dashcam through a relay server. The diagnostic command is sent to the vehicle recorder through the encrypted communication tunnel.

9. The method according to claim 7, characterized in that, The dashcam acquires a vehicle diagnostic request and sends the vehicle request and vehicle identification number to the cloud diagnostic system, including: The dashcam acquires a vehicle diagnostic request and sends the vehicle diagnostic request and the vehicle identification code to the cloud diagnostic system through the Golo platform.

10. A dashcam, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the method as described in any one of claims 1 to 6.

Images