CN112825035A

CN112825035A - Program installation file generating and processing method and device

Info

Publication number: CN112825035A
Application number: CN201911151009.1A
Authority: CN
Inventors: 范金松
Original assignee: Beijing Sogou Technology Development Co Ltd
Current assignee: Beijing Sogou Technology Development Co Ltd
Priority date: 2019-11-21
Filing date: 2019-11-21
Publication date: 2021-05-21

Abstract

The embodiment of the application discloses a method and a device for generating and processing a program installation file. And finally, packing the non-to-be-compressed files in the files to be packed and the first dynamic library file to generate a first program installation file. Namely, for a larger file in the files to be packaged, namely the file to be compressed, a compression algorithm with a high compression ratio can be adopted for compression operation, so that the files to be compressed are greatly reduced, and further the first program installation file after packaging is reduced. When a user needs to install the application program corresponding to the first program installation file, the first program installation file can be directly downloaded, and because the first program installation file is small, network resources can be saved, and the installation rate is improved.

Description

Program installation file generating and processing method and device

Technical Field

The application relates to the technical field of internet, in particular to a method and a device for generating and processing a program installation file.

Background

In an Android (Android) platform, all files of an application program can be compiled and packaged into an Android Application Package (APK) executable file in an APK format, the APK file can be used for distributing and installing the application program based on the Android platform and continuously upgrading and iterating along with projects, codes and resources are accumulated, the APK file is made to be larger and larger, when a user obtains the APK file, not only flow resources are consumed, but also downloading time is prolonged, the installation rate of the application program is reduced, and the use experience of the user is influenced.

Disclosure of Invention

In view of this, embodiments of the present disclosure provide a method and an apparatus for generating and processing a program installation file, so as to reduce the program installation file, increase the download rate of the program installation file, and save network resources.

In order to solve the above problem, the technical solution provided by the embodiment of the present application is as follows:

a method of generating a program installation file, the method comprising:

determining a file to be compressed in the file to be packaged;

performing first compression operation on the file to be compressed in a preset compression mode to generate a compressed file;

converting the compressed file into a first dynamic library file;

and packaging the non-to-be-compressed files in the files to be packaged and the first dynamic library file to generate a first program installation file.

In a possible implementation manner, the determining a file to be compressed in the files to be packaged includes:

acquiring a predefined file to be compressed in the file to be packaged;

and/or the presence of a gas in the gas,

and acquiring the file size of each file to be packaged, and determining the file to be packaged with the file size exceeding a threshold value as the file to be compressed.

In one possible implementation manner, before determining the file to be compressed in the file to be packaged, the method further includes:

and compiling the class files to generate android executable files, determining the android executable files as files to be packaged, or decompressing the second program installation files to obtain the android executable files, and determining the android executable files as files to be packaged.

In a possible implementation manner, when the file to be compressed is a file of a dynamic library type, the converting the compressed file into a first dynamic library file includes:

deleting the last-stage extension of the compressed file to obtain a first dynamic library file;

when the file to be compressed is a file of a non-dynamic library type, the converting the compressed file into a first dynamic library file includes:

and replacing the last-stage extension of the compressed file with an extension of a dynamic library type to obtain a first dynamic library file.

In a possible implementation manner, the generating a first program installation file by performing a packing operation on a non-to-be-compressed file in the files to be packed and the first dynamic library file includes:

performing second compression operation on a second dynamic library file in non-to-be-compressed files in the files to be packaged and the first dynamic library file to generate a third dynamic library file;

and performing packing operation on other files which are not to be compressed and the third dynamic library file to generate a first program installation file.

A method of processing program installation files, the method comprising:

unpacking the program installation file to obtain a first dynamic library file;

and performing first decompression operation on the first dynamic library file by adopting a preset decompression mode.

In a possible implementation manner, the unpacking the program installation file to obtain the first dynamic library file includes:

unpacking the program installation file to obtain a third dynamic library file;

and determining a first dynamic library file from the third dynamic library file.

In one possible implementation manner, the determining the first dynamic library file from the third dynamic library file includes:

and performing second decompression operation on the third dynamic library file, and identifying a first dynamic library file from the files of the dynamic library types obtained by the second decompression operation.

In a possible implementation manner, the performing a first decompression operation on the first dynamic library file by using a preset decompression manner includes:

identifying an original file type corresponding to the first dynamic library file;

when the original file type corresponding to the first dynamic library file is identified as the dynamic library type, directly performing first decompression operation on the first dynamic library file in a preset decompression mode to obtain a file of the dynamic library type;

and when the original file type corresponding to the first dynamic library file is identified to be a non-dynamic library type, performing first decompression operation on the first dynamic library file in a preset decompression mode, and deleting the last-level extension of the file of the dynamic library type obtained by the first decompression operation to obtain the file of the original file type.

In a possible implementation manner, the identifying an original file type corresponding to the first dynamic library file includes:

inquiring the corresponding original file type according to the file name corresponding to the first dynamic library file;

alternatively, the first and second electrodes may be,

identifying a file type flag bit in the first dynamic library file, and determining an original file type corresponding to the first dynamic library file;

alternatively, the first and second electrodes may be,

when the first dynamic library file only comprises an extension of a dynamic library type, identifying that an original file type corresponding to the first dynamic library file is the dynamic library type, and when the first dynamic library file comprises the extension of the dynamic library type and the extension of a non-dynamic library type, identifying the original file type corresponding to the first dynamic library file according to the included extension of the non-dynamic library type.

An apparatus for generating a program installation file, the apparatus comprising:

the determining unit is used for determining a file to be compressed in the file to be packaged;

the first generation unit is used for performing first compression operation on the file to be compressed in a preset compression mode to generate a compressed file;

the conversion unit is used for converting the compressed file into a first dynamic library file;

and the second generating unit is used for performing packaging operation on the non-to-be-compressed file in the files to be packaged and the first dynamic library file to generate a first program installation file.

In a possible implementation manner, the determining unit is specifically configured to obtain a predefined file to be compressed in the file to be packaged; and/or obtaining the file size of each file to be packaged, and determining the file to be packaged with the file size exceeding a threshold value as the file to be compressed.

In one possible implementation, the apparatus further includes:

a third generating unit, configured to compile the class file to generate an android executable file before executing the determining unit, determine the android executable file as a file to be packaged, or,

and the obtaining unit is used for decompressing the second program installation file to obtain the android executable file, and determining the android executable file as a file to be packaged.

In a possible implementation manner, when the file to be compressed is a file of a dynamic library type, the conversion unit is specifically configured to delete the last-level extension of the compressed file to obtain a first dynamic library file;

when the file to be compressed is a file of a non-dynamic library type, the conversion unit is specifically configured to replace the last-stage extension of the compressed file with an extension of a dynamic library type, so as to obtain a first dynamic library file.

In a possible implementation manner, the second generating unit specifically includes:

the first generating subunit is configured to perform a second compression operation on a second dynamic library file in non-to-be-compressed files in the files to be packaged and the first dynamic library file, and generate a third dynamic library file;

and the second generation subunit is used for performing packaging operation on other files which are not to be compressed and the third dynamic library file to generate a first program installation file.

A program installation file processing apparatus, the apparatus comprising:

the unpacking unit is used for unpacking the program installation file to obtain a first dynamic library file;

and the decompression unit is used for performing first decompression operation on the first dynamic library file in a preset decompression mode.

In one possible implementation manner, the unpacking unit includes:

the unpacking subunit is used for unpacking the program installation file to obtain a third dynamic library file;

and the determining subunit is used for determining the first dynamic library file from the third dynamic library file.

In a possible implementation manner, the determining subunit is specifically configured to perform a second decompression operation on the third dynamic library file, and identify the first dynamic library file from the files of the dynamic library type obtained through the second decompression operation.

In one possible implementation, the decompression unit includes:

the identification subunit is used for identifying the original file type corresponding to the first dynamic library file;

the first decompression sub-unit is used for directly performing first decompression operation on the first dynamic library file in a preset decompression mode to obtain a file of the dynamic library type when the original file type corresponding to the first dynamic library file is identified as the dynamic library type;

and the second decompression subunit is configured to, when it is identified that the original file type corresponding to the first dynamic library file is a non-dynamic library type, perform a first decompression operation on the first dynamic library file in a preset decompression manner, and delete the last-level extension of the file of the dynamic library type obtained through the first decompression operation, to obtain a file of the original file type.

In a possible implementation manner, the identifying subunit is specifically configured to query a corresponding original file type according to a file name corresponding to the first dynamic library file; or identifying a file type flag bit in the first dynamic library file, and determining an original file type corresponding to the first dynamic library file; or, when the first dynamic library file only includes an extension of a dynamic library type, identifying that an original file type corresponding to the first dynamic library file is a dynamic library type, and when the first dynamic library file includes an extension of a dynamic library type and an extension of a non-dynamic library type, identifying an original file type corresponding to the first dynamic library file according to the included extension of the non-dynamic library type.

A generation apparatus for a program installation file, comprising a memory, and one or more programs, wherein the one or more programs are stored in the memory and configured for execution by one or more processors the one or more programs include instructions for:

determining a file to be compressed in the file to be packaged;

converting the compressed file into a first dynamic library file;

A computer readable medium having stored thereon instructions which, when executed by one or more processors, cause an apparatus to perform the method for generating a program installation file.

A processing device for program installation files, comprising a memory, and one or more programs, wherein the one or more programs are stored in the memory and configured for execution by one or more processors the one or more programs including instructions for:

unpacking the program installation file to obtain a first dynamic library file;

A computer readable medium having stored thereon instructions which, when executed by one or more processors, cause an apparatus to perform the method of processing a program installation file.

Therefore, the embodiment of the application has the following beneficial effects:

in the embodiment of the application, before the program installation file is generated by packaging, a file to be compressed in the file to be packaged is determined, a first compression operation is performed on the file to be compressed by adopting a preset compression mode, a compressed file is generated, and the compressed file is converted into a first dynamic library file. And finally, packing the non-to-be-compressed files in the files to be packed and the first dynamic library file to generate a first program installation file. Namely, for a larger file in the files to be packaged, namely the file to be compressed, a compression algorithm with a high compression ratio can be adopted for carrying out first compression operation, so that the files to be compressed are greatly reduced, and further, the first program installation file after packaging is reduced. When a user needs to install the application program corresponding to the first program installation file, the first program installation file can be directly downloaded, and because the first program installation file is small, network resources can be saved, and the installation rate and the user experience are improved.

Drawings

Fig. 1 is an embodiment of an application scenario provided in an embodiment of the present application;

fig. 2 is a flowchart of a method for generating a program installation file according to an embodiment of the present application;

FIG. 3 is a block diagram of a generation framework of a program installation file according to an embodiment of the present disclosure;

fig. 4 is a flowchart of a processing method for a program installation file according to an embodiment of the present application;

FIG. 5 is a block diagram of a processing framework for installing a file in a program according to an embodiment of the present application;

fig. 6 is a structural diagram of a device for generating a program installation file according to an embodiment of the present application;

fig. 7 is a structural diagram of a processing apparatus for program installation files according to an embodiment of the present application;

fig. 8 is a diagram illustrating a structure of a server according to an embodiment of the present application;

fig. 9 is a block diagram of another processing apparatus for program installation files according to an embodiment of the present application.

Detailed Description

In order to make the aforementioned objects, features and advantages of the present application more comprehensible, embodiments accompanying the drawings are described in detail below.

In order to facilitate understanding of the technical solutions provided in the present application, the following description will first be made on the background of the present application.

The inventor finds that the traditional reduction method mainly focuses on reducing useless resources, dividing dex files, removing redundant native libraries and the like in the research of the traditional APK file reduction method. The removing of the redundant native refers to generating a corresponding dynamic library (native library) file according to a CPU instruction set and removing an unnecessary native library file. For example, if there are different instruction sets such as x86, arm-v7, arm64-v8a, etc., a dynamic library file needs to be compiled for each instruction set, but if the number of android devices using the x86 instruction set is very small, the dynamic library file corresponding to the instruction set may not be provided, which may reduce the size of the installation file. However, with the continuous upgrading of the application program, the corresponding codes and resources are also continuously increased, and the traditional reduction method cannot effectively reduce the weight of the APK file, so that the downloading and installation of the APK file are influenced.

Based on this, the embodiment of the present application provides a method for generating a program installation file, where before generating the program installation file, a file to be compressed in a file to be packaged is determined, that is, a larger file in the file to be packaged is determined as the file to be compressed. Then, a preset compression mode is adopted to perform first compression operation on the file to be compressed, and a compressed file is generated. Namely, the larger file is compressed by adopting a preset compression method, so that the storage resource occupied by the larger file is reduced. Meanwhile, the compressed file is converted into a first dynamic library file, and the non-to-be-compressed file in the files to be packaged and the first dynamic file are packaged to generate a first program installation file. That is, by the method provided by the embodiment of the present application, a compression operation with a high compression ratio can be performed on a file to be compressed, so that a first program installation file generated by packaging is smaller, consumption of a user on network resources during installation is reduced, and an installation rate is increased.

To facilitate understanding of the embodiments of the present application, reference is made to fig. 1, which is a schematic diagram of a framework of an exemplary application scenario provided by the embodiments of the present application. The method for generating the program installation file provided by the embodiment of the present application may be applied to the server 20.

Specifically, the server 20 may obtain files to be packaged, and determine files to be compressed from the files to be packaged, that is, determine a large file to be compressed. Then, a preset compression mode is adopted to perform first compression operation on the file to be compressed, a compressed file is generated, and the compressed file is converted into a first dynamic library file. And then packing the non-to-be-compressed files in the files to be packed and the first dynamic library file to generate a first program installation file.

When the user installs the first program installation file using the terminal 10, the first program installation file may be downloaded locally from the server 20, and the first program installation file may be unpacked to obtain a first dynamic library file. Meanwhile, a preset decompression method is adopted to carry out first decompression operation on the first dynamic library file to obtain an operable file, and then installation of the application program is achieved.

Those skilled in the art will appreciate that the block diagram shown in fig. 1 is only one example in which embodiments of the present application may be implemented. The scope of applicability of the embodiments of the present application is not limited in any way by this framework.

It should be noted that the terminal 10 can be any user equipment now known, developing or later developed that is capable of interacting with each other via any form of wired and/or wireless connection (e.g., Wi-Fi, LAN, cellular, coaxial cable, etc.), including but not limited to: smart wearable devices, smart phones, non-smart phones, tablets, laptop personal computers, desktop personal computers, minicomputers, midrange computers, mainframe computers, and the like, either now in existence, under development, or developed in the future. The embodiments of the present application are not limited in any way in this respect. It should also be noted that the server 20 in the embodiment of the present application may be an example of an existing, developing or future developing device capable of providing the application download service to the user. The embodiments of the present application are not limited in any way in this respect.

In order to facilitate understanding of the technical solutions provided by the embodiments of the present application, the following describes a generation method provided by the embodiments of the present application with reference to the accompanying drawings.

Referring to fig. 2, which is a flowchart of a method for generating a program installation file according to an embodiment of the present application, as shown in fig. 2, the method may include:

s201: and determining a file to be compressed in the file to be packaged.

Before the files to be packaged are packaged, in order to reduce the storage space occupied by the packaged files, the files to be compressed are determined from the files to be packaged. In the Android platform, the files to be packaged may include class.

In specific implementation, this embodiment provides two implementation manners for determining a file to be compressed from files to be packaged, and one implementation manner is to acquire a predefined file to be compressed from the files to be packaged. That is, a user may predefine a file to be compressed, and then determine whether the file to be packaged includes a predefined file to be compressed, and if so, obtain the file to be compressed. For example, the predefined files to be compressed are files with extensions of. dex and. arsc, and if the files to be packaged comprise the. dex and. arsc files, the. dex and. arsc files are obtained and taken as the files to be compressed.

And the other method is to obtain the file size of each file to be packaged, and determine the file to be packaged, of which the file exceeds the threshold value, as the file to be compressed. Namely, a larger file in the files to be packaged is determined as a file to be compressed, wherein the larger file can be obtained through threshold screening.

It should be noted that, in practical application, one of the modes may be selected to determine the file to be compressed, or the two modes may be simultaneously used to determine the file to be compressed, and a specific selection mode may be determined according to a practical application situation, which is not limited herein.

In practical application, since a dex file (i.e., an android executable file) in an APK file cannot be directly obtained, the embodiment further provides two ways of generating the dex file and determines the dex file as a file to be packaged. In the two implementation modes, one mode is to pre-compile the class file to generate an android executable file, and determine the android executable file as a file to be packaged; and the other method is that the second program installation file is decompressed to obtain the android executable file, and the android executable file is determined as the file to be packaged. That is, the class file (i.e., class file) that has not been compiled may be precompiled to obtain an android executable file, and the android executable file is determined as a file to be packaged. Or, for the second program installation file generated in the conventional manner, decompressing the second program installation file to obtain an android executable file, determining the android executable file as a file to be packaged, and then performing subsequent processing according to the generation method of the program installation file provided by the application.

S202: and performing first compression operation on the file to be compressed by adopting a preset compression mode to generate a compressed file.

After the file to be compressed is determined, a first compression operation can be performed on the file to be compressed by using a preset compression mode, so that a compressed file is obtained. That is, the file to be compressed is compressed to reduce the size of the compressed file. The preset compression mode may be a compression mode with a high compression ratio, for example, LZMA (Lempel-Ziv-Markov chain-Algorithm), and the generated compression file is a file of the type LZMA.

S203: the compressed file is converted into a first dynamic library file.

And when the compressed file is obtained, converting the compressed file into a first dynamic library file, wherein the first dynamic library file is a file of a dynamic library type and is obtained by converting the compressed file, so that other operations can be performed on the first dynamic library file in the following process conveniently.

In the specific implementation process, different conversion methods are adopted when the compressed files generated aiming at different types of files to be compressed are converted. When the file to be compressed is a dynamic library type file, after the file to be compressed is subjected to a first compression operation in a preset compression mode to generate a compressed file, and the compressed file is converted into a first dynamic library file, the last-stage extension name of the compressed file can be deleted to obtain the first dynamic library file. When the file to be compressed is a file of a non-dynamic library type, after the file to be compressed is subjected to a first compression operation in a preset compression mode to generate a compressed file, and the compressed file is converted into a first dynamic library file, the last-stage extension of the compressed file can be replaced by the extension of the dynamic library type to obtain the first dynamic library file. Wherein, the last stage extension of the compressed file is the extension of the compression algorithm.

For example, in the Android platform, the extension corresponding to the file of the dynamic library type may be. When the file to be compressed is a file of a dynamic library type, such as libcore. When the file to be compressed is a classes.

It can be understood that, when the file to be compressed is a file of a dynamic library type, the file name of the file to be compressed is the same as the file name of the first dynamic library file corresponding to the file to be compressed; when the file to be compressed is a file of a non-dynamic library type, the corresponding first dynamic library file cannot reflect the file type of the first dynamic library file. In order to facilitate subsequent file installation, when the compressed file is converted into the first dynamic library file, the original file type corresponding to each first dynamic library file can be stored in advance, so that after subsequent decompression is completed, the type of the file can be restored to the original file type by referring to the prestored information.

S204: and packing the non-to-be-compressed files in the files to be packed and the first dynamic library file to generate a first program installation file.

After the first dynamic library file is obtained, packing the non-to-be-compressed file in the files to be packed and the first dynamic library file to obtain a first program installation file.

In specific implementation, this embodiment provides an implementation manner for performing a packing process on a file to be compressed and a first dynamic library file, specifically, a second dynamic library file and a first dynamic library file in a file to be packed, which are not to be compressed, are subjected to a second compression operation to generate a third dynamic library file; and then packaging other files which are not to be compressed and the third dynamic library file to generate a first program installation file. That is, the second dynamic library file is a file of a dynamic library type in the non-to-be-compressed files in the files to be packaged, the file of the dynamic library type (i.e., the second dynamic library file) is firstly screened from the non-to-be-compressed files in the files to be packaged, then the second dynamic library file and the first dynamic library file obtained through the first compression operation are subjected to the second compression operation, a third dynamic library file is obtained, further compression is realized, and the size of the packaged program installation file is reduced.

As can be seen from the above description, in the embodiment of the present application, before a program installation file is generated by packaging, a file to be compressed in a file to be packaged is determined, a first compression operation is performed on the file to be compressed in a preset compression manner, a compressed file is generated, and then the compressed file is converted into a first dynamic library file. And finally, packing the non-to-be-compressed files in the files to be packed and the first dynamic library file to generate a first program installation file. Namely, for a larger file in the files to be packaged, namely the file to be compressed, a compression algorithm with a high compression ratio can be adopted for carrying out first compression operation, so that the files to be compressed are greatly reduced, and further, the first program installation file after packaging is reduced. When a user needs to install the application program corresponding to the first program installation file, the first program installation file can be directly downloaded, and because the first program installation file is small, network resources can be saved, and the installation rate and the user experience are improved.

In order to facilitate understanding of the generation method of the program installation file provided by the present application, referring to the generation framework diagram shown in fig. 3, first, a file to be packaged is obtained, and a file to be compressed is determined from the file. And performing first compression operation on the file to be compressed to obtain a compressed file, and converting the compressed file into a first dynamic library file. And then, performing second compression operation on the second dynamic library file and the first dynamic library file in the files to be packaged to obtain a third dynamic library file. And finally, packaging the third dynamic library file and the file which is not to be compressed to obtain a first program installation file.

When a user wants to install an application program corresponding to the first program installation file, the user may download the first program installation file from the server through the terminal, and obtain an installable program file after processing the first program file, and the specific processing procedure will be described with reference to the drawings.

Referring to fig. 4, which is a flowchart of a processing method for a program installation file according to an embodiment of the present application, as shown in fig. 4, the method may include:

s401: and unpacking the program installation file to obtain a first dynamic library file.

Since the program installation file stored in the server is a packaged file, that is, a first program installation file, when the terminal acquires the program installation file, it is necessary to perform an unpacking operation on the program installation file to acquire a first dynamic library file.

In a specific implementation, when the program installation file acquired by the terminal is a file generated through two compression operations, the unpacking operation is performed on the program installation file to obtain a first dynamic library file, including: unpacking the program installation file to obtain a third dynamic library file; a first dynamic library file is determined from the third dynamic library file. The determining of the first dynamic library file from the third dynamic library file may be performing a second decompression operation on the third dynamic library file, and the first dynamic library file is identified from a file of a dynamic library type obtained through the second decompression operation.

It is to be understood that the third dynamic library file includes both the first dynamic library file obtained by the first compression operation and a file of a dynamic library type itself. Therefore, the first dynamic library file needs to be identified from the files of the dynamic library type obtained from the second decompression operation. In a specific implementation, which files of the dynamic library type are the first dynamic library files may be identified according to pre-stored configuration files. The configuration file may be generated during the second compression operation to record which files of the dynamic library type in the files subjected to the second compression operation are the first dynamic library files.

S402: and performing first decompression operation on the first dynamic library file by adopting a preset decompression mode.

It can be understood that, when the first dynamic library file is generated, the first compression operation is performed in a preset compression manner, so that the first decompression operation needs to be performed on the first dynamic library file in a corresponding decompression manner to obtain a decompressed file. For example, when the program installation file is generated, the first compression operation is performed by the LZMA compression method, and when the program installation file is decompressed, the first dynamic library file is compressed by the LZMA decompression method.

In specific implementation, this embodiment provides a first decompression implementation manner for a first dynamic library file by using a preset decompression manner, specifically, identifying an original file type corresponding to the first dynamic library file; when the original file type corresponding to the first dynamic library file is identified as the dynamic library type, directly performing first decompression operation on the first dynamic library file in a preset decompression mode to obtain a file of the dynamic library type; and when the original file type corresponding to the first dynamic library file is identified to be the non-dynamic library type, performing first decompression operation on the first dynamic library file in a preset decompression mode, and deleting the last-stage extension name of the file of the dynamic library type obtained through the first decompression operation to obtain the file of the original file type.

It can be understood that, as can be seen from the embodiment shown in fig. 3, when converting a compressed file into a first dynamic library file, the converted compressed file may be obtained by compressing a file of a dynamic library type, or may be obtained by compressing a file of a non-dynamic library type, whichever type of file is converted into a file of a dynamic library type. Therefore, when decompressing the first dynamic library file, the original file type corresponding to the first dynamic library file needs to be identified, that is, the original file type is the dynamic library type or the non-dynamic library type. A specific implementation of identifying the original file type corresponding to the first dynamic library file will be described in the following embodiments.

And if the original file type corresponding to the first dynamic library file is the dynamic library type, directly decompressing the first dynamic library file to obtain a file of the dynamic library type. For example, if the first dynamic library file is libcore. If the original file type corresponding to the first dynamic library file is a non-dynamic library type, firstly decompressing the first dynamic library file to obtain a file of the dynamic library type, and then deleting the last-level extension of the file of the dynamic library type to obtain a file of the original file type. For example, if the first dynamic library file is of class.

In the specific implementation, when the original file type corresponding to the first dynamic library file is the dynamic library type, directly decompressing the original file type, wherein the decompressed file can be stored in the directory where the first dynamic library file is located; when the original file type corresponding to the first dynamic library file is the non-dynamic library type, the decompressed file can be stored in a preset directory, so that when an application program is started, the required file can be read in the preset directory.

In a possible implementation manner, this embodiment provides the following implementation manners for identifying the original file type corresponding to the first dynamic library file, specifically:

one is to query the corresponding original file type according to the file name corresponding to the first dynamic library file.

That is, when the compressed file is converted into the first dynamic library file, the mapping relationship between the file name corresponding to the first dynamic library file and the original file type corresponding to the first dynamic library file is recorded, and when the original file type corresponding to the first dynamic library file needs to be acquired, the corresponding original file type can be queried according to the file name corresponding to the first dynamic library file.

And the other one is that the file type flag bit in the first dynamic library file is identified, and the original file type corresponding to the first dynamic library file is determined.

Namely, the original file type corresponding to the first dynamic library file is represented by the file type flag bit in the first dynamic library file, and when the corresponding original file type in the first dynamic library file needs to be acquired, the original file type can be acquired by identifying the flag bit. For example, a flag bit of 1 for the file type indicates that the original file type of the first dynamic library file is a dynamic library type, a flag bit of 0 indicates that the original file type of the first dynamic library file is a non-dynamic type, and the original file type of the first dynamic library file can be determined by identifying the flag bit.

And when the first dynamic library file comprises the extension of the dynamic library type and the extension of the non-dynamic library type, identifying the original file type corresponding to the first dynamic library file as the dynamic library type according to the included extension of the non-dynamic library type.

It can be understood that, when the compressed file is converted into the first dynamic library file, if the compressed file is a file of a dynamic library type, only the last-stage extension (the extension corresponding to the compression mode) of the compressed file needs to be deleted when the conversion is performed, and the extension of the dynamic library type is reserved. If the compressed file is a file of a non-dynamic library type, the last-stage extension (the extension corresponding to the compression mode) of the compressed file is only required to be replaced by the extension of the dynamic library type during conversion, and the extension of the non-dynamic library type is reserved. That is, the extension of the original file type is retained in any conversion, and therefore, the original file type corresponding to the first dynamic library file can be identified by determining the extension included in the first dynamic library file.

When the first dynamic library file only comprises the extension of the dynamic library type, the corresponding original file type is the dynamic library type. So, the original file type corresponding to the first dynamic library file is the dynamic library type; when the first dynamic library file comprises the extension of the dynamic library type and the extension of the non-dynamic library type, the corresponding original file type is represented as the non-dynamic library type. For example, the first dynamic library file is class, dex, so that the first dynamic library file comprises an extension of a dynamic library type, so that the first dynamic library file also comprises an extension of an inactive library type, dex, and then the original file type corresponding to the first dynamic library file is the inactive library type.

For understanding, referring to the processing framework diagram shown in fig. 5, the obtained program installation file is first unpacked to obtain a third dynamic library file and other files. And performing second decompression operation on the third dynamic library file to obtain the first dynamic library file and the second dynamic library file. And finally, performing first compression operation on the first dynamic library file to obtain a file of a dynamic library type and a file of a non-dynamic library type.

According to the embodiment, when the application program is started by the terminal, the program installation file is decompressed to support the application program. In addition, because the program installation file downloaded by the terminal is a smaller file, network resources can be saved, and the installation rate and the user experience can be improved.

Based on the above method embodiment, the present application provides a program installation file generation apparatus and a processing apparatus, which will be described below with reference to the accompanying drawings.

Referring to fig. 6, a structure of a program installation file generation apparatus, as shown in fig. 6, includes:

a determining unit 601, configured to determine a file to be compressed in files to be packaged;

a first generating unit 602, configured to perform a first compression operation on the file to be compressed in a preset compression manner, so as to generate a compressed file;

a converting unit 603, configured to convert the compressed file into a first dynamic library file;

a second generating unit 604, configured to perform a packaging operation on a non-to-be-compressed file in the files to be packaged and the first dynamic library file to generate a first program installation file.

In one possible implementation, the apparatus further includes:

It should be noted that, in the present embodiment, implementation of each unit may refer to the foregoing method embodiment, and the present embodiment is not limited herein.

Referring to fig. 7, which is a result diagram of an apparatus for processing a program installation file according to an embodiment of the present application, as shown in fig. 7, the apparatus includes:

the unpacking unit 701 is used for unpacking the program installation file to obtain a first dynamic library file;

the decompressing unit 702 is configured to perform a first decompressing operation on the first dynamic library file in a preset decompressing manner.

In one possible implementation manner, the unpacking unit includes:

In one possible implementation, the decompression unit includes:

Fig. 8 is a schematic structural diagram of a server in an embodiment of the present invention. The server 800, which may vary significantly depending on configuration or performance, may include one or more Central Processing Units (CPUs) 822 (e.g., one or more processors) and memory 832, one or more storage media 830 (e.g., one or more mass storage devices) storing applications 842 or data 844. Memory 832 and storage medium 830 may be, among other things, transient or persistent storage. The program stored in the storage medium 830 may include one or more modules (not shown), each of which may include a series of instruction operations for the server. Still further, a central processor 822 may be provided in communication with the storage medium 830 for executing a series of instruction operations in the storage medium 830 on the server 800.

The server 800 may also include one or more power supplies 826, one or more wired or wireless network interfaces 850, one or more input-output interfaces 856, one or more keyboards 856, and/or one or more operating systems 841, such as Windows Server, Mac OS XTM, UnixTM, LinuxTM, FreeBSDTM, etc.

In particular implementations, central processor 822 may execute the following instructions:

determining a file to be compressed in the file to be packaged;

converting the compressed file into a first dynamic library file;

Optionally, the determining a file to be compressed in the file to be packaged includes:

acquiring a predefined file to be compressed in the file to be packaged; and/or the presence of a gas in the gas,

Optionally, before determining the file to be compressed in the file to be packaged, the method further includes:

Optionally, when the file to be compressed is a file of a dynamic library type, the converting the compressed file into a first dynamic library file includes:

Optionally, the performing a packing operation on the non-to-be-compressed file in the to-be-packed file and the first dynamic library file to generate a first program installation file includes:

Fig. 9 shows a block diagram of a processing device 900 for installing files by a program. For example, the apparatus 900 may be a mobile phone, a computer, a digital broadcast terminal, a messaging device, a game console, a tablet device, a medical device, an exercise device, a personal digital assistant, and the like.

Referring to fig. 9, apparatus 900 may include one or more of the following components: a processing component 902, a memory 904, a power component 909, a multimedia component 908, an audio component 910, an input/output (I/O) interface 99, a sensor component 914, and a communication component 916.

The processing component 902 generally controls overall operation of the device 900, such as operations associated with display, telephone calls, data communications, camera operations, and recording operations. Processing element 902 may include one or more processors 920 to execute instructions to perform all or a portion of the steps of the methods described above. Further, processing component 902 can include one or more modules that facilitate interaction between processing component 902 and other components. For example, the processing component 902 may include a multimedia module to facilitate interaction between the multimedia component 909 and the processing component 902.

The memory 904 is configured to store various types of data to support operation at the device 900. Examples of such data include instructions for any application or method operating on device 900, contact data, phonebook data, messages, pictures, videos, and so forth. The memory 904 may be implemented by any type or combination of volatile or non-volatile memory devices such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disks.

The power supply component 909 provides power to the various components of the device 900. The power components 909 may include a power management system, one or more power sources, and other components associated with generating, managing, and distributing power for the device 900.

The multimedia component 908 comprises a screen providing an output interface between the device 900 and a user. In some embodiments, the screen may include a Liquid Crystal Display (LCD) and a Touch Panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive an input signal from a user. The touch panel includes one or more touch sensors to sense touch, slide, and gestures on the touch panel. The touch sensor may not only sense the boundary of a touch or slide action, but also detect the duration and pressure associated with the touch or slide operation. In some embodiments, the multimedia component 908 includes a front facing camera and/or a rear facing camera. The front-facing camera and/or the rear-facing camera may receive external multimedia data when the device 900 is in an operating mode, such as a shooting mode or a video mode. Each front camera and rear camera may be a fixed optical lens system or have a focal length and optical zoom capability.

The audio component 910 is configured to output and/or input audio signals. For example, audio component 910 includes a Microphone (MIC) configured to receive external audio signals when apparatus 900 is in an operating mode, such as a call mode, a recording mode, and a voice recognition mode. The received audio signals may further be stored in the memory 904 or transmitted via the communication component 916. In some embodiments, audio component 910 also includes a speaker for outputting audio signals.

The I/O interface provides an interface between the processing component 902 and peripheral interface modules, which may be keyboards, click wheels, buttons, etc. These buttons may include, but are not limited to: a home button, a volume button, a start button, and a lock button.

The sensor component 914 includes one or more sensors for providing status assessment of various aspects of the apparatus 900. For example, the sensor assembly 914 may detect an open/closed state of the device 900, the relative positioning of the components, such as a display and keypad of the apparatus 900, the sensor assembly 914 may also detect a change in the position of the apparatus 900 or a component of the apparatus 900, the presence or absence of user contact with the apparatus 900, orientation or acceleration/deceleration of the apparatus 900, and a change in the temperature of the apparatus 900. The sensor assembly 914 may include a proximity sensor configured to detect the presence of a nearby object in the absence of any physical contact. The sensor assembly 914 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, the sensor assembly 914 may also include an acceleration sensor, a gyroscope sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.

The communication component 916 is configured to facilitate communications between the apparatus 900 and other devices in a wired or wireless manner. The apparatus 900 may access a wireless network based on a communication standard, such as WiFi, 2G or 3G, or a combination thereof. In an exemplary embodiment, the communication component 916 receives a broadcast signal or broadcast associated information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communication component 916 further includes a Near Field Communication (NFC) module to facilitate short-range communications. For example, the NFC module may be implemented based on Radio Frequency Identification (RFID) technology, infrared data association (IrDA) technology, Ultra Wideband (UWB) technology, Bluetooth (BT) technology, and other technologies.

In an exemplary embodiment, the apparatus 900 may be implemented by one or more Application Specific Integrated Circuits (ASICs), Digital Signal Processors (DSPs), Digital Signal Processing Devices (DSPDs), Programmable Logic Devices (PLDs), Field Programmable Gate Arrays (FPGAs), controllers, micro-controllers, microprocessors or other electronic components for performing the following methods:

unpacking the program installation file to obtain a first dynamic library file;

Optionally, the unpacking the program installation file to obtain the first dynamic library file includes:

unpacking the program installation file to obtain a third dynamic library file;

Optionally, the determining the first dynamic library file from the third dynamic library file includes:

Optionally, the performing a first decompression operation on the first dynamic library file in a preset decompression manner includes:

Optionally, the identifying an original file type corresponding to the first dynamic library file includes:

alternatively, the first and second electrodes may be,

It should be noted that, in the present specification, the embodiments are described in a progressive manner, each embodiment focuses on differences from other embodiments, and the same and similar parts among the embodiments may be referred to each other. For the system or the device disclosed by the embodiment, the description is simple because the system or the device corresponds to the method disclosed by the embodiment, and the relevant points can be referred to the method part for description.

It should be understood that in the present application, "at least one" means one or more, "a plurality" means two or more. "and/or" for describing an association relationship of associated objects, indicating that there may be three relationships, e.g., "a and/or B" may indicate: only A, only B and both A and B are present, wherein A and B may be singular or plural. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship. "at least one of the following" or similar expressions refer to any combination of these items, including any combination of single item(s) or plural items. For example, at least one (one) of a, b, or c, may represent: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", wherein a, b, c may be single or plural.

It is further noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.

The steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module may reside in Random Access Memory (RAM), memory, Read Only Memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.

The previous description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the application. Thus, the present application is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method for generating a program installation file, the method comprising:

determining a file to be compressed in the file to be packaged;

converting the compressed file into a first dynamic library file;

2. The method of claim 1, wherein the determining the files to be compressed in the files to be packaged comprises:

acquiring a predefined file to be compressed in the file to be packaged;

and/or the presence of a gas in the gas,

3. The method of claim 1, wherein before determining the files to be compressed in the files to be packaged, the method further comprises:

4. A method for processing a program installation file, the method comprising:

unpacking the program installation file to obtain a first dynamic library file;

5. An apparatus for generating a program installation file, the apparatus comprising:

6. A program installation file processing apparatus, comprising:

7. A generation apparatus for a program installation file, comprising a memory, and one or more programs, wherein the one or more programs are stored in the memory, and wherein the one or more programs configured to be executed by one or more processors comprise instructions for:

determining a file to be compressed in the file to be packaged;

converting the compressed file into a first dynamic library file;

8. A computer-readable medium having stored thereon instructions which, when executed by one or more processors, cause an apparatus to perform the method of generating a program installation file according to any one of claims 1 to 3.

9. A processing apparatus for program installation files, comprising a memory, and one or more programs, wherein the one or more programs are stored in the memory, and wherein execution of the one or more programs by one or more processors comprises instructions for:

unpacking the program installation file to obtain a first dynamic library file;

10. A computer-readable medium having stored thereon instructions which, when executed by one or more processors, cause an apparatus to perform the method of processing a program installation file of claim 4.