Communication Receiver for ECU Service Protocol Offloading

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing in-vehicle communication systems face challenges in implementing service-oriented communication due to limited processing capabilities of microcomputers in ECUs, making it difficult to establish protocol stacks for service communication.

Innovation Solution

A communication receiver is introduced with a first and second interface, a service control unit, and a service interface unit, enabling service-oriented communication by transmitting search messages and converting event messages into stream data, even when protocol stacks cannot be implemented in the main control unit.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If protocol stacks are implemented in microcomputers of ECUs to enable service-oriented communication, then communication capability is improved, but processing capability requirements increase beyond what microcomputers can provide

Engineering Contradiction:
Improveservice-oriented communication capabilityVSAvoidprocessing capability
Core Design Contradiction:
Adaptability or versatilityVSPower

Solution Approach 1:

The system segments the communication functionality by separating the service-oriented communication protocol stack from the main control unit. The communication receiver handles protocol conversion and data transmission, while the main control unit processes application-level data. This segmentation allows service-oriented communication without requiring the microcomputer to implement full protocol stacks.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The communication receiver acts as an intermediary between the main control unit and external communication interfaces. It receives data from the main control unit, converts it to service-oriented protocol formats, transmits it via communication lines, and handles protocol conversion for different communication protocols (CAN, LIN, MOST, FlexRay, Ethernet). This intermediary function enables service-oriented communication without burdening the microcomputer with protocol stack implementation.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Device complexity

If data conversion and protocol handling are performed in the main control unit, then integration is simplified, but processing load and communication delays increase

Engineering Contradiction:
Improveintegration complexityVSAvoiddata processing efficiency
Core Design Contradiction:
Device complexityVSProductivity

Solution Approach 1:

The patent extracts the protocol conversion and data transmission functions from the main control unit and places them in a dedicated communication receiver. This extraction reduces the processing load on the main control unit by offloading protocol stack operations to the communication receiver, which is optimized for these specific tasks.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The communication receiver performs preliminary actions by pre-converting data into the appropriate service-oriented protocol formats before transmission. It handles protocol conversion, data formatting, and transmission preparation in advance, so that when data needs to be transmitted, the main control unit only needs to provide raw data without waiting for complex conversions.

Inventive Principle:
Principle #10Preliminary action

3Adaptability or versatility

If multiple protocol conversions are performed to support various communication standards, then compatibility is improved, but processing time and complexity increase

Engineering Contradiction:
Improveprotocol compatibilityVSAvoiddata conversion time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The communication receiver is designed with multi-functionality to handle multiple communication protocols (CAN, LIN, MOST, FlexRay, Ethernet) simultaneously. It contains protocol conversion capabilities for all these standards within a single integrated unit, allowing it to convert data between different protocols efficiently without requiring separate conversion processes for each protocol type.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The system replaces complex mechanical/software-based protocol conversion processes with optimized hardware-level conversion mechanisms in the communication receiver. By implementing protocol conversions at the hardware level rather than through software processing in the main control unit, conversion speed is significantly improved while maintaining support for multiple protocols.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

Data Source

PatentUS20250219865A1Communication receiver
Publication Date: 2025.07.03 DENSO CORP
  • US20250219865A1 patent drawing
  • US20250219865A1 patent drawing
  • US20250219865A1 patent drawing

AI summary

A communication receiver is connected to a main control unit of a communication device, and includes a first IF, a second IF, a service control unit, and a service IF unit. The service control unit transmits a search message to the electronic control unit conforming to the first protocol, which is a service communication protocol, based on the first setting information received from the main control unit via the first IF. The service IF unit converts an event message conforming to the first protocol or the second protocol received from the electronic control device into stream data based on the second setting information received from the main control unit via the first IF, and transmits the stream data to the main control unit via the second IF.