Vehicle User Setting Menu Updates via CAN-to-SOA Conversion
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing vehicle systems lack the ability to efficiently manage and update user setting menus for new functions added post-production without requiring software updates of the controller managing the menu, limiting flexibility and responsiveness to market changes.
Innovation Solution
A method and configuration involving a conversion controller that acquires and converts existing function information into a Service-Oriented Architecture-compatible protocol, allowing a head unit controller to update the user setting menu without updating the software of system controllers, using a network protocol conversion between CAN and Ethernet/SOME/IP protocols.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If software of the controller managing the user setting menu is updated to support new functions, then the user setting menu can be provided for new functions, but the complexity of software updates and system integration increases
Solution Approach 1:
The patent segments the user setting menu management into two independent parts: (1) the head unit controller that manages the USM interface, and (2) the system controllers that provide function-specific setting information. This segmentation allows the head unit to remain unchanged while system controllers are updated with new functions, resolving the contradiction between adaptability and software complexity.
Solution Approach 2:
The head unit controller is designed with universal functionality to manage user setting menus for both existing and new functions without requiring software updates. It receives function-specific setting information from various system controllers through a standardized protocol, enabling it to adapt to new functions while maintaining its core management capabilities.
2Adaptability or versatility
If traditional fixed-function vehicle systems are used, then development and production are simpler, but the vehicle cannot flexibly respond to market changes and add new functions post-production
Solution Approach 1:
The patent implements a dynamic architecture where the user setting menu is not fixed at production time but can be dynamically updated. The head unit controller receives real-time function information from system controllers through a network protocol, allowing the vehicle to adapt to market changes by adding new functions without retooling or complex reintegration, thus maintaining ease of manufacture while gaining flexibility.
Solution Approach 2:
The head unit controller acts as an intermediary between the user interface and multiple system controllers. It receives standardized function information from various controllers and presents a unified user setting menu, enabling flexible addition of new functions through simple controller integration without affecting the overall system architecture or manufacturing complexity.
3Adaptability or versatility
If protocol conversion is implemented to enable SOA-based communication, then new functions can be added flexibly, but the complexity of network communication and data conversion increases
Solution Approach 1:
The head unit controller serves as a protocol conversion intermediary, receiving function setting information from system controllers using existing protocols and converting it into a standardized SOA-based format for unified management. This intermediary approach enables flexible function addition through SOA while isolating the protocol conversion complexity to a single component rather than requiring all controllers to handle multiple protocols.
Data Source
AI summary
A vehicle and a method of managing a user setting menu (USM) enables the vehicle to add a new function after production of the vehicle so as to effectively manage the USM. The method includes: acquiring, by a conversion controller, first setting information about at least one existing function from a system controller through a first network using a first protocol; converting, by the conversion controller, the first setting information into second setting information using a second protocol; transmitting the converted second setting information to a head unit controller to manage the USM through a second network; transmitting third setting information about a one new function from a connectivity controller to the head unit controller through the second network, and updating, by the head unit controller, the USM based on the second and third setting information.