Integrated TBOX remote diagnosis data optimization transmission method and system

Abstract

The invention provides an integrated TBOX remote diagnosis data optimization transmission method and system, and relates to the technical field of Internet of Vehicles. Comprising the steps that a cloud side sends a diagnosis instruction to a TBOX in an encrypted communication mode, and the TBOX conducts physical layer transparent transmission on the diagnosis instruction and transmits the diagnosis instruction to a vehicle-mounted MCU through a UART interface in a transparent mode; the vehicle-mounted MCU identifies a diagnosis instruction from the cloud based on an integrated UDS / J1939 protocol analysis engine, triggers and executes a diagnosis task, obtains a diagnosis result and carries out structured packaging; the vehicle-mounted MCU transmits the diagnosis result subjected to structured packaging back to the TBOX through the UART interface, and the TBOX finally transmits the diagnosis result subjected to structured packaging back to the cloud end in an encryption communication mode. According to the invention, the end-to-end transmission delay of the diagnosis instruction and the vehicle-mounted network protocol is reduced, the diagnosis response efficiency is improved, and high-reliability and low-delay remote diagnosis technical support is provided for the health management of the whole life cycle of the vehicle.

Description

Technical Field

[0001] This invention belongs to the field of vehicle networking technology, and in particular relates to an integrated TBOX remote diagnostic data optimization transmission method and system. Background Technology

[0002] In the field of remote diagnostics for intelligent connected vehicles, there are three main technical bottlenecks: protocol compatibility, transmission latency and reliability, and security and scalability. Specifically: regarding protocol compatibility, there are issues of multiple protocol conversion layers, low efficiency, and inconsistent protocol standards; regarding transmission latency and reliability, there are issues of high end-to-end transmission latency, insufficient data integrity guarantees, and limited diagnostic coverage scenarios; regarding security and scalability, there are issues of weak communication link security and limited diagnostic data dimensions.

[0003] For example, existing technologies require cloud commands to be received first through a T-Box (vehicle terminal), then converted into UDS / J1939 commands recognizable by the underlying ECU (Electronic Control Unit) via the CAN bus protocol, ultimately triggering the diagnostic module to execute tasks. This protocol conversion hierarchy, from cloud → T-Box → gateway → ECU, results in high end-to-end latency (typically exceeding 200ms). Furthermore, the protocol conversion logic is tightly coupled with the diagnostic application, making it difficult to flexibly expand to new protocols or adapt to the proprietary protocols of different automakers.

[0004] For example, in terms of security, existing technologies often use HTTPS or TLS protocols to protect cloud communication, but they do not combine physical layer isolation to build a two-layer protection system.

[0005] Chinese invention patent application CN 117289680 A discloses a remote monitoring and processing system and method for vehicle faults. The system includes a vehicle identification number (TBOX) and a vehicle manufacturer platform. The TBOX is configured to acquire vehicle information sent by various ECUs via the vehicle network and select relevant signal packets to upload to the vehicle manufacturer platform. In this technical solution, the TBOX and the diagnostic MCU are connected via CAN and Ethernet, posing a potential information security risk. Summary of the Invention

[0006] To overcome the shortcomings of the existing technologies, this invention provides an integrated TBOX remote diagnostic data optimization transmission method and system, which integrates intelligent protocol conversion, transmission optimization, and data closed-loop management. By constructing a three-level collaborative architecture of "cloud-vehicle terminal TBOX-vehicle control unit MCU", and adopting multi-protocol intelligent conversion technology, it reduces the end-to-end transmission latency between diagnostic commands and vehicle network protocols, improves diagnostic response efficiency, and provides highly reliable and low-latency remote diagnostic technology support for vehicle full life cycle health management.

[0007] To achieve the above objectives, one or more embodiments of the present invention provide the following technical solutions: The first aspect of this invention provides an integrated TBOX remote diagnostic data optimized transmission method.

[0008] An optimized transmission method for remote diagnostic data from an integrated TBOX includes the following steps: Construct a three-tier communication system comprising cloud, TBOX, and in-vehicle MCU; The cloud sends diagnostic commands to the TBOX using encrypted communication. The TBOX transmits the diagnostic commands transparently at the physical layer and transmits them to the vehicle MCU via the UART interface. The vehicle MCU uses an integrated UDS / J1939 protocol parsing engine to identify diagnostic commands from the cloud, trigger and execute diagnostic tasks, obtain diagnostic results, and encapsulate them in a structured manner. The vehicle-mounted MCU transmits the structured packaged diagnostic results back to the TBOX via the UART interface. The TBOX then transmits the structured packaged diagnostic results back to the cloud via encrypted communication.

[0009] A second aspect of the present invention provides an integrated TBOX remote diagnostic data optimization transmission system.

[0010] The integrated TBOX remote diagnostic data optimization transmission system includes: The communication system construction module is configured to build a three-level communication system including the cloud, TBOX, and vehicle MCU. The instruction delivery module is configured to: send diagnostic instructions to the TBOX via encrypted communication in the cloud; the TBOX transmits the diagnostic instructions transparently at the physical layer and transmits them to the vehicle MCU via the UART interface; The diagnostic execution module is configured such that the on-board MCU identifies diagnostic commands from the cloud based on the integrated UDS / J1939 protocol parsing engine, triggers and executes diagnostic tasks, obtains diagnostic results, and performs structured encapsulation. The result feedback module is configured such that the onboard MCU transmits the structured packaged diagnostic results back to the TBOX via the UART interface, and the TBOX transmits the structured packaged diagnostic results back to the cloud via encrypted communication.

[0011] A third aspect of the present invention provides a computer-readable storage medium having a program stored thereon that, when executed by a processor, implements the steps of the integrated TBOX remote diagnostic data optimization transmission method as described in the first aspect of the present invention.

[0012] A fourth aspect of the present invention provides an electronic device including a memory, a processor, and a program stored in the memory and executable on the processor, wherein the processor executes the program to implement the steps of the integrated TBOX remote diagnostic data optimization transmission method as described in the first aspect of the present invention.

[0013] The above one or more technical solutions have the following beneficial effects: This invention provides an integrated TBOX remote diagnostic data optimization transmission method and system, integrating intelligent protocol conversion, transmission optimization, and data closed-loop management. By constructing a three-level collaborative architecture of cloud-vehicle terminal TBOX-vehicle control unit, it achieves a breakthrough of less than 200ms end-to-end transmission latency for diagnostic commands and a 40% improvement in response efficiency. Its core advantages include: 1) Multi-protocol intelligent conversion technology uses HTTPS encrypted transmission and UDS / J1939 protocol parsing engine to decouple the underlying diagnostic protocol from the upper layer application, breaking through the protocol compatibility bottleneck; 2) The high-reliability transmission mechanism employs closed-loop processing of diagnostic data, proactive reporting, local caching for breakpoint resumption, and dynamic priority scheduling to ensure data integrity and real-time performance. 3) A two-layer security protection system combines HTTPS and UART physical isolation, supports bidirectional conversion of international standard protocols, and enhances system security and scalability; 4) Full-scenario diagnostic capabilities enable engine shutdown wake-up, multi-source data fusion and collection, and user-manufacturer dual-channel interaction to form a three-dimensional diagnostic information package that covers the entire life cycle of vehicle health management, significantly improving the real-time performance, reliability and business expansion capabilities of remote diagnostics.

[0014] Advantages of additional aspects of the invention will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of the invention. Attached Figure Description

[0015] The accompanying drawings, which form part of this invention, are used to provide a further understanding of the invention. The illustrative embodiments of the invention and their descriptions are used to explain the invention and do not constitute an improper limitation of the invention.

[0016] Figure 1 This is a flowchart of the method in Example 1.

[0017] Figure 2 This is a flowchart of the method in Example 1. Detailed Implementation

[0018] It should be noted that the following detailed descriptions are exemplary and intended to provide further illustration of the invention. Unless otherwise specified, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this invention pertains.

[0019] It should be noted that the terminology used herein is for the purpose of describing particular implementations only and is not intended to limit the exemplary implementations of the present invention.

[0020] Where there is no conflict, the embodiments and features in the embodiments of the present invention can be combined with each other.

[0021] Terminology Explanation (1) TBOX (Telematics Box): A smart device integrated into a vehicle, mainly used to enable the vehicle to connect and communicate with external networks (such as the Internet and mobile communication networks). It is one of the core components of the Internet of Vehicles (V2X), and enables data interaction between the vehicle and the back-end server, other devices or users through wireless communication technologies (such as 4G / 5G, GPS, CAN bus, etc.).

[0022] (2) Integrated TBOX: It is a highly integrated vehicle terminal device that integrates the traditional TBOX and MCU into a single controller to achieve multifunctional, high-efficiency, and low-cost vehicle information interaction and control.

[0023] (3) AUTOSAR architecture: AUTomotive Open System Architecture, a standardized automotive software framework designed to unify in-vehicle software development and improve modularity and portability.

[0024] (4) Dem module (Diagnostic Event Manager): The diagnostic event management module is responsible for monitoring vehicle fault events (such as fault code triggering), recording diagnostic data, and coordinating the execution of diagnostic tasks.

[0025] (5) UDS Protocol (Unified Diagnostic Services): The Unified Diagnostic Services Protocol defined by the International Organization for Standardization (ISO 14229) is used for diagnostic communication of vehicle electronic control units (ECUs) and supports functions such as fault code reading, clearing, and data stream monitoring.

[0026] (6) J1939 protocol: A communication protocol based on CAN bus (SAE J1939 standard), mainly used for vehicle network communication of heavy vehicles (such as trucks and agricultural machinery), supporting real-time data exchange and diagnosis between devices.

[0027] (7) HTTPS protocol: Based on the SSL / TLS encrypted HTTP protocol, it provides secure client-server communication and ensures the confidentiality and integrity of data transmission.

[0028] (8) UART interface: Universal Asynchronous Receiver / Transmitter Interface, a serial communication protocol used for short-distance, full-duplex data transmission.

[0029] (9) Intelligent protocol conversion: Automatically parses and converts data formats between different communication protocols (such as HTTPS and UDS / J1939) to achieve cross-platform compatibility.

[0030] (10) Local caching mechanism: Temporary data (such as diagnostic results and vehicle status information) is stored locally. The data is temporarily stored when the network is interrupted and will continue to be transmitted after the network is restored.

[0031] (11) Dynamic scheduling of diagnostic priority: Communication resources are dynamically allocated according to the urgency of the diagnostic task, and key fault information is processed first.

[0032] (12) Three-dimensional diagnostic information package: a composite data package containing diagnostic results, real-time vehicle status (such as operating parameters) and geographical location information.

[0033] (13) Remote wake-up technology: When the vehicle is turned off, the on-board diagnostic system can be remotely activated by cloud commands to extract and transmit historical diagnostic data.

[0034] (14) OTA upgrade strategy (Over-The-Air): a technology that uses wireless communication to remotely update vehicle software or firmware, supporting system function optimization and vulnerability repair.

[0035] (15) Transparent transmission: Data is not parsed or modified during transmission and is directly forwarded to the target device.

[0036] (16) Data closed-loop management: full lifecycle management from data collection, transmission, storage to feedback, to ensure data integrity and traceability.

[0037] (17) Two-layer security protection system: Combining encrypted communication (such as HTTPS) and physical layer isolation (such as UART) multi-level security mechanisms to ensure data transmission security.

[0038] Overall concept of the invention The shortcomings of existing technologies mainly lie in protocol conversion efficiency, data transmission reliability, system security, diagnostic scenario coverage, and data value mining. Specifically, the disadvantages of remote diagnostic technology for intelligent connected vehicles are as follows: (a) Protocol compatibility defects: (1) The protocol conversion has many layers and low efficiency. Existing systems typically employ a multi-layer protocol adaptation architecture (such as cloud-gateway-TBOX-ECU multi-layer conversion), resulting in lengthy protocol parsing and conversion processes and increased transmission latency (typical latency >300ms).

[0039] Typical problem: The underlying diagnostic protocols such as UDS / J1939 and the upper-layer HTTPS application layer protocols need to be converted multiple times, resulting in insufficient interface standardization and poor protocol stack compatibility, which limits the expansion of cross-platform diagnostic functions.

[0040] (2) Inconsistent protocol standards The lack of a unified standard for in-vehicle network protocols (such as CAN and LIN) and cloud communication protocols (such as HTTP) makes it difficult for ECUs or cloud platforms from different manufacturers to communicate directly, requiring the reliance on customized middleware and increasing development costs.

[0041] (ii) Transmission delay and reliability issues: (1) High end-to-end transmission delay Traditional TBOXes typically use layered protocol processing (such as parsing HTTP commands first and then converting them to UDS / J1939), resulting in diagnostic command transmission delays generally exceeding 200ms, which affects diagnostic scenarios with high real-time requirements (such as emergency fault diagnosis).

[0042] (2) Insufficient data integrity protection Network interruption leads to data loss: The existing system lacks local caching and breakpoint resume mechanism. After the network is restored, it cannot automatically retransmit the diagnostic data during the interruption, resulting in incomplete data.

[0043] No-priority scheduling: Critical fault information (such as fault codes) and non-critical data (such as ECU operating parameters) use the same transmission channel, which may cause delays or loss of emergency data due to bandwidth contention.

[0044] (3) Limited diagnostic coverage scenarios Traditional systems rely on the vehicle being started to perform diagnostics. After the engine is turned off, the ECU cannot be remotely woken up to collect data, resulting in the inability to monitor the health status of vehicles at night or when they are parked for a long time.

[0045] (iii) Insufficient security and scalability (1) Weak security of communication links Single-layer encryption protection: Most existing systems only use application-layer encryption (such as TLS), lacking the dual protection of physical layer isolation (such as transparent transmission of UART protocol) and application-layer encryption, making them vulnerable to man-in-the-middle attacks.

[0046] Protocol pass-through risk: Some systems use CAN transmission for TBOX and MCU, which may lead to unauthorized intrusion of the ECU due to protocol parsing vulnerabilities.

[0047] (2) Diagnostic data has a single dimension. Existing systems typically only collect ECU fault codes, lacking correlation with vehicle status (GPS positioning, VIN code) and environmental information, resulting in isolated diagnostic results and making it difficult to achieve accurate fault location and scenario-based analysis.

[0048] This invention addresses the aforementioned issues through innovations such as a three-tier collaborative architecture, intelligent protocol conversion, and closed-loop data management, providing a more efficient and secure remote diagnostic solution for the full lifecycle health management of intelligent connected vehicles.

[0049] Specifically, this invention proposes an innovative solution for remote diagnostics of intelligent connected vehicles. Addressing technical bottlenecks such as poor protocol compatibility, high transmission latency, and insufficient data integrity, it constructs a three-level collaborative architecture of cloud-vehicle terminal (TBOX)-vehicle control unit (MCU).

[0050] By employing multi-protocol intelligent conversion and transparent transmission technology, and using HTTPS encrypted transmission combined with the UDS / J1939 protocol parsing engine, a breakthrough was achieved in diagnostic command end-to-end latency of less than 200ms and response efficiency improvement of over 40%, solving the problems of multiple protocol conversion layers and high latency in traditional systems. At the same time, a highly reliable data closed-loop mechanism is established to support real-time feedback of diagnostic results, proactive reporting of diagnostic data, breakpoint resumption, and emergency priority processing, ensuring data integrity and real-time monitoring capabilities. Furthermore, this invention balances system security and scalability through a dual-layer security protection system, international standard protocol compatibility design, and AUTOSAR architecture integration. It also innovatively integrates multi-source diagnostic data acquisition, remote wake-up in engine shutdown scenarios, and user-manufacturer dual-channel interaction functions, achieving technical support for all-time diagnostic coverage and full lifecycle health management.

[0051] This invention, centered on protocol decoupling, transmission optimization, and data closed-loop, overcomes several technical challenges in the field of remote diagnostics. Its multi-protocol intelligent conversion architecture and three-level collaborative transmission design significantly improve diagnostic efficiency and reliability, while proactive reporting, remote wake-up, and dual-channel interaction functions expand the comprehensiveness and real-time capability of diagnostic scenarios. Through standardized interfaces and modular design, the system is compatible with international standard protocols such as UDS / J1939 and achieves deep integration with vehicle ECUs, providing a highly reliable, low-latency remote diagnostic solution for intelligent connected vehicles. It can be widely applied to scenarios such as vehicle fault diagnosis, health status monitoring, and full lifecycle management.

[0052] Example 1 Current remote diagnostic technologies mostly rely on independent external TBOXes. The TBOXes interact with the controller to be diagnosed via the CAN_UDS protocol. Integrated TBOXes lack fast and effective remote diagnostic technologies.

[0053] The purpose of this embodiment is to address the technical bottlenecks in the field of remote diagnostics for intelligent connected vehicles, such as poor protocol compatibility, high transmission latency, and insufficient data integrity, and to propose an integrated and highly reliable remote diagnostic solution to achieve the following core objectives: (1) Improve protocol compatibility and communication efficiency. By constructing a three-level collaborative architecture of "cloud-vehicle terminal-TBOX-vehicle control unit", adopting multi-protocol intelligent conversion technology (bidirectional conversion between UDS / J1939 and HTTPS protocol), the diagnostic commands and vehicle network protocols are seamlessly connected, solving the delay problem caused by multiple protocol layers in traditional systems, reducing end-to-end transmission delay to less than 200ms, and improving cross-platform compatibility through standardized interfaces.

[0054] (2) Optimize the closed-loop management of diagnostic data and establish a complete mechanism for the collection, transmission, storage and feedback of diagnostic data. Real-time bidirectional transmission of diagnostic results and vehicle status information (such as fault codes and operating parameters) is supported, and priority handling of emergency faults and asynchronous transmission of non-critical data are supported. Data integrity is ensured through local caching and breakpoint resume technology. The innovative implementation of proactive reporting of diagnostic data (such as periodic collection of vehicle status using the J1939 protocol) is realized to support the full life cycle health management of vehicles.

[0055] (3) Enhance system security and reliability, build a two-layer security protection system (HTTPS encryption + UART physical isolation) to ensure the security of the communication link between the cloud and the vehicle terminal; improve the deep integration of diagnostic functions and ECU based on the modular design of AUTOSAR architecture to reduce the risk of system failure.

[0056] (4) Achieve full-scenario diagnostic coverage and multi-terminal collaboration. Through remote wake-up technology in the case of engine shutdown, break through the dependence of traditional diagnosis on vehicle start-up and achieve full-time diagnostic coverage. Integrate VIN code, GPS positioning and other multi-source data to form a three-dimensional diagnostic information package to improve diagnostic accuracy. Support dual-channel information interaction between user end and manufacturer end (users view basic diagnostic information in real time, and manufacturers obtain complete data packages for in-depth analysis and OTA upgrade strategy formulation) to form an efficient collaborative diagnostic ecosystem.

[0057] In summary, this invention aims to build a highly reliable, low-latency, and cross-platform compatible remote diagnostic system through technological innovations such as protocol decoupling, transmission optimization, data closed-loop, and security enhancement. This system will provide technical support for the full lifecycle health management of vehicles and promote the development of intelligent connected vehicle diagnostic technology towards intelligence, real-time capabilities, and full-scenario application.

[0058] like Figure 1 As shown, the integrated TBOX remote diagnostic data optimization transmission method provided in this embodiment includes the following steps: Construct a three-tier communication system comprising cloud, TBOX, and in-vehicle MCU; The cloud sends diagnostic commands to the TBOX using encrypted communication. The TBOX transmits the diagnostic commands transparently at the physical layer and transmits them to the vehicle MCU via the UART interface. The vehicle MCU uses an integrated UDS / J1939 protocol parsing engine to identify diagnostic commands from the cloud, trigger and execute diagnostic tasks, obtain diagnostic results, and encapsulate them in a structured manner. The vehicle-mounted MCU transmits the structured packaged diagnostic results back to the TBOX via the UART interface. The TBOX then transmits the structured packaged diagnostic results back to the cloud via encrypted communication.

[0059] Among them, the UDS / J1939 protocol parsing engine can convert the proprietary diagnostic protocol instructions of different car manufacturers into unified diagnostic protocol instructions that can be recognized by the controller.

[0060] It is understandable that different car manufacturers' proprietary diagnostic protocols have differences in data encapsulation (including message structure and verification methods) and instruction semantics (including feature identifier definitions and status code mechanisms).

[0061] The proprietary diagnostic protocol commands from different car manufacturers in the cloud are converted into unified diagnostic protocol commands that can be recognized by the controller. The specific implementation method is as follows: First, import the target vendor's proprietary diagnostic protocol into the proprietary protocol library; Secondly, the protocol parsing engine extracts the feature flags of the proprietary diagnostic protocol, identifies the diagnostic action of each instruction, and then maps it to the unified diagnostic protocol (UDS / J1939) recognized by the controller, thereby completing the conversion from the vehicle manufacturer's proprietary protocol to the unified diagnostic protocol.

[0062] This invention addresses the technical bottlenecks in remote diagnostics of integrated TBOX controllers for intelligent connected vehicles, such as poor protocol compatibility, high transmission latency, and insufficient data integrity. It proposes an innovative solution integrating intelligent protocol conversion, transmission optimization, and closed-loop data management. By constructing a three-level collaborative architecture of cloud-vehicle terminal-vehicle control unit, it achieves a breakthrough by reducing end-to-end diagnostic command transmission latency to below 200ms and improving diagnostic response efficiency by over 40%, providing highly reliable, low-latency remote diagnostic technology support for vehicle lifecycle health management.

[0063] The technical solution of this embodiment will be explained in detail below.

[0064] (1) Multi-protocol intelligent conversion and transparent transmission architecture.

[0065] This embodiment constructs a three-level communication system of cloud-vehicle terminal (TBOX)-vehicle control unit (MCU), and innovatively adopts the technical solution of "HTTPS protocol encrypted transmission + protocol transparent pass-through + underlying protocol intelligent conversion": The cloud sends diagnostic commands to the TBOX via 4G / 5G network using the HTTPS protocol. The TBOX then transmits the messages transparently at the physical layer, passing them through the native protocol of the UART interface to the MCU.

[0066] The vehicle-mounted MCU's remote diagnostic module integrates a UDS / J1939 protocol parsing engine, which can intelligently identify and convert cloud commands, directly triggering the AUTOSAR-based Dem diagnostic module to execute diagnostic tasks. This decouples the underlying diagnostic protocol (UDS / J1939) from the upper-layer application, achieving cross-platform compatibility and business expansion of diagnostic information through standardized data interfaces.

[0067] The above-mentioned technical means have overcome the technical bottlenecks of traditional system protocol conversion layers and high latency, and achieved end-to-end diagnostic command transmission latency of less than 200ms.

[0068] (2) High-reliability diagnostic data transmission and storage mechanism.

[0069] like Figure 2 As shown, this embodiment establishes a complete closed-loop processing flow for diagnostic data: Fault diagnosis result feedback direction: After the Dem module completes the reading and clearing of fault codes, the remote diagnostic management module uses the UDS protocol specification to encapsulate the diagnostic results in a structured manner and transmits them back to the cloud in real time via the TBOX through the reverse transmission path.

[0070] Diagnostic information broadcast direction: The system innovatively implements the function of proactively reporting diagnostic data. It periodically collects vehicle status information through the J1939 protocol, encapsulates it into standardized diagnostic data packets, and proactively sends them to the cloud at preset intervals (such as 500ms) to achieve real-time monitoring of vehicle health status.

[0071] Local caching mechanism: The vehicle stores diagnostic data (including fault codes, operating parameters, etc.), and automatically triggers breakpoint resume transmission after the network is restored to ensure data integrity.

[0072] Dynamic scheduling of diagnostic priorities: An emergency fault code priority handling mechanism (such as collision, lock picking) is adopted to ensure real-time transmission of critical fault information. Non-critical diagnostic data is processed through an asynchronous transmission channel to reduce communication resource consumption.

[0073] By using the HTTPS protocol to ensure the security of cloud communication links and combining the physical layer isolation characteristics of the UART interface, a two-layer security protection system is constructed.

[0074] (3) Full-scenario diagnostic data acquisition and wake-up, multi-terminal collaboration technology.

[0075] Multi-source data fusion acquisition: During the diagnostic process, the vehicle's VIN code and GPS location information are collected simultaneously and intelligently bound to the diagnostic data to form a three-dimensional diagnostic information package containing "diagnostic results + vehicle status + geographical location".

[0076] Remote wake-up technology for engine shutdown scenarios: When the vehicle is off, the diagnostic system can be activated via a remote wake-up command in the cloud, extracting and transmitting historical diagnostic data. This breaks through the limitation of traditional diagnostics relying on vehicle startup, achieving full-time diagnostic coverage.

[0077] Dual-channel information exchange between user and manufacturer: End users can view basic vehicle diagnostic information (such as fault status and location information) in real time via mobile devices. The manufacturer's backend can obtain complete diagnostic data packages, supporting in-depth fault code analysis, historical data tracing, and OTA upgrade strategy formulation.

[0078] This embodiment of the technical solution optimizes the protocol conversion layer and innovates the transmission path design, while ensuring the integrity of diagnostic data and improving diagnostic response efficiency by more than 40%. It also enables real-time monitoring and proactive reporting of diagnostic data, providing a highly reliable and low-latency solution for remote diagnostics of intelligent connected vehicles.

[0079] This embodiment has the following innovative features: Innovation Point 1: Multi-protocol intelligent conversion system.

[0080] Diagnostic command issuance direction: The remote diagnostic module of the vehicle MCU integrates a UDS / J1939 protocol parsing engine, which can intelligently identify and convert cloud commands (automaker-specific protocols) to directly trigger the Dem diagnostic module based on the AUTOSAR architecture to execute diagnostic tasks. This decouples the underlying diagnostic protocol (UDS / J1939) from the upper-layer application, and achieves cross-platform compatibility and business expansion of diagnostic information through standardized data interfaces.

[0081] Directions for reporting diagnostic results: After the Dem module completes the reading and clearing of fault codes, the remote diagnostic management module uses the UDS protocol specification to encapsulate the diagnostic results in a structured manner and transmits them back to the cloud in real time via the TBOX through the reverse transmission path.

[0082] This embodiment innovatively implements the function of actively reporting diagnostic data. It periodically collects vehicle status information through the J1939 protocol, encapsulates it into a standardized diagnostic data packet, and actively sends it to the cloud at a preset period (such as 500ms) to realize real-time monitoring of vehicle health status.

[0083] This embodiment overcomes the technical bottlenecks of traditional protocols having multiple conversion layers and high latency, achieving an end-to-end diagnostic command transmission latency of less than 200ms.

[0084] Innovation Point Two: High-Reliability Diagnostic Data Transmission and Storage Mechanism.

[0085] Local caching mechanism: The vehicle stores diagnostic data (including fault codes, operating parameters, etc.), and automatically triggers breakpoint resume transmission after the network is restored to ensure data integrity.

[0086] Dynamic scheduling of diagnostic priorities: An emergency fault code priority handling mechanism is adopted to ensure real-time transmission of critical fault information. Non-critical diagnostic data is processed through an asynchronous transmission channel to reduce communication resource consumption.

[0087] By using the HTTPS protocol to ensure the security of cloud communication links and combining the physical layer isolation characteristics of the UART interface, a two-layer security protection system is constructed.

[0088] Innovation Point 3: Full-Scenario Diagnostic Data Collection and Activation.

[0089] Multi-source data fusion acquisition: During the diagnostic process, the vehicle's VIN code and GPS location information are collected simultaneously and intelligently bound to the diagnostic data to form a three-dimensional diagnostic information package containing "diagnostic results + vehicle status + geographical location".

[0090] Remote wake-up technology for engine shutdown scenarios: When the vehicle is off, the diagnostic system can be activated via a remote wake-up command in the cloud, extracting and transmitting historical diagnostic data. This breaks through the limitation of traditional diagnostics relying on vehicle startup, achieving full-time diagnostic coverage.

[0091] The technical effects of this embodiment are demonstrated in the following aspects: 1. Breakthrough in transmission efficiency: End-to-end latency reduced by 60%, diagnostic response efficiency improved by 40%; 2. Data integrity guarantee: Local caching + breakpoint resume ensures a data integrity loss rate of <0.01%; 3. Full-scenario coverage: Supports full lifecycle vehicle diagnostics, including engine shutdown / start and other full-condition diagnostics; 4. Two-way value mining: Building a collaborative service system that combines real-time user monitoring with in-depth manufacturer analysis; 5. Industry standard compatibility: Supports international standard protocols such as ISO 14229 and SAE J1939.

[0092] Finally, a difference analysis is performed on the existing technical solutions that are closest to this embodiment: (1) Regarding vehicle protocol conversion middleware: In traditional vehicle systems, the conversion between UDS (Unified Diagnostic Service) and J1939 (Heavy Vehicle Network Protocol) protocols usually relies on multi-level middleware (such as gateway modules) to achieve protocol conversion through layered parsing, protocol adaptation, and command mapping.

[0093] For example, cloud commands need to be received first through the T-Box (vehicle terminal), and then converted into UDS / J1939 commands that can be recognized by the underlying ECU (electronic control unit) via the CAN bus protocol, ultimately triggering the diagnostic module to execute the task.

[0094] Technical limitations: Multiple protocol conversion layers (e.g., cloud → T-Box → gateway → ECU) result in high end-to-end latency (typically exceeding 200ms). The protocol conversion logic is tightly coupled with diagnostic applications, making it difficult to flexibly extend to new protocols or adapt to the proprietary protocols of different car manufacturers.

[0095] (2) Integration of diagnostic modules based on AUTOSAR: Some systems have adopted the AUTOSAR architecture to implement diagnostic modules (such as the Dem module), but their protocol parsing and command triggering usually rely on predefined fixed protocols (such as UDS) and cannot dynamically adapt to private protocol commands issued from the cloud.

[0096] In terms of protocol conversion efficiency, this embodiment integrates the UDS / J1939 parsing engine to achieve intelligent protocol conversion directly in the remote diagnostic module, reducing intermediate layer latency (<200ms), while existing technologies have higher latency due to multiple layers.

[0097] Regarding protocol decoupling, this embodiment achieves decoupling between the protocol and the application through a standardized data interface, supporting flexible expansion; existing technologies require redeveloping adaptation logic for each protocol.

[0098] (3) Regarding the mechanism for transmitting and storing diagnostic results: Traditional systems transmit diagnostic results such as fault codes via the UDS protocol, but this transmission is usually passive and only occurs when the vehicle is started or under specific triggering conditions. It lacks active reporting and breakpoint resume functionality.

[0099] For example, some systems use local caching to store diagnostic data, but after the network recovers, data retransmission needs to be manually or periodically triggered, and the integrity of interrupted transmission cannot be guaranteed.

[0100] (4) Diagnostic priority scheduling and security mechanisms Some systems support fault code priority classification (such as priority transmission for emergency faults), but this is usually achieved through simple queue management without combining dynamic scheduling algorithms to optimize resource allocation.

[0101] In terms of security, HTTPS or TLS protocols are commonly used to protect cloud communication, but they do not combine physical layer isolation (such as UART interface) to build a two-layer protection system.

[0102] Regarding proactive reporting and real-time performance, this embodiment proactively reports diagnostic data periodically (e.g., every 500ms) via the J1939 protocol, while existing technologies mostly rely on passive triggering or fixed-period transmission, resulting in insufficient real-time performance.

[0103] Regarding breakpoint resume and dynamic priority scheduling, this embodiment supports automatic breakpoint resume after network recovery and priority handling of emergency fault codes, while existing technologies lack such mechanisms.

[0104] In terms of security, this embodiment combines two layers of protection with physical isolation between HTTPS and UART, while existing technologies mostly rely on a single encryption protocol.

[0105] (5) Multi-source data acquisition and binding Some systems can collect information such as VIN codes and GPS, but they usually only associate the diagnostic results during the diagnostic process, without forming a three-dimensional data package of "diagnostic results + vehicle status + geographical location", and the data binding logic is not intelligent enough.

[0106] (6) Remote wake-up technology Traditional T-Boxes support remote wake-up, but require the vehicle to be in a dormant state (e.g., the key is not removed), and the diagnostic tasks can only be performed after the vehicle is started. For example, some systems can wake up the ECU via the CAN bus, but the diagnostic module cannot be activated when the engine is off (the vehicle is completely powered off). This embodiment directly wakes up the diagnostic system of a vehicle that is off via cloud commands (without requiring the vehicle to be started).

[0107] This embodiment forms a three-dimensional diagnostic package through intelligent binding of multi-source data, while existing technologies mostly involve isolated data acquisition and lack correlation integration.

[0108] Example 2 This embodiment discloses an integrated TBOX remote diagnostic data optimization transmission system.

[0109] The integrated TBOX remote diagnostic data optimization transmission system includes: The communication system construction module is configured to build a three-level communication system including the cloud, TBOX, and vehicle MCU. The instruction delivery module is configured to: send diagnostic instructions to the TBOX via encrypted communication in the cloud; the TBOX transmits the diagnostic instructions transparently at the physical layer and transmits them to the vehicle MCU via the UART interface; The diagnostic execution module is configured such that the on-board MCU identifies diagnostic commands from the cloud based on the integrated UDS / J1939 protocol parsing engine, triggers and executes diagnostic tasks, obtains diagnostic results, and performs structured encapsulation. The result feedback module is configured such that the onboard MCU transmits the structured packaged diagnostic results back to the TBOX via the UART interface, and the TBOX transmits the structured packaged diagnostic results back to the cloud via encrypted communication. Example 3 The purpose of this embodiment is to provide a computer-readable storage medium.

[0110] A computer-readable storage medium having a computer program stored thereon that, when executed by a processor, implements the steps of the integrated TBOX remote diagnostic data optimization transmission method as described in Embodiment 1 of this disclosure.

[0111] Example 4 The purpose of this embodiment is to provide an electronic device.

[0112] An electronic device includes a memory, a processor, and a program stored in the memory and executable on the processor, wherein the processor executes the program to implement the steps in the integrated TBOX remote diagnostic data optimization transmission method as described in Embodiment 1 of this disclosure.

[0113] The steps and methods involved in the apparatuses of Embodiments 2, 3, and 4 above correspond to those in Embodiment 1. For specific implementation details, please refer to the relevant description section of Embodiment 1. The term "computer-readable storage medium" should be understood as a single medium or multiple media including one or more instruction sets; it should also be understood as including any medium capable of storing, encoding, or carrying an instruction set for execution by a processor and enabling the processor to perform any of the methods in this invention.

[0114] Those skilled in the art will understand that the modules or steps of the present invention described above can be implemented using general-purpose computer devices. Optionally, they can be implemented using computer-executable program code, thereby allowing them to be stored in a storage device for execution by a computer device, or they can be fabricated as separate integrated circuit modules, or multiple modules or steps can be fabricated as a single integrated circuit module. The present invention is not limited to any particular combination of hardware and software.

[0115] While the specific embodiments of the present invention have been described above in conjunction with the accompanying drawings, this is not intended to limit the scope of protection of the present invention. Those skilled in the art should understand that various modifications or variations that can be made by those skilled in the art without creative effort based on the technical solutions of the present invention are still within the scope of protection of the present invention.

Claims

1. An integrated TBOX remote diagnosis data optimization transmission method, characterized in that, The method comprises the following steps: A three-level communication system including a cloud, a TBOX and a vehicle-mounted MCU is constructed; The cloud sends a diagnostic instruction to the TBOX in an encrypted communication mode, the TBOX performs physical layer transparent transmission on the diagnostic instruction, and transmits the diagnostic instruction to the vehicle-mounted MCU through a UART interface; The vehicle-mounted MCU identifies the diagnostic instruction from the cloud based on an integrated UDS / J1939 protocol analysis engine, triggers and executes a diagnostic task, obtains a diagnostic result and performs structured packaging on the diagnostic result; The vehicle-mounted MCU transmits the structured diagnostic result back to the TBOX through the UART interface, and the TBOX finally transmits the structured diagnostic result back to the cloud in an encrypted communication mode. 2.The integrated TBOX remote diagnosis data optimized transmission method according to claim 1, wherein, The cloud and the TBOX communicate through an HTTPS protocol; Alternatively, After obtaining the diagnostic result, the vehicle-mounted MCU judges the priority of the diagnostic result and transmits the diagnostic result back according to the priority. 3.The integrated TBOX remote diagnosis data optimized transmission method of claim 1, wherein, The vehicle-mounted MCU identifies the diagnostic instruction from the cloud based on the integrated UDS / J1939 protocol analysis engine, and the specific mode is as follows: The vehicle-mounted MCU converts the private diagnostic protocol instructions of different automobile manufacturers from the cloud into uniform diagnostic protocol instructions recognized by the controller based on the UDS / J1939 protocol analysis engine, and the specific process includes: Importing the private diagnostic protocol of the target automobile manufacturer into a private protocol library; The protocol analysis engine extracts the characteristic marks of the private protocol of the target automobile manufacturer from the private protocol library, identifies each private diagnostic protocol instruction of the automobile manufacturer as a diagnostic action, and maps the identified diagnostic action to the uniform diagnostic protocol recognized by the controller, i.e., UDS / J1939, thereby completing the conversion of the private diagnostic protocol of the automobile manufacturer to the uniform diagnostic protocol. After the conversion is completed, the diagnostic task is triggered and executed to obtain a diagnostic result. Alternatively, The private diagnostic protocols of different automobile manufacturers have data packaging differences and instruction semantic differences, the data packaging differences include message structure and verification method, and the instruction semantic differences include characteristic identification bit definition and state code mechanism. During the execution of the diagnostic task, the vehicle-mounted MCU synchronously collects the vehicle VIN code and GPS positioning information, binds the vehicle VIN code and GPS positioning information with the diagnostic result, forms a diagnostic information package containing the diagnostic result, vehicle state and geographical position, performs structured packaging on the diagnostic information package, and obtains the structured diagnostic result. 4.The integrated TBOX remote diagnosis data optimized transmission method of claim 1, wherein, Further, the vehicle-mounted MCU actively sends the structured diagnostic result to the cloud at a preset period to realize real-time monitoring of the vehicle health status. 5.The integrated TBOX remote diagnosis data optimized transmission method of claim 4, wherein, Further, in the vehicle off state, the cloud activates the diagnostic system of the vehicle-mounted MCU through a remote wake-up instruction, extracts and transmits historical diagnostic data of the vehicle. 6.The integrated TBOX remote diagnosis data optimized transmission method according to claim 1, wherein, The vehicle-mounted MCU stores the structured diagnostic result to the vehicle end and automatically triggers breakpoint resume after network recovery. 7.The integrated TBOX remote diagnosis data optimized transmission method according to claim 1, wherein, The method comprises:

8. An integrated TBOX remote diagnosis data optimized transmission system, characterized in that, A communication system construction module configured to construct a three-level communication system including a cloud, a TBOX and a vehicle-mounted MCU; ​ The instruction issuing module is configured to: the cloud sends a diagnosis instruction to the TBOX in an encrypted communication mode, the TBOX performs physical layer transparent transmission on the diagnosis instruction, and transmits the diagnosis instruction to the vehicle-mounted MCU through a UART interface; The diagnosis executing module is configured to: the vehicle-mounted MCU identifies the diagnosis instruction from the cloud based on the integrated UDS / J1939 protocol analysis engine, triggers and executes a diagnosis task, obtains a diagnosis result, and performs structured packaging; The result returning module is configured to: the vehicle-mounted MCU transmits the structured diagnosis result to the TBOX through the UART interface, and the TBOX finally transmits the structured diagnosis result to the cloud in an encrypted communication mode.

9. A computer-readable storage medium having stored thereon a program, characterized in that, The program is executed by the processor to implement the steps in the integrated TBOX remote diagnosis data optimized transmission method according to any one of claims 1-7.

10. An electronic device comprising a memory, a processor, and a program stored on the memory and executable on the processor, characterized in that, The processor executes the program to implement the steps in the integrated TBOX remote diagnosis data optimized transmission method according to any one of claims 1-7.

Images