Application Installation Packages Using Static Linking and Difference Content
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Users face difficulties in flexibly performing operations such as installation or uninstallation of applications on terminal devices, leading to poor user experience.
Innovation Solution
A method for generating application installation packages that involves recognizing difference content after merging a source component with a base version component, adding redirection information to ensure non-conflicting storage addresses, and statically linking the content to generate an installation package that can be independently loaded and installed on the terminal device, reducing dependency on the running framework and maintaining the original static linking relationship.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If the application is integrated into the operating system as a source project, then the application can be loaded and run, but the user cannot flexibly perform installation or uninstallation operations
Solution Approach 1:
The patent segments the application from the operating system by extracting the application as a separate installable package. The application is compiled and statically linked with the base version component to generate an installation package that can be independently managed, allowing users to install and uninstall the application without affecting the operating system core.
Solution Approach 2:
The patent extracts the application component from the integrated source project structure and packages it as a separate installable unit. By taking out the application as an independent installation package, the system enables flexible installation and uninstallation operations while maintaining the application's functional integration with the operating system.
2Ease of operation
If the application installation package includes all content from the source project, then the application can run independently, but the installation package size becomes large with redundant information
Solution Approach 1:
The patent extracts only the difference content between the application and the base version component, rather than including the entire source project. This extraction approach allows the application to be packaged as a smaller installation package while maintaining independence, as the base version component is already present in the operating system.
Solution Approach 2:
The patent merges the difference content with redirection information that references the base version component in the operating system. This combining approach allows the application to function independently while sharing common code and resources with the base version, reducing redundancy and package size.
3Productivity
If the application shares address space with the base version component, then memory utilization is efficient, but address conflicts occur affecting system stability
Solution Approach 1:
The patent segments the address space by allocating a separate first link address range for the application that does not conflict with the second link address range of the base version component. This segmentation prevents address conflicts and ensures system stability while maintaining efficient memory utilization through proper address space management.
Solution Approach 2:
The patent introduces redirection information as an intermediary layer between the application and the base version component. This redirection mechanism allows the application to access necessary resources while maintaining distinct address ranges, preventing direct address conflicts and ensuring system reliability.
Data Source
Figure 1~2
Figure 3
Figure 4
AI summary
This application discloses an application installation package generation method, an application installation method, and a related device. In a static linking condition, a server may compile archived images of a plurality of versions of an application at a plurality of preset locations based on a source project component and a source component of the application, and a terminal device may apply to the server for an archived image of a corresponding version based on an existing storage space status, and implement downloading, verification, installation, uninstallation, and the like of the archived image. In this way, the terminal device can independently load an application. A static linking relationship of the application is kept consistent with that of a source project, and the original static linking relationship of the source project is not affected. In addition, because the source component of the application and the source project component participate in static linking together, an existing code segment and data segment of the source project can be reused. Therefore, the archived image of the application may include only content different from that of the source project. This reduces a size of the archived image of the application, improves downloading and installation efficiency, and improves user experience.