CAN-Based Service Architecture for Powersports Vehicle Controllers
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing vehicle communication architectures, such as SOME/IP, are limited to IP networks and do not support service-oriented communication for non-diagnostic features in controller area networks (CAN), restricting the implementation of vehicle-wide features.
Innovation Solution
Implement a service-oriented architecture in powersports vehicles using Unified Diagnostic Services (UDS) over a CAN bus, enabling a vehicle controller to discover and communicate with component controllers, allowing for publish/subscribe and request/response methods, and utilizing existing communication protocols like ISO 14229 and ISO 15765 to coordinate vehicle-wide features.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If SOME/IP service-oriented architecture is used, then service-based messaging is enabled, but it is limited to IP networks and cannot be applied to CAN bus
Solution Approach 1:
The patent uses UDS (Unified Diagnostic Services) as an intermediary protocol that operates over CAN bus, enabling service-oriented architecture functionality without requiring IP network infrastructure. The UDS protocol acts as a mediator that translates service-based communication requirements into CAN-compatible diagnostic messages, allowing SOME/IP-like service discovery and communication patterns to function on traditional CAN networks.
2Adaptability or versatility
If traditional signal-based communication is used on CAN bus, then compatibility is maintained, but vehicle-wide features cannot be implemented
Solution Approach 1:
The patent implements a dual-mode communication architecture where the same CAN bus infrastructure supports both traditional signal-based communication and service-oriented UDS communication. The vehicle controller is configured to perform both discovery processes for service-based features and maintain conventional signal routing, allowing the system to universally support multiple communication paradigms without requiring separate network infrastructure.
3Productivity
If service-oriented architecture is implemented over CAN bus, then vehicle-wide features are enabled, but discovery and communication processes are required
Solution Approach 1:
The patent performs a discovery process during system initialization or startup, where the vehicle controller proactively identifies and catalogs available component controllers and their supported services on the CAN bus. This preliminary action creates a service registry that enables subsequent service-based communication to proceed efficiently without requiring repeated discovery operations, reducing the overhead complexity of implementing service-oriented architecture on CAN bus.
Data Source
AI summary
A powersports vehicle with a service-oriented architecture is provided. In example aspects, a vehicle controller connected to a CAN bus performs a discovery process to identify vehicle component controllers on the CAN bus and the capabilities thereof. Based on the discovered capabilities of the vehicle component controllers, the vehicle controller can control communication with the vehicle component controllers to implement vehicle-wide features. For example, the discovery process may enable publish/subscribe and request/response communication between the vehicle controller and the vehicle component controllers. These discovery and communication processes allow for a service-oriented architecture to be implemented over the CAN bus.