Versioning Schema for Wireless Software Update Compatibility
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The complexity of implementing software updates on wireless terminal devices is high due to intermittent connectivity, resource constraints, and the need for ordered installation of updates, which existing methods struggle to manage effectively.
Innovation Solution
A method and system for controlling software updates on wireless devices using a versioning schema and update scripts, where an update notification message with a software identifier, version number, and script address is used to install updates asynchronously, ensuring compatibility and controlled distribution across multiple devices.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If software updates are released frequently to resolve defects and provide new functions, then software utility and reliability are improved, but the complexity of implementing updates on wireless devices increases due to intermittent connectivity, resource constraints, and installation ordering requirements
Solution Approach 1:
The version number is segmented into multiple fields (e.g., major version, minor version, patch version) where each field represents a different aspect of the software update. This segmentation allows the system to track and manage different types of changes independently, enabling complex update scenarios to be broken down into manageable version increments that can be handled separately.
Solution Approach 2:
The system performs preliminary actions by establishing a comprehensive versioning scheme before updates are released. The version number structure is predefined with specific fields that capture compatibility information, installation ordering requirements, and dependency relationships. This preliminary framework enables automatic update management without requiring complex real-time coordination during the actual update process.
2Adaptability or versatility
If updates are downloaded and installed on devices with intermittent connectivity, then update availability is improved, but resource management becomes more difficult due to limited memory and processing power on wireless devices
Solution Approach 1:
The system changes parameters by using a structured version number that encodes resource requirements and installation conditions. Different version fields represent different parameter states (e.g., compatibility requirements, installation order, resource needs). This parameter encoding allows the device to automatically determine whether it has sufficient resources and appropriate conditions for installation without requiring complex external management.
3Reliability
If a series of application updates must be downloaded and installed in a particular order, then software compatibility is improved, but the time required for complete update installation increases
Solution Approach 1:
The version number structure provides feedback mechanisms where each version field indicates the state of the software and what updates have been applied. The system uses this feedback to determine installation ordering automatically - higher version fields indicate updates that should be installed first, and lower fields indicate subsequent updates. This feedback-driven approach eliminates the need for complex external scheduling while maintaining compatibility.
Data Source
AI summary
A versioning schema enforced by the application development environment enables the runtime environment of a terminal device to evaluate a software update to identify potential compatibility issues and control installation of the update. The versioning schema includes a respective field for each one of a plurality of aspects of the application and defines an initial value of each field when an initial application load is released. For each successive software update affecting the application, the method involves identifying each aspect of the application affected by the software update and incrementing a value of the respective field of each identified aspect. The version number can be in the form D.M.F where D, M and F are incremented in response to changes in the application relating to data components, message components and features.