Vehicle Message Routing via Directionality Bit
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current vehicle message routing systems rely on databases to identify ECUs on CAN buses, which can be inefficient, especially when messages need to be widely broadcast or routed between multiple networks, and lack flexibility in module placement.
Innovation Solution
A processor-based system that uses a directionality bit in the CAN identifier to route telematics messages to either all non-backbone networks or pre-identified backbone networks, allowing for flexible routing strategies without the need for a global master reference database.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a database is used to identify ECUs on CAN buses, then message routing can be managed, but routing efficiency decreases and flexibility in module placement is reduced
Solution Approach 1:
The patent extracts the routing logic from the database lookup approach and embeds it directly in the CAN identifier structure. The gateway processor examines specific bits within the CAN identifier itself (such as the directionality bit and network identifier bits) to determine routing decisions, eliminating the need to query external database tables for each routing decision.
Solution Approach 2:
The routing information is pre-encoded into the CAN identifier structure before messages are transmitted. The directionality bit and network identifier bits are set in advance within the identifier, allowing the gateway processor to make immediate routing decisions based on pre-configured rules associated with specific bit patterns, rather than looking up routing information during message transmission.
2Reliability
If CAN messages are widely broadcast to all vehicle networks, then intended modules can receive messages, but routing complexity increases
Solution Approach 1:
The patent applies different routing behaviors based on the value of the directionality bit in the CAN identifier. When the directionality bit indicates backbone routing, messages are routed only to pre-identified backbone networks. When it indicates non-backbone routing, messages are broadcast to all networks. This localized differentiation based on identifier bits simplifies the overall routing logic while ensuring reliable delivery to intended modules.
3Productivity
If signals are sent directly to module addresses, then routing is efficient, but adaptability to dynamic module placement is reduced
Solution Approach 1:
The patent enables dynamic module placement by using the network identifier bits in the CAN identifier to indicate which network an ECU resides on. The gateway processor uses these bits to dynamically determine the appropriate network for routing messages, allowing ECUs to be moved between networks without requiring updates to fixed address mappings or database tables. The routing adapts dynamically based on the identifier information.
Data Source
AI summary
A system includes a processor configured to route a telematics message to all networks not pre-identified as backbone networks in response to a directionality bit, included in a CAN identifier, indicating non-backbone routing. The processor is also configured to route the telematics message to any pre-identified backbone networks in response to the directionality bit indicating backbone routing.