In-Vehicle Gateway for Cross-Network Diagnostic Translation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current diagnostic methods for in-vehicle electronic systems are limited in their ability to diagnose devices connected via Ethernet, and they struggle to harmonize with various network types and communication methods, particularly when using the Controller Area Network (CAN) and Ethernet simultaneously.
Innovation Solution
A diagnostic communication scheme that utilizes a message generator and receiver, with a header structure including protocol version, payload type, and length fields, to facilitate communication across different in-vehicle networks like CAN and Ethernet, using Transmission Control Protocol (TCP) for message transfer, and an in-vehicle gateway to convert messages between network types.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If diagnostic methods use traditional CAN network protocols, then compatibility with existing in-vehicle systems is maintained, but inability to diagnose Ethernet-connected devices occurs
Solution Approach 1:
The patent introduces a gateway device as an intermediary between CAN network diagnostic tools and Ethernet-connected controllers. The gateway translates diagnostic messages between CAN protocol format and Ethernet/IP protocol format, enabling universal diagnostic access. The gateway receives diagnostic requests from external tools via CAN, converts them to appropriate Ethernet messages, forwards them to target controllers, and translates responses back to CAN format for the diagnostic tool.
2Adaptability or versatility
If multiple communication networks (CAN and Ethernet) are used simultaneously, then diagnostic coverage is improved, but system complexity increases
Solution Approach 1:
The gateway device is designed with multi-functionality to handle both CAN and Ethernet protocols simultaneously. It performs protocol translation, message routing, data formatting, and controller identification across different network types using a single integrated device, eliminating the need for separate diagnostic tools for each network type.
Solution Approach 2:
The diagnostic system is segmented into distinct functional modules within the gateway: a CAN protocol processing module, an Ethernet protocol processing module, a message translation module, and a routing module. This segmentation allows each module to specialize in specific protocols while working together seamlessly, reducing overall system complexity through modular design.
3Ease of manufacture
If payload length is fixed for CAN compatibility, then existing diagnostic tools work without modification, but Ethernet communication efficiency is reduced
Solution Approach 1:
The system dynamically changes the payload length parameter based on the target network type. When communicating with CAN-connected controllers, the payload is limited to 8 bytes to match CAN message format requirements. When communicating with Ethernet-connected controllers through the gateway, the payload length can be extended beyond 8 bytes to accommodate larger data transfers, improving Ethernet communication efficiency while maintaining CAN compatibility.
Data Source
AI summary
An apparatus, for performing a diagnostic operation on plural controllers which are coupled via different types of in-vehicle communication networks, may include at least one of a message generator, configured to generate a diagnostic message used for the diagnostic operation on the plural controller, and a message receiver, configured to recognize the diagnostic message, wherein the diagnostic message that may be communicated over the in-vehicle communication networks includes a header and a payload, and wherein the payload is determined to correspond to a length of communication data for a controller area network (CAN).