Plug-in Installation via Major Version Matching
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing plug-in installation methods for Android App Bundles require all plug-ins to have the same version number as the plug-in framework, limiting flexibility and user experience by necessitating the installation of all plug-ins when only one is needed.
Innovation Solution
An electronic device allows for the installation of plug-ins with the same major version number as the plug-in framework, even if the sub or phase version numbers differ, enabling flexible installation and separate downloading of different plug-ins based on user requirements.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If all plug-ins are required to have the same version number as the plug-in framework, then version consistency is maintained, but installation flexibility and user experience deteriorate
Solution Approach 1:
The version number is segmented into major version number and sub version number. The patent allows comparison and matching only on the major version number level, while permitting different sub version numbers. This segmentation resolves the contradiction by maintaining consistency at the critical major version level while allowing flexibility at the less critical sub version level, enabling selective plug-in installation without requiring complete version parity across all components.
2Reliability
If all plug-ins must be installed together, then version compatibility is ensured, but download time and data usage increase
Solution Approach 1:
The patent extracts the version comparison requirement from the context of installing all plug-ins and applies it selectively to individual plug-ins. By checking major version number compatibility independently for each plug-in against the plug-in framework, the system allows users to install only the specific plug-ins they need rather than forcing installation of entire plug-in bundles. This extraction principle reduces download time and data usage while maintaining version compatibility through targeted verification.
3Stability of the object's composition
If complete version matching is required, then system stability is maintained, but upgrade flexibility and compatibility improve
Solution Approach 1:
The patent applies different quality requirements to different parts of the version number structure. The major version number is treated with strict equality requirements to ensure system stability and compatibility, while the sub version number is treated with greater flexibility, allowing differences without preventing installation. This local quality differentiation resolves the contradiction by maintaining stability where it matters most (major version compatibility) while enabling upgrade flexibility in less critical areas (sub version variations).
Data Source
AI summary
An electronic device receives a first user operation. The first user operation is used to request to install a first plug-in related to a first application, the first application includes a first plug-in framework and at least one plug-in associated with the first plug-in framework, a major version number of each of the at least one plug-in is the same as a major version number of the first plug-in framework, and the first plug-in is different from the at least one plug-in. The electronic device receives the first plug-in from a server. The electronic device detects whether a major version number of the first plug-in is the same as the major version number of the first plug-in framework. If yes, the electronic device installs the first plug-in.