Gateway RXSWIN Management for Vehicle Software Updates
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The challenge lies in managing software updates for vehicles, particularly in ensuring correct updates across multiple electronic control units (ECUs) and compliance with regulations like UNECE's R156, which requires secure software updates and unique identification of software versions to prevent unauthorized changes and ensure security and type approval.
Innovation Solution
A vehicle control apparatus and system that includes an RXSWIN information management system, which configures, generates, and updates software identification management information, ensuring compliance with UNECE regulation R156 by using a gateway to manage and update software identification information, verify updates, and maintain a master list of software versions, while preventing unauthorized changes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If software updates are performed manually for each ECU, then development convenience is maintained, but update time and complexity increase significantly
Solution Approach 1:
A gateway is introduced as an intermediary component between ECUs and the external environment. The gateway centralizes software identification information management, automatically receives update information, manages version control, and coordinates updates across multiple ECUs. This intermediary approach eliminates manual update processes while maintaining system manageability, directly resolving the contradiction between update efficiency and management complexity.
2Reliability
If software updates are performed without systematic management, then update flexibility is maintained, but link verification between ECUs becomes difficult and unnecessary checks increase
Solution Approach 1:
The system implements feedback mechanisms where the gateway continuously monitors software identification information from ECUs, compares it against update information, and verifies update completion status. This automated feedback loop ensures reliable update verification and link checking between ECUs without requiring complex manual verification processes, thereby improving reliability while reducing verification complexity.
3Adaptability or versatility
If RXSWIN information is not systematically managed, then system simplicity is maintained, but compliance with UNECE regulation R156 cannot be achieved
Solution Approach 1:
The gateway is configured to preliminarily establish and maintain a structured database of software identification information (RXSWIN) for all ECUs before updates occur. This preliminary organization of information including version numbers, identification strings, and ECU mappings enables the system to meet UNECE R156 compliance requirements without adding complex management structures during operation, as the framework is already in place.
4Productivity
If software identification information is not centralized, then individual ECU independence is maintained, but master list management and version control become inefficient
Solution Approach 1:
The gateway merges software identification information from multiple independent ECUs into a centralized master list. This consolidation combines version numbers, identification strings, and update status information into a single manageable structure. The merging approach improves version management efficiency by providing a unified view of all software states while the gateway's automated management minimizes the operational complexity of this centralized structure.
Data Source
AI summary
A vehicle control apparatus and a vehicle control system including the same are provided. The vehicle control apparatus includes an electronic control unit and a gateway. The electronic control unit is configured to store software identification management information associated with the electronic control unit. The gateway is configured to store a master list of the software identification management information, which includes the software identification management information received from the electronic control unit, deliver update information related to software associated with vehicle type approval (VTA) to the electronic control unit corresponding to the update information, as the update information is received, and update the software identification management information associated with the electronic control unit in the master list as an update of the software of the electronic control unit is completed.