Gateway Software Package Structure for Multi-Controller ROM Updates
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Software developers face challenges in customizing updates for various controllers due to differing memory areas, write and delay times, and relay schemes, making it difficult to predict and respond to future reprogramming schemes.
Innovation Solution
A computer-readable storage medium and gateway system that generates a standardized software package with a binary file, configuration file, and hash file, enabling transmission of ROM data across controllers using a unified update procedure, irrespective of specific reprogramming schemes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If software developers customize update software for each controller type, then update accuracy and reliability are improved, but development complexity and time consumption increase
Solution Approach 1:
The patent creates a universal update file structure that can be used across different controller types. The configuration file contains controller-specific parameters (memory address, write delay time, scheme type) that allow the same update software to adapt to various controllers without customization, achieving multi-functionality while maintaining reliability through parameterized configuration.
Solution Approach 2:
The patent uses parameter changes to resolve the contradiction by storing controller-specific characteristics (memory area, write delay time, reprogramming scheme) as configurable parameters in the configuration file. This allows the update system to maintain a unified structure while adapting to different controllers by changing parameters rather than rewriting the entire update software.
2Reliability
If gateway relays software differently for each controller, then update accuracy is improved, but gateway complexity increases
Solution Approach 1:
The patent applies local quality by placing controller-specific update parameters (memory address, write delay time, scheme type) in a localized configuration file section. The gateway reads these localized parameters for each controller type and applies them accordingly, maintaining simple gateway logic while achieving accurate updates for each controller through localized configuration data.
3Adaptability or versatility
If developers predict future reprogramming schemes, then adaptability is improved, but prediction accuracy and response time worsen
Solution Approach 1:
The patent implements dynamics by making the update system adaptable to future reprogramming schemes through a configurable parameter structure. When a new controller type or scheme emerges, only the configuration file needs to be updated with new parameters, not the entire update software. This dynamic adaptability eliminates prediction needs and enables immediate response to new schemes.
4Ease of manufacture
If a unified update scheme is used for all controllers, then development complexity is reduced, but update accuracy for specific controllers deteriorates
Solution Approach 1:
The patent resolves this contradiction by using parameter changes to customize updates for specific controllers within a unified software structure. The configuration file contains controller-specific parameters (memory address, write delay time, scheme type) that are changed based on the target controller, allowing a single update program to achieve controller-specific accuracy through parameter variation rather than code customization.
Data Source
AI summary
A software package, a gateway for transmitting the same, and a software update method using the same are provided. A software package includes a binary file, a configuration file, and a hash file. The binary file includes read-only memory (ROM) data of a target controller. A management server generates the configuration file by combining a hash value obtained by hashing the binary file with meta information indicating an update procedure between a gateway and the target controller. The management server generates the hash file by hashing the configuration file. The gateway receives the software package and extract the binary file and the configuration file. The gateway transmits the binary file to the target controller according to the update procedure indicated by the meta information.