Ghost Entries for Software Version Compatibility
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Software upgrades and downgrades become impractical due to the accumulation of unused conversion programs, leading to inefficiencies and potential system malfunctions, especially when updating from older versions with many intervening changes.
Innovation Solution
The introduction of 'ghost' conversion entries that ignore or remove unsupported configuration programs, allowing for finer granularity in software version management by distinguishing between active and ghost entries, thereby simplifying and increasing the reliability of the upgrade and downgrade processes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If software upgrade programs include all conversion programs for every version, then compatibility with all versions is improved, but device complexity and processing burden increase significantly
Solution Approach 1:
The patent segments the conversion programs by version number, organizing them in a hierarchical structure where each version has its own dedicated conversion program. This allows the system to selectively apply only the necessary version-specific conversion programs rather than loading all possible conversions, thus maintaining compatibility while reducing complexity.
Solution Approach 2:
The patent implements preliminary action by pre-configuring version-specific conversion programs and using a version number stored in the configuration program file to automatically select and apply the appropriate conversion program before the software runs. This eliminates the need to process all possible version conversions during execution.
2Reliability
If software upgrade programs process all configuration entries, then completeness of conversion is improved, but processing time and system resources increase
Solution Approach 1:
The patent applies local quality by making the conversion program file structure adaptable to different version requirements. Each version-specific conversion program only processes configuration entries relevant to its target version, allowing the system to maintain complete conversion coverage while minimizing unnecessary processing of irrelevant configuration entries.
Solution Approach 2:
The patent implements dynamics by making the conversion process adaptive based on the stored version number. The system dynamically selects which conversion program to execute and which configuration entries to process, rather than following a static all-inclusive conversion approach. This reduces processing time while ensuring all necessary conversions are completed.
3Ease of operation
If old configuration entries are retained for backward compatibility, then ease of operation is improved, but software corruption risk increases
Solution Approach 1:
The patent extracts and removes obsolete configuration entries that are no longer supported by the current software version. By selectively eliminating only the unsupported entries while preserving necessary backward compatibility through version-specific conversion programs, the system reduces corruption risk without significantly impacting ease of operation.
Solution Approach 2:
The patent converts the potential harm of obsolete configuration entries into a benefit by using them as version identifiers. The version number stored in configuration program files is used to automatically select the appropriate conversion program, transforming what could be source of corruption into a mechanism for ensuring compatibility and safe updates.
Data Source
AI summary
Methods and systems for modifying software programs are disclosed. For instance, an example method for modifying a software program may include extracting, from a configuration program file, a future list of one or more future active entries relating to a future version of the software program and a future list of one or more future ghost entries relating to the future version of the software program, comparing the future lists of future active and ghost entries to current lists of current active entries and current ghost entries of a current version of the software program. Then, at least one upgrade or at least one downgrade of the current version of the software program is performed in response the comparison of the current and future lists.