Vehicle cloud communication system, method and device for collecting vehicle data based on diagnosis model, and storage medium

Abstract

The invention discloses a vehicle cloud communication system, method and device for collecting whole vehicle data based on a diagnosis model and a storage medium, and belongs to the technical field of automotive electronics and Internet of Vehicles communication, and the system comprises a central gateway arranged at a vehicle end and a remote server at a cloud end. The central gateway and the remote server are connected and communicate with each other through a vehicle cloud communication protocol; the central gateway comprises a gateway module and a communication module, and the gateway module is configured to have gateway functions of a controller local area network, a local internet and an Ethernet and is used for routing and acquiring full-quantity network data of the electronic control unit of the whole vehicle; and the communication module is in communication connection with the gateway module and is used for sending the data acquired by the gateway module to the remote server through a transmission protocol. According to the method, the problems of inflexible data acquisition, key data loss or large transmission redundancy in the prior art are effectively solved, accurate, timely and automatic reporting of fault data is realized, the problem diagnosis efficiency is remarkably improved, and network and cloud resources are saved.

Description

Technical Field

[0001] This invention belongs to the field of automotive electronics and vehicle networking communication technology, specifically relating to a vehicle-to-cloud communication system, method, device, and storage medium for collecting vehicle data based on a diagnostic model. Background Technology

[0002] In existing technologies, the collection of vehicle condition data typically relies on the cooperation between the vehicle's telematics unit (TBOX) and the cloud-based vehicle service platform (TSP). The TBOX is responsible for collecting vehicle data and transmitting it to the TSP via network protocols, allowing users to remotely view vehicle information and enabling automakers to troubleshoot problems and predict faults.

[0003] However, existing data acquisition methods have significant drawbacks. TBOX typically only collects certain frequently used data or performs full-scale vehicle-side data collection. When errors occur during production line or remote diagnostics, the corresponding diagnostic data cannot be uploaded immediately. Often, it's necessary to redeploy the configuration from the cloud to modify the collection method, and data collection can only resume after the problem is reproduced. If the problem cannot be reproduced, critical data will be lost. On the other hand, using a full-scale collection method generates massive amounts of data, leading to long transmission times, susceptibility to network conditions causing packet loss, and consuming significant cloud storage and computing resources.

[0004] In addition, existing research focuses on driving vehicle-side data collection tasks through cloud configuration. This approach has a delay in taking effect and cannot fundamentally solve the problems of timeliness, accuracy, and efficiency in data collection. Summary of the Invention

[0005] The purpose of this invention is to overcome the shortcomings of the prior art and provide a vehicle-to-cloud communication system, method, device, and storage medium for collecting vehicle data based on a diagnostic model. This enables the system to adaptively configure the collected information according to the diagnostic model after vehicle diagnosis, ensuring that the required vehicle condition information can be uploaded to the cloud computing center in real time and accurately. This achieves timely and correct data upload, accurate data acquisition, less redundant data, facilitates rapid problem location, improves problem-solving speed, and reduces unnecessary resource consumption in the cloud.

[0006] This invention is achieved through the following technical solution:

[0007] In a first aspect, the present invention provides a vehicle-to-cloud communication system for collecting vehicle data based on a diagnostic model, comprising a central gateway (CGW) located on the vehicle and a remote server (TSP) in the cloud. The central gateway and the remote server establish a connection and communicate with each other through a vehicle-to-cloud communication protocol. The central gateway includes a gateway module and a communication module. The gateway module is configured to have gateway functions for Controller Area Network (CAN), Local Area Network (LIN), and Ethernet, and is used to route and acquire full network data of the vehicle's electronic control unit (ECU). The communication module is communicatively connected to the gateway module and is used to send the data acquired by the gateway module to the remote server through a transmission protocol.

[0008] Furthermore, the central gateway is equipped with a diagnostic model, which includes data acquisition rules associated with multiple error codes; each error code is associated with a corresponding ECU, diagnostic identifier (DID), error type, associated diagnostic message, and associated application message;

[0009] The central gateway is used to identify errors issued by the ECU during production line diagnosis or remote diagnosis, query the diagnostic model based on the identified error, determine the corresponding error code and the associated diagnostic message and application message associated with the error code, and control the communication module to upload the determined associated message data to the remote server.

[0010] Furthermore, the central gateway is also used to resend historical associated message data within a certain time window when uploading associated message data.

[0011] Furthermore, the remote server is used to automatically parse the received associated message data and directly output the parsed signal value or version information.

[0012] Secondly, the present invention provides a method for collecting vehicle data in a vehicle-to-cloud communication system based on a diagnostic model, specifically including the following steps:

[0013] S1. Configure a diagnostic model in the central gateway on the vehicle side. The diagnostic model contains data acquisition rules associated with multiple error codes. Each error code is associated with a corresponding ECU, DID, error type, associated diagnostic message, and associated application message.

[0014] S2. During production line diagnostics or remote diagnostics, the central gateway identifies errors issued by the ECU.

[0015] S3. Based on the identified errors, query the diagnostic model to determine the corresponding error code and the associated diagnostic message and application message associated with that error code;

[0016] S4. The central gateway uploads the identified associated message data to the remote cloud server.

[0017] Furthermore, in step S1, the diagnostic model is classified according to different ECUs and a basic status message is bound to each type of ECU; a corresponding error code is established for the DID and possible error types of each ECU; and the relevant diagnostic messages and application messages required to troubleshoot each error are associated with the corresponding error code.

[0018] Furthermore, in step S4, when the central gateway uploads the current associated message data, it also re-uploads the historical associated message data within the previous time window.

[0019] Furthermore, in step S4, the remote server automatically parses the received associated message data and outputs the parsed signal value or version information.

[0020] Thirdly, the present invention also provides a computer device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement a vehicle-to-cloud communication system for collecting vehicle data based on a diagnostic model as described in any of the present invention.

[0021] Fourthly, the present invention also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements a vehicle-to-cloud communication system for collecting vehicle data based on a diagnostic model as described in any of the present invention.

[0022] Compared with the prior art, the advantages of the present invention are as follows:

[0023] 1. Through the pre-set diagnostic model, when a specific fault is detected, it can automatically and accurately associate and upload the diagnostic message and application message data necessary for troubleshooting the fault, avoiding data redundancy caused by full data collection;

[0024] 2. When a fault occurs, the relevant data can be uploaded immediately, and historical data can be resent, ensuring that critical data is not lost and greatly improving the timeliness and accuracy of problem analysis;

[0025] 3. The cloud can automatically parse uploaded messages and quickly output information that can be directly used for analysis, further accelerating the speed of problem location and resolution. Attached Figure Description

[0026] To more clearly illustrate the specific embodiments of the present invention or the technical solutions in the prior art, the accompanying drawings used in the description of the specific embodiments or the prior art will be briefly introduced below. In all the drawings, similar elements or parts are generally identified by similar reference numerals. In the drawings, the elements or parts are not necessarily drawn to scale.

[0027] Figure 1 This is a schematic diagram of the system structure of a vehicle-to-cloud communication system for collecting vehicle data based on a diagnostic model, according to the present invention.

[0028] Figure 2 This is a schematic diagram illustrating the principle of a vehicle-to-cloud communication system for collecting vehicle data based on a diagnostic model, according to the present invention.

[0029] Figure 3 This is a flowchart illustrating the data acquisition method of a vehicle-to-cloud communication system based on a diagnostic model for acquiring vehicle data, according to the present invention.

[0030] Figure 4 This is a schematic diagram of the structure of an electronic device according to Embodiment 3 of the present invention. Detailed Implementation

[0031] To clearly and completely describe the technical solution and its specific working process of the present invention, the specific embodiments of the present invention are as follows, in conjunction with the accompanying drawings:

[0032] In this invention, unless otherwise explicitly specified and limited, the terms "installation," "connection," "linking," and "fixing," etc., should be interpreted broadly. For example, they can refer to a fixed connection, a detachable connection, or an integral part; they can refer to a mechanical connection or an electrical connection; they can refer to a direct connection or an indirect connection through an intermediate medium; they can refer to the internal communication of two components or the interaction between two components, unless otherwise explicitly limited. Those skilled in the art can understand the specific meaning of the above terms in this invention according to the specific circumstances.

[0033] In this invention, unless otherwise explicitly specified and limited, "above" or "below" the second feature can mean that the first feature is in direct contact with the second feature, or that the first feature is in indirect contact with the second feature through an intermediate medium. Furthermore, "above," "over," and "on top" of the second feature can mean that the first feature is directly above or diagonally above the second feature, or simply that the first feature is at a higher horizontal level than the second feature. "Below," "below," and "under" the second feature can mean that the first feature is directly below or diagonally below the second feature, or simply that the first feature is at a lower horizontal level than the second feature.

[0034] In the description of this specification, the references to terms such as "one embodiment," "some embodiments," "example," "specific example," or "some examples," etc., indicate that a specific feature, structure, material, or characteristic described in connection with that embodiment or example is included in at least one embodiment or example of the present invention. In this specification, the illustrative expressions of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in one or more embodiments or examples. Moreover, without contradiction, those skilled in the art can combine and integrate the different embodiments or examples described in this specification, as well as the features of different embodiments or examples.

[0035] Example 1

[0036] refer to Figure 1 This embodiment provides a vehicle-to-cloud communication system for collecting vehicle data based on a diagnostic model. It includes a central gateway (CGW) located in the vehicle and a remote server (TSP) in the cloud. The central gateway and the remote server establish a connection and communicate via a vehicle-to-cloud communication protocol. The central gateway includes a gateway module and a communication module. The gateway module is configured to have gateway functions for Controller Area Network (CAN), Local Area Network (LIN), and Ethernet, used for routing and acquiring full network data from the vehicle's electronic control unit (ECU). The communication module is communicatively connected to the gateway module and is used to send the data acquired by the gateway module to the remote server via a transmission protocol.

[0037] The central gateway is equipped with a diagnostic model, which includes data acquisition rules associated with multiple error codes; each error code is associated with a corresponding ECU, diagnostic identifier (DID), error type, associated diagnostic message, and associated application message;

[0038] The central gateway is used to identify errors issued by the ECU during production line diagnosis or remote diagnosis, query the diagnostic model based on the identified error, determine the corresponding error code and the associated diagnostic message and application message associated with the error code, and control the communication module to upload the determined associated message data to the remote server.

[0039] In this embodiment, the vehicle-side hardware adopts an S32G3 + AG35 solution. The S32G3 acts as the central gateway (CGW), utilizing its CAN and LIN resources and hard routing capabilities to implement CAN / LIN gateway functionality, and its internal PFE softswitch capability to implement Ethernet gateway functionality, thereby acquiring all CAN, LIN, and Ethernet data from the entire vehicle. The S32G3 transmits this data to the AG35 communication module via the SPI interface. The AG35 module is responsible for sending the vehicle status data that needs to be uploaded to the cloud-based TSP server via mobile network and other transmission protocols.

[0040] The diagnostic model is pre-stored in the CGW in the form of an encoding table; for example, an example of an error encoding is shown in Table 1.

[0041] Table 1 Examples of Error Codes

[0042] Error Code 0x001 ECU Vehicle controller DID 19 02 08 Error Type No response Related diagnostic messages 0x75X, 0x76X Related application messages 0x101, 0x102, 0x103

[0043] The process of establishing this diagnostic model includes: First, ECUs are classified according to different types, with each type of ECU fixedly bound to its basic status message. Then, for each ECU's supported DIDs and their possible error contents (such as no response, incorrect response content, negative response, Diagnostic Trouble Code (DTC), etc.), a corresponding error code is established. Finally, the relevant diagnostic and application messages needed to troubleshoot this problem are associated with this error code.

[0044] Example 2

[0045] See Figure 2 and Figure 3 This embodiment provides a data acquisition method for a vehicle-to-cloud communication system based on a diagnostic model, which includes the following steps:

[0046] S1. Configure a diagnostic model in the central gateway on the vehicle side. The diagnostic model contains data acquisition rules associated with multiple error codes. Each error code is associated with a corresponding ECU, DID, error type, associated diagnostic message, and associated application message.

[0047] S2. During production line diagnostics or remote diagnostics, the central gateway identifies errors issued by the ECU.

[0048] S3. Based on the identified errors, query the diagnostic model to determine the corresponding error code and the associated diagnostic message and application message associated with that error code;

[0049] S4. The central gateway uploads the identified associated message data to the remote cloud server.

[0050] During production line diagnostics or remote diagnostics, the CGW monitors the responses of each ECU. For example, if no response is received after sending a command with DID 19 02 08 to the vehicle controller, the CGW identifies the error. The CGW then queries the diagnostic model, matches the error code 0x001, and retrieves its associated diagnostic messages (ID=0x75X, 0x76X) and application messages (ID=0x101, 0x102, 0x103, etc.). The CGW controls the AG35 module to upload the associated message data (0x100, 0x75X, 0x76X, 0x101, 0x102, 0x103) to the cloud-based TSP. Simultaneously, the CGW can retrieve historical data of these messages from a previously cached period (e.g., 5 minutes) and resend them. After receiving data, the cloud-based TSP can automatically parse application messages using preset parsing rules (such as DBC files), directly outputting the actual physical value of the signal, or parse diagnostic messages to obtain information such as the ECU version number, for technicians to analyze quickly.

[0051] This system and method enable CGW to report relevant data information and upload historical data when an error is detected during production line diagnostic testing or remote diagnostic testing. This improves the efficiency of problem analysis and resolution, and reduces data transmission volume and increases transmission rate by not uploading useless data, thus saving bandwidth costs.

[0052] Example 3

[0053] Figure 4 This is a schematic diagram of the structure of a computer device in Embodiment 3 of the present invention. Figure 4 A block diagram of an exemplary computer device 12 suitable for implementing embodiments of the present invention is shown. Figure 4 The computer device 12 shown is merely an example and should not impose any limitation on the functionality and scope of use of the embodiments of the present invention.

[0054] like Figure 4 As shown, the computer device 12 is represented in the form of a general-purpose computing device. The components of the computer device 12 may include, but are not limited to: one or more processors or processing units 16, system memory 28, and bus 18 connecting different system components (including system memory 28 and processing unit 16).

[0055] Bus 18 represents one or more of several bus architectures, including a memory bus or memory controller, a peripheral bus, a graphics acceleration port, a processor, or a local bus using any of the various bus architectures. For example, these architectures include, but are not limited to, the Industry Standard Architecture (ISA) bus, the Micro Channel Architecture (MAC) bus, the Enhanced ISA bus, the Video Electronics Standards Association (VESA) local bus, and the Peripheral Component Interconnect (PCI) bus.

[0056] Computer device 12 typically includes a variety of computer system readable media. These media can be any available media that can be accessed by computer device 12, including volatile and non-volatile media, removable and non-removable media.

[0057] System memory 28 may include computer system readable media in the form of volatile memory, such as random access memory (RAM) 30 and / or cache memory 32. Computer device 12 may further include other removable / non-removable, volatile / non-volatile computer system storage media. By way of example only, storage system 34 may be used to read and write non-removable, non-volatile magnetic media (…). Figure 4 Not shown; usually referred to as a "hard drive"). Although Figure 4 Not shown, a disk drive for reading and writing to a removable non-volatile disk (e.g., a "floppy disk") and an optical disk drive for reading and writing to a removable non-volatile optical disk (e.g., a CD-ROM, DVD-ROM, or other optical media) may be provided. In these cases, each drive may be connected to bus 18 via one or more data media interfaces. Memory 28 may include at least one program product having a set (e.g., at least one) of program modules configured to perform the functions of the embodiments of the present invention.

[0058] A program / utility 40 having a set (at least one) of program modules 42 may be stored, for example, in memory 28. Such program modules 42 include—but are not limited to—an operating system, one or more application programs, other program modules, and program data. Each or some combination of these examples may include an implementation of a network environment. Program modules 42 typically perform the functions and / or methods described in the embodiments of the present invention.

[0059] The computer device 12 can also communicate with one or more external devices 14 (e.g., keyboard, pointing device, display 24, etc.), and with one or more devices that enable a user to interact with the computer device 12, and / or with any device that enables the computer device 12 to communicate with one or more other computing devices (e.g., network card, modem, etc.). This communication can be performed via the input / output (I / O) interface 22. Furthermore, in this embodiment, the display 24 of the computer device 12 is not an independent entity, but is embedded in a mirror, so that when the display surface of the display 24 is not displayed, the display surface of the display 24 and the mirror surface visually blend together. Moreover, the computer device 12 can also communicate with one or more networks (e.g., local area network (LAN), wide area network (WAN), and / or public networks, such as the Internet) via the network adapter 20. As shown, the network adapter 20 communicates with other modules of the computer device 12 via the bus 18. It should be understood that, although not shown in the figure, other hardware and / or software modules may be used in conjunction with computer device 12, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems.

[0060] The processing unit 16 executes various functional applications and data processing by running programs stored in the system memory 28, such as implementing a method for reducing vehicle weight provided in an embodiment of the present invention.

[0061] Example 4

[0062] Embodiment 4 of the present invention provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the vehicle noise reduction method provided in all embodiments of the present application.

[0063] Any combination of one or more computer-readable media may be used. A computer-readable medium can be a computer-readable signal medium or a computer-readable storage medium. A computer-readable storage medium can be, for example—but not limited to—an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples (a non-exhaustive list) of computer-readable storage media include: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In this document, a computer-readable storage medium can be any tangible medium that contains or stores a program that can be used by or in connection with an instruction execution system, apparatus, or device.

[0064] Computer-readable signal media may include data signals propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such propagated data signals may take various forms, including—but not limited to—electromagnetic signals, optical signals, or any suitable combination thereof. Computer-readable signal media may also be any computer-readable medium other than computer-readable storage media, capable of transmitting, propagating, or transmitting programs for use by or in connection with an instruction execution system, apparatus, or device.

[0065] The program code contained on a computer-readable medium may be transmitted using any suitable medium, including—but not limited to—wireless, wire, optical fiber, RF, etc., or any suitable combination thereof.

[0066] Computer program code for performing the operations of this invention can be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, and C++, as well as conventional procedural programming languages ​​such as "C" or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network—including a local area network (LAN) or a wide area network (WAN)—or can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0067] Note that the above description is merely a preferred embodiment of the present invention and the technical principles employed. Those skilled in the art will understand that the present invention is not limited to the specific embodiments described herein, and various obvious changes, readjustments, and substitutions can be made without departing from the scope of protection of the present invention. Therefore, although the present invention has been described in detail through the above embodiments, the present invention is not limited to the above embodiments, and may include many other equivalent embodiments without departing from the concept of the present invention, the scope of which is determined by the scope of the appended claims.

Claims

1. A vehicle-to-cloud communication system for collecting vehicle data based on a diagnostic model, characterized in that, The system includes a central gateway (CGW) located in the vehicle and a remote server (TSP) in the cloud. The central gateway and the remote server establish a connection and communicate with each other via a vehicle-to-cloud communication protocol. The central gateway includes a gateway module and a communication module. The gateway module is configured to have gateway functions for Controller Area Network (CAN), Local Area Network (LIN), and Ethernet, and is used to route and acquire all network data of the vehicle's Electronic Control Unit (ECU). The communication module is communicatively connected to the gateway module and is used to send the data acquired by the gateway module to the remote server via a transmission protocol.

2. The vehicle-to-cloud communication system for collecting vehicle data based on a diagnostic model as described in claim 1, characterized in that, The central gateway is equipped with a diagnostic model, which includes data acquisition rules associated with multiple error codes; each error code is associated with a corresponding ECU, diagnostic identifier DID, error type, associated diagnostic message, and associated application message. The central gateway is used to identify errors issued by the ECU during production line diagnosis or remote diagnosis, query the diagnostic model based on the identified error, determine the corresponding error code and the associated diagnostic message and application message associated with the error code, and control the communication module to upload the determined associated message data to the remote server.

3. The vehicle-to-cloud communication system for collecting vehicle data based on a diagnostic model as described in claim 1, characterized in that, The central gateway is also used to resend historical associated message data within a certain time window when uploading associated message data.

4. The vehicle-to-cloud communication system for collecting vehicle data based on a diagnostic model as described in claim 1, characterized in that, The remote server is used to automatically parse the received associated message data and directly output the parsed signal value or version information.

5. The data acquisition method of a vehicle-to-cloud communication system for acquiring vehicle data based on a diagnostic model as described in claim 1, characterized in that, Specifically, the steps include the following: S1. Configure a diagnostic model in the central gateway on the vehicle side. The diagnostic model contains data acquisition rules associated with multiple error codes. Each error code is associated with a corresponding ECU, DID, error type, associated diagnostic message, and associated application message. S2. During production line diagnostics or remote diagnostics, the central gateway identifies errors issued by the ECU. S3. Based on the identified errors, query the diagnostic model to determine the corresponding error code and the associated diagnostic message and application message associated with that error code; S4. The central gateway uploads the identified associated message data to the remote cloud server.

6. The data acquisition method of a vehicle-to-cloud communication system for acquiring vehicle data based on a diagnostic model as described in claim 5, characterized in that, In step S1, the diagnostic model is classified according to different ECUs and a basic status message is bound to each type of ECU; a corresponding error code is established for the DID and possible error types of each ECU; and the relevant diagnostic messages and application messages required to troubleshoot each error are associated with the corresponding error code.

7. The data acquisition method of a vehicle-to-cloud communication system for acquiring vehicle data based on a diagnostic model as described in claim 5, characterized in that, In step S4, when the central gateway uploads the current associated message data, it also re-uploads the historical associated message data from the previous time window.

8. The data acquisition method of a vehicle-to-cloud communication system for acquiring vehicle data based on a diagnostic model as described in claim 5, characterized in that, In step S4, the remote server automatically parses the received associated message data and outputs the parsed signal value or version information.

9. A computer device, characterized in that, The system includes a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the program, it implements the data acquisition method of a vehicle-to-cloud communication system based on a diagnostic model for acquiring vehicle data as described in any one of claims 5-8.

10. A computer-readable storage medium, characterized in that, It stores a computer program that, when executed by a processor, implements the data acquisition method of a vehicle-to-cloud communication system for acquiring whole vehicle data based on a diagnostic model, as described in any one of claims 5-8.

Images