Component Installation State Management for Wireless Terminals
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing solutions for managing Look-and-Feel Customization (LFC) packages in wireless terminals do not prevent repeated installation of removed components, leading to inefficient resource usage and user dissatisfaction.
Innovation Solution
A processing method and system that sets and stores state information for removed components, allowing the terminal to determine operations based on this information, preventing repeated downloads or installations by comparing component versions and deadlines, and automatically removing information when specified.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the SP server checks the installation state of components periodically, then the server can monitor terminal status, but removed components are re-installed repeatedly causing resource waste
Solution Approach 1:
The terminal performs preliminary actions by setting state information for removed components before the server checks. This allows the terminal to proactively mark removed components with specific state information, so when the server queries later, it can identify these components as removed and avoid re-installation, thus preventing wasted network bandwidth and processing resources.
2Reliability
If state information is stored permanently for removed components, then repeated installation can be prevented, but storage space is wasted on futile information
Solution Approach 1:
Instead of permanent storage, the system uses periodic action by setting state information with associated deadlines. The terminal and server periodically check whether the current time exceeds the deadline for removed components. If the deadline is exceeded, the state information is cleared. This allows prevention of repeated installation within the valid period while automatically cleaning up stale data to free storage space.
3Quantity of substance
If the node corresponding to LFC package is removed when software is removed, then memory is freed, but the server cannot distinguish between removed and never-installed components
Solution Approach 1:
The system segments the component management into two independent parts: (1) the LFC package node in the content management tree, which can be removed to free memory, and (2) the state information record, which is stored separately with a deadline. This segmentation allows the package node to be removed for memory efficiency while the separate state information record preserves the installation history needed for the server to distinguish removed components from never-installed ones.
Data Source
Figure 1~2
Figure 3
Figure 4
AI summary
A processing method, a system, and an apparatus for component installation are disclosed herein. The processing method includes: receiving a component delivered by a server; and determining operations to be performed on the delivered component according to state information set for a removed component or information about the removed component. After the component is removed, the state information of the removed component or information about the component is set and stored, and the operations to be performed on a subsequent component are determined accordingly, thus preventing repeated installation of the removed component. Moreover, a deadline of storing the removed component information is set so that the information about the component can be removed automatically upon arrival of the deadline.