Plugin Loading via Host Component Identifier Substitution
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current plugin framework solutions for terminals face challenges such as increased development costs, lack of system component attributes, and poor adaptation to new operating systems, leading to inefficient plugin loading and user experience issues.
Innovation Solution
A method and apparatus that utilize a child class threading module to replace the original parent class component function, allowing the plugin component to bypass system permission verification and run as a system component, ensuring high adaptation and stability by replacing the plugin component's identifier with a host component's identifier and performing system permission verification.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a conventional plugin framework solution is used, then the plugin App can be loaded, but the plugin App lacks system component attributes and requires modification to meet scheduling requirements, increasing development costs
Solution Approach 1:
The patent introduces a threading module as an intermediary between the plugin App and the system. This threading module acts as a mediator that schedules and manages the plugin component, allowing the plugin to run with system component attributes without requiring modification of the plugin App itself. The threading module handles the scheduling requirements while the plugin maintains its original form, thus resolving the contradiction between adaptability and development cost.
2Adaptability or versatility
If a DroidPlugin plugin framework solution is used, then the plugin App can run, but there is large adaptation risk in newly released versions of operating systems, requiring large adaptation costs
Solution Approach 1:
The threading module is designed with universal functionality that can adapt to different versions of operating systems. It implements a standardized interface and scheduling mechanism that works across various OS versions, reducing adaptation risk. The threading module handles version-specific variations internally while maintaining consistent behavior for the plugin, thus improving reliability across different operating system environments.
3Reliability
If the plugin component identifier is replaced with host component identifier for verification, then system permission verification can be performed, but the original plugin identifier must be preserved for proper plugin loading
Solution Approach 1:
The patent performs preliminary actions by recording the original plugin component identifier before replacement. This recorded identifier is preserved and used later when the plugin needs to be loaded. The temporary replacement with host component identifier is used only for verification purposes, while the original identifier is kept safe for the actual plugin loading process, thus managing identifier complexity while ensuring verification reliability.
Data Source
AI summary
The present disclosure discloses a method for plugin loading. The method includes obtaining an identifier of a plugin component of a plugin from a threading module, recording the identifier of the plugin component, and replacing the identifier of the plugin component with an identifier of a host component of an application program. The method also includes sending the identifier of the host component to a threading module, to perform system permission verification and receiving runnable notification information when passing the verification. The method further includes in response to the received runnable notification information, replacing the identifier of the host component with the identifier of the plugin component according to the recorded identifier of the plugin component; and sending the identifier of the plugin component to the threading module, to load the plugin. The present invention further discloses an apparatus and a storage medium for plugin loading.