CN107402792B

CN107402792B - Integration method, device, equipment and storage medium of application software installation package

Info

Publication number: CN107402792B
Application number: CN201710647600.0A
Authority: CN
Inventors: 吕博扬
Original assignee: Guangzhou Shiyuan Electronics Thecnology Co Ltd
Current assignee: Guangzhou Shiyuan Electronics Thecnology Co Ltd
Priority date: 2017-08-01
Filing date: 2017-08-01
Publication date: 2020-08-28
Anticipated expiration: 2037-08-01
Also published as: CN107402792A

Abstract

The invention discloses an integration method, an integration device, integration equipment and a storage medium of an application software installation package. The integration method comprises the following steps: acquiring a first APK of host software to be integrated with a third-party function and a second APK of the third-party function, wherein the first APK and the second APK have the same API (application program interface) use rule; and merging the first APK and the second APK to generate a third APK of host software which contains API use rules and integrates third party functions. By adopting the method, the technical problems of poor package universality and tighter code function coupling caused by writing the third-party function APK into the original host software package code in the prior art can be solved.

Description

Integration method, device, equipment and storage medium of application software installation package

Technical Field

The present invention relates to the field of data processing, and in particular, to an integration method, an integration device, an integration apparatus, and a storage medium for an application software installation package.

Background

An Android (Android) operating system is a free and open source code operating system, and is widely applied to intelligent terminals such as tablet computers and mobile phones. Android installation packages (APKs) are a class of file formats that android systems can recognize. Generally, after the APK is downloaded, the APK is decompressed and installed to run corresponding application software in the smart terminal.

With the popularization of intelligent terminals and the increasing demand of users, more and more third-party functions are integrated by the same application software. For example, when a certain video application program is used by a user, third-party functions such as user login, video push, member purchase, third-party advertisement application, and video sharing need to be involved. In the prior art, when an original program package of application software is developed, Android Package (APK) of various third-party functions is written into an original program package code as much as possible, so that the finally developed program package has poor universality and relatively tight code functional coupling.

Disclosure of Invention

In view of this, embodiments of the present invention provide an integration method, an integration device, an integration apparatus, and a storage medium for an application software installation package, so as to solve the technical problems in the prior art that the third-party function APK is written into an original host software package, which results in poor package universality and tighter code function coupling.

In a first aspect, an embodiment of the present invention provides an integration method for an application software installation package, including:

acquiring a first android installation package (APK) of host software of a third-party function to be integrated and a second APK of the third-party function, wherein the first APK and the second APK have the same Application Programming Interface (API) use rule;

and merging the first APK and the second APK to generate a third APK of host software which contains the API use rule and integrates third party functions.

In a second aspect, an embodiment of the present invention further provides an integrated device for an application software installation package, including:

the system comprises an acquisition module, a processing module and a processing module, wherein the acquisition module is used for acquiring a first android installation package (APK) of host software of a third-party function to be integrated and a second APK of the third-party function, and the first APK and the second APK have the same Application Programming Interface (API) use rule;

and the merging module is used for merging the first APK and the second APK to generate a third APK which contains the API use rule and integrates host software of third party functions.

In a third aspect, an embodiment of the present invention further provides an apparatus, where the apparatus includes:

one or more processors;

a memory for storing one or more programs,

when the one or more programs are executed by the one or more processors, the one or more processors implement the integration method of the application software installation package according to the embodiment of the present invention.

In a fourth aspect, the embodiment of the present invention further provides a computer-readable storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements the integration method of the application software installation package according to the embodiment of the present invention.

According to the integration method, the device, the equipment and the storage medium of the application software installation package, the first APK and the second APK of the host software with the third-party function to be integrated are obtained, wherein the first APK and the second APK have the same API use rule, and further, the first APK and the second APK with the same API use rule are combined to obtain the third APK with the API use rule.

Drawings

Other features, objects and advantages of the invention will become more apparent upon reading of the detailed description of non-limiting embodiments made with reference to the following drawings:

fig. 1 is a flowchart of an integration method of an application software installation package according to an embodiment of the present invention;

fig. 2a is a flowchart of an integration method of an application software installation package according to a second embodiment of the present invention;

FIG. 2b is a flowchart illustrating a method of integrating application software installation packages;

fig. 3 is a schematic structural diagram of an integrated device for application software installation packages according to a third embodiment of the present invention;

fig. 4 is a schematic structural diagram of an apparatus according to a fourth embodiment of the present invention.

Detailed Description

The present invention will be described in further detail with reference to the accompanying drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the invention and are not limiting of the invention. It should be further noted that, for the convenience of description, only some but not all of the relevant aspects of the present invention are shown in the drawings.

Example one

Fig. 1 is a flowchart of an integration method for an application software installation package according to an embodiment of the present invention. The integration method of the application software installation package provided by this embodiment may be executed by an integration apparatus of the application software installation package, where the integration apparatus may be implemented in the form of software and/or hardware and integrated in a device, where the device may be a server that integrates a third party function for host software. Specifically, referring to fig. 1, the integration method for an application software installation package provided in this embodiment specifically includes:

s110, acquiring a first APK of host software of a third-party function to be integrated and a second APK of the third-party function.

In this embodiment, the host software is application software that can be installed in the android system, and the application software needs to use a third-party function when running. The host software to be integrated with the third-party function means that the package of the host software does not contain the APK of the third-party function or the package of the third-party function, i.e. the host software does not have the capability of using the third-party function in the using process. The third-party function is not specifically referred to as a certain function, and may be understood as a generic term of all third-party functions that can be used in the host software, for example, the third-party function includes, but is not limited to, a payment function, a login function, a push function, a sharing function, and the like.

Further, the first APK and the second APK have the same API usage rules. Optionally, the API usage rule is set by the server, and the API usage rule of the third-party application is called. In general, the usage rules may be documented in a configuration file that is used to determine the calling rules of the intermediate API when the first APK and the second APK are subsequently synthesized. When the first APK and the second APK have the same API usage rule, the host Software and the third-party function may interact through an API corresponding to the API usage rule, specifically, the host Software may call a third-party function Software Development Kit (SDK) through the API, so as to implement the third-party function in the host Software.

Specifically, the API for interaction between the host software and the third-party function may default to integration of various API interfaces, such as integration of a login API, a payment API, a push API, and a sharing API. The specific content of the corresponding API usage rule may be set according to actual conditions. For example, the third party function for login is set to be called by the API for login through the main entry class, wherein the main entry class is named as login API. Third party functions related to payment may each be invoked for the payment API through a main portal class, named payment API. Further, when the login API is set, the method specifically includes: the third-party login functions such as login, asynchronous login, delayed login, user information acquisition after login, successful callback of login and the like can be called through the login API, and different function codes are set for various login functions, so that when the login function is called through the login API, the different login functions are distinguished through the function codes. Setting a payment API, which specifically comprises the following steps: third party payment functions such as WeChat payment, Payment treasure payment, Jingdong payment and bank card payment can all be called through the payment API, and different identity marks are set for various payment functions, so that when the payment function is called through the payment API, different payment functions are distinguished through the identity marks.

When the first APK and the second APK have the same API usage rule, it can be generally understood that one of the first APK and the second APK integrates a Java code executable file (jar package) of an API corresponding to the API usage rule, and the other integrates a reference rule of the API, so as to ensure that the corresponding host software can call a third-party function through the API. For example, the API jar package is integrated in the first APK, and in this case, the first APK includes the host software package and the API jar package. And integrating the API reference rule in the second APK, wherein the second APK comprises a third-party function program package and the API reference rule. The reference rule is preferably in a provider mode, namely the API jar package does not need to be integrated in the second APK, and the API is only referenced in the provider mode. It should be noted that, in this embodiment, the second APK does not refer to a specific third-party function APK in particular, but refers to a set of various third-party functions APK in general, that is, the number of the third-party functions APK included in the second APK is not unique.

And S120, merging the first APK and the second APK to generate a third APK of the host software which contains the API use rule and integrates the third party function.

Illustratively, the first APK is decompiled to obtain a first decompiled file. And performing decompiling processing on the second APK to obtain a second decompiled file. The first APK and the second APK are decompiled in the same way, for example, both are decompiled by the same APK compiling tool. After the APK is decompiled, the APK file can be decompiled into a file with a corresponding format. That is, the first decompiled file and the second decompiled file have the same format, for example, both are smali files. The first decompiled file comprises a host software program package with an API jar package, and the second decompiled file comprises a third party function program package with an API reference rule. It should be noted that, since the number of third-party function APKs in the second APK is not unique, the number of the obtained second decompiled files is not unique.

Specifically, the first decompiled file and the plurality of second decompiled files are merged. The specific mode of the merging treatment can be selected as follows: and synthesizing the first decompilated file and the plurality of second decompilated files according to the preset script file. The specific content of the preset script file can be set according to the actual situation. Wherein, the preset script file preferably comprises: configuration files of the API. The configuration file comprises the API main entry class, the class name, the third-party function and other contents which can be called under various classes, so that the client can realize the plug-in of the API through the configuration file after downloading the third APK. The method adopts a static merging mode during merging processing, namely the APK of the host software and the APK of the third-party function are not changed, the APK of the host software and the APK of the third-party function are completely decoupled, the plug-in of the API is realized only through the configuration file, and then the calling of the host software to the third-party function is realized through the API.

And further compiling the merged file to obtain a final third APK. The third APK comprises a host software APK, a third-party function APK and a jar package of API. Namely, the third APK is the APK of the host software which contains the API reference specification and integrates the third party function. And compiling the merged file by using an APK compiling tool to obtain a third APK. Optionally, the signature and alignment optimization operation is performed on the third APK, and the third APK after the signature and alignment optimization operation is used as the APK delivered to the client.

According to the technical scheme provided by the embodiment, the third-party function APK is integrated in the third APK of the host software to be integrated with the third-party function by acquiring the first APK and the second APK of the host software to be integrated with the third-party function, and further combining the first APK and the second APK with the same API usage rule to obtain the third APK with the API usage rule.

Example two

Fig. 2a is a flowchart of an integration method of an application software installation package according to a second embodiment of the present invention. The present embodiment is embodied on the basis of the above-described embodiments. Specifically, before acquiring the first APK of the host software to be integrated with the third-party function and the second APK of the third-party function, the method may further include: importing a selected third-party function program package in the constructed project; and compiling the third-party function program package based on a preset reference rule of the API required by calling the third-party function program package to generate a second APK.

Further, before obtaining the first APK of the host software to be integrated with the third-party function and the second APK of the third-party function, the method may further include: compiling a fourth APK provided with a Java code executable file of an API required for calling the third-party function package to generate the first APK.

Further, the merging the first APK and the second APK to generate a third APK including the API usage rule and integrating the host software of the third party function specifically includes: decompiling the first APK and the second APK to generate a corresponding first decompiled file and a corresponding second decompiled file; and statically synthesizing the first decompilated file and the second decompilated file, and compiling the statically synthesized files to generate a third APK of host software which contains API (application programming interface) use rules and integrates third party functions.

Referring to fig. 2a, the integration method for an application software installation package provided in this embodiment specifically includes:

s210, importing the selected third-party function program package in the constructed project.

The third-party function program package is a code program package containing third-party functions SDK, and each third-party function corresponds to one third-party function program package.

S220, compiling the third-party function program package based on a preset reference rule of the API required by calling the third-party function program package to generate a second APK.

Specifically, the API reference rule is set for each third-party function package, which may be that a code corresponding to the API jar package is written into a code of the current project, and when the third-party function package is set to be called by the host software through the API, the third-party function package references the reference rule of the API, that is, the API reference rule is written into the third-party function package. Among them, the reference rule is preferably in a provide manner. The advantage of setting the API reference rule is that when the third-party function program package is compiled, the API jar package does not need to be compiled. Especially when the third party functions are excessive, the process of compiling the API jar package needs a large amount of workload, so by setting the API reference rule, each third party function package is compiled only based on the reference rule, and the workload of program processing can be reduced.

Specifically, the specific compiling mode and the adopted compiling tool when compiling the third-party function program package can be set according to the actual situation. Furthermore, the third-party function program package is compiled based on the reference rule to generate a second APK containing the reference rule, and the API jar package is not included in the second APK. Meanwhile, since the API can be implemented by referring to the rule, the second APK is made to have the API use rule.

And S230, compiling a fourth APK of the Java code executable file provided with the API required by calling the third-party function program package to generate the first APK.

And the fourth APK refers to the APK of the host software which is to be integrated with the third-party function and does not have the API use rule. In general, the fourth APK may be provided by the host software developer.

Specifically, a jar package that can call the API of the third party application package is set in the fourth APK, and the jar package may specifically be: and writing the jar packet into a host software program packet in the fourth APK. For example, the fourth APK is decompiled to obtain a source file in the fourth APK file, namely a host software package, and the API jar package is written into the host software package.

Further, the specific compiling mode and the adopted compiling tool when compiling the fourth APK can be set according to the actual situation. Further, compiling the fourth APK based on the jar packet may be compiling a host software package written into the API jar packet to generate the first APK including the API jar packet. Since the API can be realized through the API jar package, the first APK is enabled to have the API use rule which is the same as the API use rule of the second APK configured with the API reference rule.

It should be noted that S210-S220 are mainly specific processes for developing the second APK. S230 is mainly a specific process of configuring an API for the host software APK (fourth APK), and the two processes may be performed completely independently in time sequence. The execution sequence in this embodiment is only an optional way, and is not a limitation. Illustratively, referring to fig. 2b, when the integration of third-party functions into the host software is started, a second APK is set, which contains APKs of various types of third-party functions (such as login, payment, advertisement, etc.), and the API is referred to by the provider method. Meanwhile, setting a first APK and integrating the API jar package into a program package of host software. Wherein the first APK and the second APK are set simultaneously. Further, the first APK and the second APK, when in use, may interact through the API.

S240, decompiling the first APK and the second APK to generate a corresponding first decompiled file and a corresponding second decompiled file.

Specifically, the decompilation mode and the decompilation tool can be set according to actual conditions. The decompilated file corresponding to the first APK is recorded as a first decompilated file which comprises a host software program package with a jar package, and the decompilated file corresponding to the second APK is recorded as a second decompilated file which comprises third-party function program packages with reference rules. It should be noted that the number of the second APKs is not unique, and thus the number of the obtained second decompiled files is not unique.

Optionally, when the same decompilation tool is used to decompilate the first APK and the second APK, the generated first decompilated file and the second decompilated file have the same format.

S250, statically synthesizing the first decompilated file and the second decompilated file, and compiling the statically synthesized files to generate a third APK of the host software which contains the API use rule and integrates the third party function.

Specifically, static synthesis is performed on the first decompiled file and the second decompiled file according to a preset script, wherein the preset script optionally includes: composition rules, and configuration files. The configuration file contains the usage rules of the API, i.e., the main entry class, the class name, and the third-party functions that can be called under each class. For example, calling the payment function corresponds to a payment class, and the class name is a payment API. And simultaneously, recording the third-party function SDK which can be called by each main entry class and the identity of each third-party function SDK. The identity is set to distinguish different third-party functions when different third-party functions SDKs are called through the same API. The main entrance class is set for each type of third-party functions, so that a large amount of workload required when too many third-party functions are provided and corresponding APIs are set for each third-party function can be avoided.

Illustratively, the third-party function package and the host software package in the file obtained by merging according to the preset script are independent from each other, and only the API for the host software to call the third-party function is set in the file, so as to integrate the third-party function in the host software.

Furthermore, compiling the merged file to obtain a third APK. The compiling mode can be set according to actual conditions.

Optionally, since the number of the second decompiled files is not unique, the number of times of the merging operation of the first decompiled file and the second decompiled file is not unique. Referring to fig. 2b, specifically, after the first decompilated file and the second decompilated file are merged, the first decompilated file and the second decompilated file are merged continuously until all the second decompilated files are merged, and the merged file is compiled to obtain a third APK. The script comprises a combination rule of the first decompilated file and all the second decompilated files.

According to the technical scheme provided by the embodiment, the reference rule of the API is set in the second APK of the third-party function, the jar packet of the API is set in the first APK of the host software to be integrated with the third-party function, and the first APK and the second APK are merged to obtain the third APK. The host software program package and the third-party function program package in the third APK are mutually independent, and integration is realized only through one API. The advantage of doing so is that can separate host software and third party's function, can not only realize the complete decoupling from the maintenance, also can realize respectively the development to host software and third party's function in the program development aspect simultaneously, saved manpower resources and development resources. And when the third APK is obtained, the first APK and the second APK are synthesized only through the preset script file without changing the host software program package and the third-party function program package, and the loading problem caused by loading various third-party function program packages can be avoided.

EXAMPLE III

Fig. 3 is a schematic structural diagram of an integrated device for application software installation packages according to a third embodiment of the present invention. Referring to fig. 3, the integrated device provided in this embodiment specifically includes: an acquisition module 301 and a merging module 302.

The obtaining module 301 is configured to obtain a first android installation package APK of host software to be integrated with a third-party function and a second APK of the third-party function, where the first APK and the second APK have the same application programming interface API usage rule; and a merging module 302, configured to merge the first APK and the second APK, and generate a third APK of host software that includes API usage rules and integrates third-party functions.

According to the technical scheme provided by the embodiment, the third-party function APK is integrated in the third APK of the host software to be integrated with the third-party function by acquiring the first APK and the second APK of the host software to be integrated with the third-party function, and further by adopting a technical means of combining the first APK and the second APK with the same API usage rule to obtain the third APK with the API usage rule, the third-party function APK is integrated in the third APK of the host software, and the host software and the third-party function can interact through the API corresponding to the API usage rule without writing the third-party function APK into a host software program package, so that the third-party function and the host software can be independently distinguished, and the host software and the third-party function can be managed and resource developed conveniently.

On the basis of the above embodiment, the method further includes: the import module is used for importing the selected third-party function program package into the constructed project before acquiring the first APK of the host software to be integrated with the third-party function and the second APK of the third-party function; and the first generation module is used for compiling the third-party function program package based on a preset reference rule of the API required for calling the third-party function program package so as to generate a second APK.

On the basis of the above embodiment, the method further includes: and the second generation module is used for compiling a fourth APK provided with a Java code executable file of an API (application programming interface) required by calling the third-party function program package to generate the first APK before acquiring the first APK of the host software to be integrated with the third-party function and the second APK of the third-party function.

On the basis of the above embodiment, the merging module 302 includes: the decompiling unit is used for decompiling the first APK and the second APK to generate a corresponding first decompiled file and a corresponding second decompiled file; and the file merging unit is used for statically synthesizing the first decompilated file and the second decompilated file, and compiling the statically synthesized files to generate a third APK of the host software which contains the API use rule and integrates the third party function.

The integration device of the application software installation package provided by the embodiment of the invention can be used for executing the integration method of the application software installation package provided by any embodiment, and has corresponding functions and beneficial effects.

Example four

Fig. 4 is a schematic structural diagram of an apparatus according to a fourth embodiment of the present invention. As shown in fig. 4, the apparatus comprises a processor 40, a memory 41, an input device 42 and an output device 43; the number of processors 40 in the device may be one or more, and one processor 40 is taken as an example in fig. 4; the processor 40, the memory 41, the input means 42 and the output means 43 in the device may be connected by a bus or other means, as exemplified by the bus connection in fig. 4.

The memory 41 is used as a computer-readable storage medium for storing software programs, computer-executable programs, and modules, such as program instructions/modules (e.g., the obtaining module 301 and the merging module 302) corresponding to the integration method of the application software installation package in the embodiment of the present invention. The processor 40 executes various functional applications of the device and data processing by executing software programs, instructions, and modules stored in the memory 41, that is, implements the integration method of the application software installation package described above.

The memory 41 may mainly include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required for at least one function; the storage data area may store data created according to use of the device, and the like. Further, the memory 41 may include high speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other non-volatile solid state storage device. In some examples, memory 41 may further include memory located remotely from processor 40, which may be connected to the device over a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.

The input device 42 is operable to receive input numeric or character information and to generate key signal inputs relating to user settings and function controls of the apparatus. The output device 43 may include a display device such as a display screen.

The device provided by the embodiment of the invention can execute the integration method of the application software installation package provided by any embodiment, and has corresponding functions and beneficial effects.

EXAMPLE five

An embodiment of the present invention further provides a storage medium containing computer-executable instructions, where the computer-executable instructions are executed by a computer processor to perform an integration method for an application software installation package, where the integration method for an application software installation package includes:

and merging the first APK and the second APK to generate a third APK of host software which contains API use rules and integrates third party functions.

Of course, the storage medium containing the computer-executable instructions provided in the embodiments of the present invention is not limited to the above-mentioned operations of the integration method of the application software installation package, and may also perform related operations in the integration method of the application software installation package provided in any embodiment of the present invention, and has corresponding functions and advantages.

From the above description of the embodiments, it is obvious for those skilled in the art that the present invention can be implemented by software and necessary general hardware, and certainly, can also be implemented by hardware, but the former is a better embodiment in many cases. Based on such understanding, the technical solutions of the present invention may be embodied in the form of a software product, which may be stored in a computer-readable storage medium, such as a floppy disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a FLASH Memory (FLASH), a hard disk or an optical disk of a computer, and includes several instructions for enabling a computer device (which may be a personal computer, a server, or a network device) to execute the integration method of the application software installation package according to the embodiments of the present invention.

It should be noted that, in the embodiment of the integrated device of the application software installation package, the included units and modules are only divided according to the functional logic, but are not limited to the above division, as long as the corresponding functions can be realized; in addition, specific names of the functional units are only for convenience of distinguishing from each other, and are not used for limiting the protection scope of the present invention.

It is to be noted that the foregoing is only illustrative of the preferred embodiments of the present invention and the technical principles employed. It will be understood by those skilled in the art that the present invention is not limited to the particular embodiments described herein, but is capable of various obvious changes, rearrangements and substitutions as will now become apparent to those skilled in the art without departing from the scope of the invention. Therefore, although the present invention has been described in greater detail by the above embodiments, the present invention is not limited to the above embodiments, and may include other equivalent embodiments without departing from the spirit of the present invention, and the scope of the present invention is determined by the scope of the appended claims.

Claims

1. An integration method of an application software installation package, comprising:

and merging the first APK and the second APK to generate a third APK of host software which contains the API use rule and integrates a third party function, wherein a program package of the host software in the third APK is independent of a program package of the third party function.

2. The integration method according to claim 1, wherein the step of obtaining the first APK of the host software of the third-party function to be integrated and the second APK of the third-party function is preceded by the steps of:

importing a selected third-party function program package in the constructed project;

and compiling the third-party function program package based on a preset reference rule of the API required by calling the third-party function program package to generate a second APK.

3. The integration method according to claim 1, wherein the step of obtaining the first APK of the host software of the third-party function to be integrated and the second APK of the third-party function is preceded by the steps of:

compiling a fourth APK provided with a Java code executable file of an API required for calling the third-party function package to generate the first APK.

4. The integration method according to claim 1, wherein the step of merging the first APK and the second APK to generate a third APK including the API usage rule and integrating host software of third party functions comprises:

decompiling the first APK and the second APK to generate a corresponding first decompiled file and a corresponding second decompiled file;

and statically synthesizing the first decompilated file and the second decompilated file, and compiling the statically synthesized files to generate a third APK of the host software which contains the API use rule and integrates a third party function.

5. An integrated apparatus for application software installation packages, comprising:

and the merging module is used for merging the first APK and the second APK to generate a third APK of host software which contains the API use rule and integrates a third party function, and a program package of the host software in the third APK is independent of a program package of the third party function.

6. The integrated device of claim 5, further comprising:

the import module is used for importing the selected third-party function program package into the constructed project before acquiring the first APK of the host software to be integrated with the third-party function and the second APK of the third-party function;

and the first generation module is used for compiling the third-party function program package based on a preset reference rule of the API required for calling the third-party function program package so as to generate a second APK.

7. The integrated device of claim 5, further comprising:

and the second generation module is used for compiling a fourth APK provided with a Java code executable file of an API (application programming interface) required by calling the third-party function program package to generate the first APK before acquiring the first APK of the host software to be integrated with the third-party function and the second APK of the third-party function.

8. The integrated device of claim 5, wherein the merge module comprises:

the decompiling unit is used for decompiling the first APK and the second APK to generate a corresponding first decompiled file and a corresponding second decompiled file;

and the file merging unit is used for statically synthesizing the first decompiled file and the second decompiled file, and compiling the statically synthesized files to generate a third APK of the host software which contains the API use rule and integrates a third party function.

9. An integrated apparatus of an application software installation package, comprising:

one or more processors;

a memory for storing one or more programs,

when executed by the one or more processors, cause the one or more processors to implement the method of integrating an application software installation package as recited in any of claims 1-4.

10. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the integration method of the application software installation package according to any one of claims 1 to 4.