WO2024098770A1 - Application program management method and system, electronic device, and computer readable medium - Google Patents

Abstract

The present disclosure provides an application program management method, comprising: acquiring information of at least one functional unit to be combined, and generating a combination rule, wherein a total application is divided into a plurality of functional units, and the functional unit to be combined is one of the plurality of functional units; and generating a target sub-application according to the combination rule, wherein the target sub-application is composed of the at least one functional unit to be combined. The present disclosure further provides an application program management system, an electronic device, and a computer readable medium.

Description

Application management method and system, electronic device, and computer readable medium

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority to patent application No. 202211412511.5 filed with the China Patent Office on November 11, 2022, the entire contents of which are incorporated herein by reference.

Technical Field

The present disclosure relates to, but is not limited to, the field of computer technology.

Background technique

Applications and permissions are always the most basic functional parts of various devices. When managing applications based on permissions, the access rights of applications are usually restricted based on the system and components. The application itself is a complete set of functional units. Based on different permission grants, the functions that can be used normally are also different. Take the Android system as an example: the applications in the Android system are sandboxed and isolated. Each application has a dedicated data directory that only has read and write permissions. If the application wants to access the components of other applications, or some globally accessible resources on the device, or framework-specific operation behaviors, then the permission mechanism can systematically regulate and enforce the behavior rules of various applications. In the Android system, permissions are essentially a string that can represent the ability to perform specific operations, such as the ability to access a secure digital (SD) card, the ability to access the address book, and the ability to start or access a component in a third-party application. After the permission is granted, it will first be recorded in the memory and locally, and used as the basis for authentication when calling the system binder service and other application components. Secondly, the application will be divided into a certain group according to the granted permissions. Through this permission mechanism, the ability to access sensitive information, modify important information, or perform important operations is protected by permissions. When an application directly or indirectly performs a specific action associated with a specific permission, it will perform an authentication check based on the permission. Android divides permissions into normal permissions and dangerous permissions. Normal permissions declared in AndroidManifest are automatically granted by the system, while dangerous permissions need to be explicitly granted by the user when used.

However, the above-mentioned permission mechanism cannot fully meet users' needs for information security and personal privacy, nor can it adapt well to the development trend of weak terminals led by 5G mobile transmission and cloud services. Moreover, as the applications themselves have more and more functions and larger sizes, the impact on terminal space and terminal performance is also increasing.

Summary of the invention

The present disclosure provides an application management method, an application management system, an electronic device, and a computer-readable medium.

In a first aspect, the present disclosure provides a method for managing an application, comprising: obtaining information of at least one functional unit to be combined, generating a combination rule, wherein the total application is divided into multiple functional units, and the functional unit to be combined is one of the multiple functional units; generating a target sub-application according to the combination rule, wherein the target sub-application is composed of at least one functional unit to be combined.

In a second aspect, the present disclosure provides an application management system, comprising: a combination rule management module, configured to obtain information of at least one functional unit to be combined and generate a combination rule, wherein the total application is divided into multiple functional units, and the functional unit to be combined is one of the multiple functional units; a sub-application generation module, configured to generate a target sub-application according to the combination rule, wherein the target sub-application is composed of at least one functional unit to be combined.

In a third aspect, the present disclosure provides an electronic device comprising: one or more processors; and a memory on which one or more programs are stored, wherein when the one or more programs are executed by the one or more processors, the one or more processors implement the application management method described in the first aspect of the present disclosure.

In a fourth aspect, the present disclosure provides a computer-readable medium having a computer program stored thereon, and when the program is executed by a processor, the processor implements the application management method described in the first aspect of the present disclosure.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG1 is a flow chart of a method for managing an application program in the present disclosure;

FIG. 2 is a flow chart of some steps in another application management method in the present disclosure. picture;

FIG3 is a schematic diagram of a management system for an application program in the present disclosure;

FIG4 is a schematic diagram of an electronic device in the present disclosure;

FIG5 is a schematic diagram of another application management system in the present disclosure;

FIG. 6 is a schematic diagram of the structure of an overall application in the present disclosure.

Detailed ways

In order to enable those skilled in the art to better understand the technical solution of the present disclosure, the application management method, application management system, electronic device, and computer-readable medium provided by the present disclosure are described in detail below with reference to the accompanying drawings.

Example embodiments will be described more fully below with reference to the accompanying drawings, but the example embodiments may be embodied in different forms and should not be construed as limited to the embodiments set forth herein. Rather, the purpose of providing these embodiments is to make this disclosure thorough and complete and to enable those skilled in the art to fully understand the scope of this disclosure.

In the absence of conflict, the various embodiments of the present disclosure and the various features therein may be combined with each other.

As used herein, the term "and/or" includes any and all combinations of one or more of the associated listed items.

The terms used herein are only used to describe specific embodiments and are not intended to limit the present disclosure. As used herein, the singular forms "a", "an" and "the" are also intended to include plural forms unless the context clearly indicates otherwise. It will also be understood that when the terms "comprising" and/or "made of" are used in this specification, the presence of the features, wholes, steps, operations, elements and/or components is specified, but the presence or addition of one or more other features, wholes, steps, operations, elements, components and/or groups thereof is not excluded.

Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by those of ordinary skill in the art. It will also be understood that terms such as those defined in commonly used dictionaries should be interpreted as having a meaning consistent with their meaning in the context of the relevant art and the present disclosure, and will not be interpreted as having an idealized or overly formal meaning unless explicitly defined as such herein.

For example, the Android system application itself is a collection of all functions, and the size of the application It is getting bigger and bigger, and it is becoming a mixture of multiple functions. The use of each function in the application is restricted by different permission granting states. When a user uses an application, the application actually installed and running in the user's terminal is a full set of all functions. The user can control the permission granting state, and the application adapts to different permission granting states; if the permission is not granted, some functions of the application will be prohibited from being enabled, or the use of the application will be completely prohibited.

The above application structure has the following problems: when a user only wants to grant partial permissions to an application and use some of its functions, but does not need to use other functions of the application, on the one hand, the user installs and runs the entire application, which will increase the memory and storage usage; on the other hand, if the application is not granted with corresponding permissions, it can only provide compatibility processing such as prompts when the application runs to specific functions, or directly prohibit the use of the entire application or report an error.

In order to solve the above problems, some related technologies use methods such as empty authorization to construct a permission granting method, but do not return the specific behavior operation corresponding to the execution permission, so that the application can be entered or used normally, and the operation of the empty authorization returns empty data or performs an empty operation. However, the above solution can only avoid the situation where an error is directly reported when the application is started because the permission is not granted or the entire application is prohibited from being used.

In view of this, in a first aspect, referring to FIG. 1 , the present disclosure provides a method for managing an application, comprising: S1, obtaining information of at least one functional unit to be combined, and generating a combination rule, wherein the total application is divided into multiple functional units, and the functional unit to be combined is one of the multiple functional units; S2, generating a target sub-application according to the combination rule, wherein the target sub-application is composed of at least one functional unit to be combined.

In the embodiments of the present disclosure, multiple functional units in the overall application can be freely split or combined to form different sub-applications; a sub-application is composed of at least one functional unit in the overall application.

In the embodiments of the present disclosure, the functional units to be combined are functional units selected by the user. The user can select the functional units to be combined according to the functions to be used, or according to the permissions they are willing to grant, or according to the functions to be used and the permissions they are willing to grant. The embodiments of the present disclosure do not specifically limit this.

Accordingly, in the embodiments of the present disclosure, the generated target sub-application is a sub-application that meets the user's functional usage requirements, or the generated target sub-application is a sub-application that meets the user's permission granting requirements. The generated target sub-application is a sub-application that meets the user's functional usage requirements and permission granting requirements. The disclosed embodiments do not specifically limit this. In some embodiments, the generated target sub-application is a combination of the smallest functional units that meet the user's requirements.

In the embodiments of the present disclosure, the information of the functional units to be combined selected by the user may be obtained when the application is downloaded; the information of the functional units to be combined selected by the user may be obtained when the application is installed; or the information of the functional units to be combined selected by the user may be obtained when the application is running. The embodiments of the present disclosure do not specifically limit this.

In the application management method provided by the embodiment of the present disclosure, it is possible to generate combination rules based on the information of the functional units to be combined, and generate target sub-applications that meet the needs of users, thereby supporting users to select the target sub-applications required for the composition of the functional units in the total application based on their own needs for functional use and permission granting, and realize that the applications that are actually downloaded, installed, and run can change dynamically according to user needs, which is beneficial to saving terminal storage space, reducing terminal memory usage, and improving the utilization efficiency of terminal performance. At the same time, it can fully meet the user's needs for information security and personal privacy, better adapt to the development trend of weak terminals led by 5G mobile transmission and cloud services, and improve the user experience.

The disclosed embodiments do not specifically limit how to obtain the information of the functional units to be combined to generate the combination rules.

In some embodiments, referring to FIG. 2 , information of at least one functional unit to be combined is obtained, and a combination rule (S1) is generated, including: S11, extracting information of the multiple functional units of the total application, and generating a functional unit screening function; S12, determining the functional unit to be combined according to the selection instruction obtained by the functional unit screening function, and generating the combination rule.

The disclosed embodiments do not specifically limit the information of the functional unit. In some embodiments, the functional unit information includes information such as the functional unit name, permission group, functional unit type, and specific functional description. In some embodiments, the total application includes basic functional units, subsidiary functional units, and split combination information, and the split combination information includes the dependency relationship between the subsidiary functional units and the basic functional units and the functional unit information. In step S11, the functional unit information is extracted from the split combination information.

The structure of the overall application is shown in Figure 6. The overall application can have one or more basic functions. A basic function unit is composed of the basic function part and permission group extracted from the total application. The basic function unit can exist independently, for example, it can run independently as a sub-application. The subsidiary function unit is composed of the function part and permission group other than the basic function extracted from the total application. The subsidiary function unit cannot exist independently, that is, it cannot run independently as a sub-application; the subsidiary function unit can be attached to one basic function unit or multiple basic function units.

The disclosed embodiments do not specifically limit the function of filtering functional units. For example, the function of filtering functional units can provide a function of filtering functional units based on permissions, or a function of filtering subsidiary functional units that have a dependency relationship with basic functional units based on basic functional units. The function of filtering functional units supports users to input selection instructions, and the selection instructions obtained by the function of filtering functional units are instructions generated by users selecting functional units to be combined through the function of filtering functional units.

Accordingly, in some embodiments, information of the multiple functional units of the total application is extracted to generate a functional unit screening function, including: extracting information of the multiple functional units to generate a functional unit list based on permission screening; extracting dependencies between subsidiary functional units and basic functional units to generate a subsidiary functional unit list based on basic functional unit screening; generating the functional unit screening function based on the functional unit list based on permission screening and the subsidiary functional unit list based on basic functional unit screening; wherein the multiple functional units of the total application include at least one basic functional unit and at least one subsidiary functional unit.

In the disclosed embodiments, the basic function unit is generated by extracting the independent basic function part of the total application and the permission group involved in the basic function unit based on the functions of the total application and the permissions involved. The basic function unit can exist independently, that is, it can run independently as a sub-application; the subsidiary function unit is generated by splitting other functions other than the basic function part of the total application based on different permissions and permission groups. Different subsidiary function units are independent of each other. A subsidiary function unit cannot exist independently, that is, an subsidiary function unit must be attached to at least one basic function unit and cannot run independently as a sub-application.

It should be noted that, in some implementations, the list of functional units based on authority screening supports users to screen basic functional units or subsidiary functional units based on authority. The auxiliary functional units having a dependent relationship with the basic functional unit are screened from the basic functional unit.

The implementation of the present disclosure does not specifically limit the implementation of the function unit screening function. For example, the function unit screening function supports the user to input a selection instruction through a graphical interface, or the function unit screening function supports the user to input a selection instruction through a command line interface.

Accordingly, in some embodiments, the function unit screening function is generated according to the function unit list based on permission screening and the subsidiary function unit list based on basic function unit screening, including: generating a graphical interface according to the function unit list based on permission screening and the subsidiary function unit list based on basic function unit screening to obtain the function unit screening function; determining the function units to be combined selected by the user according to the selection instructions obtained by the function unit screening function, and generating the combination rules, including: determining the function units to be combined according to the selection instructions obtained by the graphical interface, and generating the combination rules.

In the embodiment of the present disclosure, the selection instruction acquired by the graphical interface refers to an instruction generated by the user selecting the functional units to be combined through the graphical interface.

The embodiments of the present disclosure do not specifically limit how to generate a target sub-application according to the combination rule.

In some implementations, referring to FIG. 2 , generating a target sub-application according to the combination rule includes: S21 , combining at least one of the to-be-combined functional units according to the trigger path and the combination rule to generate the target sub-application.

In the embodiments of the present disclosure, the trigger path refers to the scenario or path that needs to trigger the processing of generating the target sub-application. The embodiments of the present disclosure do not specifically limit the scenario or path that needs to trigger the generating of the target sub-application. For example, the processing of generating the target sub-application can be triggered when downloading the application; the processing of generating the target sub-application can also be triggered when installing the application; and the processing of generating the target sub-application can also be triggered for the sub-application that is running.

Accordingly, in some embodiments, the trigger path represents a process of triggering the generation of a target sub-application when downloading an application; and according to the trigger path and the combination rule, at least one of the functional units to be combined is combined to generate the target sub-application, including: when downloading the overall application, according to the combination rule, at least one of the functional units to be combined is combined to generate the target sub-application. Generate a sub-application to be downloaded and obtain the target sub-application.

Accordingly, in some embodiments, the trigger path represents a processing process that triggers the generation of a target sub-application when installing an application; according to the trigger path and the combination rule, at least one of the functional units to be combined is combined to generate the target sub-application, including: when installing the overall application, according to the combination rule, at least one of the functional units to be combined is combined to generate a sub-application to be installed, thereby obtaining the target sub-application.

Accordingly, in some embodiments, the trigger path represents a processing procedure for triggering the generation of a target sub-application for a running sub-application; according to the trigger path and the combination rule, at least one of the functional units to be combined is combined to generate the target sub-application, including: according to the combination rule, updating the initial sub-application to obtain the target sub-application.

The disclosed embodiments do not specifically limit how to update the initial sub-application to obtain the target sub-application.

In some embodiments, the initial sub-application is updated according to the combination rule to obtain the target sub-application, including: according to the combination rule, the functional units constituting the initial sub-application are expanded to obtain the target sub-application; and/or according to the combination rule, the functional units constituting the initial sub-application are trimmed to obtain the target sub-application.

It should be noted that in the embodiments of the present disclosure, a target sub-application can be obtained by adding or cutting specific functional units based on the initial sub-application; or a new target sub-application can be generated by combining the functional units to be combined selected by the user based on the existing functional units of the initial sub-application. The embodiments of the present disclosure do not specifically limit this.

In some implementations, splittable application management rules, or permission-based splittable application management rules, are defined to generate an overall application that is composed of multiple functional units and can be freely split and combined.

Accordingly, in some embodiments, referring to FIG. 2 , before obtaining information of at least one functional unit to be combined and generating a combination rule, the management method further includes: S31 , generating the overall application according to the divisible application management rule.

In the embodiments of the present disclosure, a total application consisting of multiple functional units and freely split and combined can be developed according to the splittable application management rules during the application development stage; an existing application can also be transformed into a total application consisting of multiple functional units according to the splittable application management rules. The present disclosure does not specifically limit this.

Accordingly, in some embodiments, the overall application is generated according to the detachable application management rules, including: extracting the basic functional units of the initial application and the permission groups involved in the basic functional units according to the functions of the initial application and the permissions involved in each function; extracting the subsidiary functional units of the initial application according to different permissions and permission groups; and recording the splitting and combining information, wherein the splitting and combining information represents the dependency relationship between the subsidiary functional units and the basic functional units and the functional unit information.

The embodiments of the present disclosure do not specifically limit the splitting and combining information. In some embodiments, the splitting and combining information includes: functional unit information <functional unit name, permission group, functional unit type, specific functional description>, the dependency relationship between the auxiliary functional unit and the basic functional unit, etc. It should be noted that the functional unit information includes but is not limited to the functional unit name, permission group, functional unit type, specific functional description, etc.

Accordingly, in some embodiments, during the development phase, the overall application is generated according to the detachable application management rules, including: developing the overall application according to the detachable application management rules, wherein the overall application includes split combination information and at least one of the functional units, the functional units include basic functional units and subsidiary functional units, and the split combination information represents the dependency relationship between the subsidiary functional units and the basic functional units and the functional unit information.

In some embodiments, for an existing initial application, the total application is generated according to the detachable application management rules, including: according to the detachable application management rules, the initial application is split to obtain at least one of the functions and split combination information, wherein the functional unit includes a basic functional unit and an auxiliary functional unit, and the split combination information represents the dependency relationship between the auxiliary functional unit and the basic functional unit and the functional unit information.

In the second aspect, referring to FIG. 3 , an embodiment of the present disclosure provides an application management system, including: a combination rule management module 301, configured to obtain information of at least one functional unit to be combined, and generate a combination rule, wherein the total application is divided into multiple functional units, and the functional unit to be combined is one of the multiple functional units; a sub-application generation module 302, configured to generate a target sub-application according to the combination rule, wherein the target sub-application is composed of at least one functional unit to be combined.

Fig. 5 is a schematic diagram of the structure of the management system of the application provided by the present disclosure. The management system shown in Fig. 5 can be regarded as a refinement of the structure of the management system shown in Fig. 3 .

As shown in Figure 5, the application management system includes a body management module 201, a functional unit information management module 202, a functional unit dependency management module 203, a combination rule management module 204, a sub-application generation function module 205, an application download management module 206, an application installation management module 207, and a sub-application update module 208. Among them: the main body management module 201: is configured to manage the main body of the overall application; the functional unit information management module 202: is configured to extract and manage the functional unit information and generate a functional unit list; the functional unit dependency management module 203: is configured to extract the dependency between the basic functional unit and the subsidiary functional unit, and generate a subsidiary functional unit list based on the basic functional unit screening; the combination rule management module 204: is configured to generate a graphical interface according to the functional unit list and the subsidiary functional unit list, and generate a combination rule according to the selection instruction obtained from the graphical interface; the sub-application generation function module 205: is configured to generate a target sub-application according to the combination rule; the application download management module 206: is configured to provide an interface for selecting a functional unit when downloading an application; the application installation management module 207: is configured to provide an interface for selecting a functional unit when installing an application; the sub-application update module 208: is configured to provide an interface for updating the installed application by selecting a functional unit.

In a third aspect, referring to FIG. 4 , the present disclosure provides an electronic device, comprising: one or more processors 101; a memory 102, on which one or more programs are stored, and when the one or more programs are executed by one or more processors, the one or more processors implement the application management method described in the first aspect of the present disclosure; and one or more I/O interfaces 103, connected between the processor and the memory, and configured to implement information interaction between the processor and the memory.

Among them, the processor 101 is a device with data processing capabilities, including but not limited to a central processing unit (CPU) and the like; the memory 102 is a device with data storage capabilities, including but not limited to random access memory (RAM, more specifically SDRAM, DDR, etc.), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory (FLASH); the I/O interface (read-write interface) 103 is connected between the processor 101 and the memory 102, and can realize information interaction between the processor 101 and the memory 102, including but not limited to a data bus (Bus) and the like.

In some implementations, the processor 101 , the memory 102 , and the I/O interface 103 are connected to each other via a bus 104 , and further connected to other components of the computing device.

In a fourth aspect, the present disclosure provides a computer-readable medium having a computer program stored thereon, and when the program is executed by a processor, the processor implements the application management method described in the first aspect of the present disclosure.

It will be appreciated by those skilled in the art that all or some of the steps, systems, and functional modules/units in the methods disclosed above may be implemented as software, firmware, hardware, and appropriate combinations thereof. In hardware implementations, the division between the functional modules/units mentioned in the above description does not necessarily correspond to the division of physical components; for example, a physical component may have multiple functions, or a function or step may be performed by several physical components in cooperation. Some or all physical components may be implemented as software executed by a processor, such as a central processing unit, a digital signal processor, or a microprocessor, or implemented as hardware, or implemented as an integrated circuit, such as an application-specific integrated circuit. Such software may be distributed on a computer-readable medium, which may include a computer storage medium (or non-transitory medium) and a communication medium (or temporary medium). As known to those skilled in the art, the term computer storage medium includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storing information (such as computer-readable instructions, data structures, program modules, or other data). Computer storage media include, but are not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tapes, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store the desired information and can be accessed by a computer. In addition, it is well known to those skilled in the art that communication media typically contain computer-readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transport mechanism, and may include any information delivery media.

Example embodiments have been disclosed herein, and although specific terms are employed, they are used and should be interpreted only in a general illustrative sense and not for limiting purposes. In some instances, it will be apparent to those skilled in the art that, unless otherwise expressly stated, features, characteristics, and/or elements described in conjunction with a particular embodiment may be used alone or in combination with features, characteristics, and/or elements described in conjunction with other embodiments. Accordingly, it will be understood by those of ordinary skill in the art that various changes in form and details may be made without departing from the scope of the present disclosure as set forth in the following claims.

Claims (16)

A method for managing an application, comprising: Acquire information of at least one functional unit to be combined, and generate a combination rule, wherein the total application is divided into a plurality of functional units, and the functional unit to be combined is one of the plurality of functional units; A target sub-application is generated according to the combination rule, wherein the target sub-application is composed of at least one of the functional units to be combined. The management method according to claim 1, wherein obtaining information of at least one functional unit to be combined and generating a combination rule comprises: Extracting information of the plurality of functional units of the overall application and generating a functional unit screening function; The function units to be combined are determined according to the selection instructions obtained by the function screening function of the function units, and the combination rule is generated. The management method according to claim 2, wherein extracting information of the plurality of functional units of the total application and generating a functional unit screening function comprises: Extracting information of the plurality of functional units and generating a functional unit list based on authority screening; Extract the dependency relationship between the subsidiary functional units and the basic functional units, and generate a list of subsidiary functional units screened based on the basic functional units; Generate the function unit screening function according to the function unit list based on authority screening and the subsidiary function unit list based on basic function unit screening; The plurality of functional units of the overall application include at least one basic functional unit and at least one subsidiary functional unit. The management method according to claim 3, wherein the function unit screening function is generated according to the function unit list based on the authority screening and the subsidiary function unit list based on the basic function unit screening, comprising: Generate a graphical interface based on the permission-based screening function unit list and the basic function unit-based screening subsidiary function unit list to obtain the function unit screening function; The selection instruction obtained according to the function unit screening function is used to determine the function unit to be combined, and the combination rule is generated, including: According to the selection instruction obtained through the graphical interface, the functional units to be combined are determined, and the combination rule is generated. The management method according to any one of claims 1 to 4, wherein generating a target sub-application according to the combination rule comprises: According to the trigger path and the combination rule, at least one of the to-be-combined functional units is combined to generate the target sub-application. The management method according to claim 5, wherein, according to the trigger path and the combination rule, combining at least one of the to-be-combined functional units to generate the target sub-application comprises: When downloading the overall application, at least one of the to-be-combined functional units is combined according to the combination rule to generate a to-be-downloaded sub-application, thereby obtaining the target sub-application. The management method according to claim 5, wherein, according to the trigger path and the combination rule, combining at least one of the to-be-combined functional units to generate the target sub-application comprises: When installing the overall application, at least one of the to-be-combined functional units is combined according to the combination rule to generate a to-be-installed sub-application, thereby obtaining the target sub-application. The management method according to claim 5, wherein, according to the trigger path and the combination rule, combining at least one of the to-be-combined functional units to generate the target sub-application comprises: According to the combination rule, the initial sub-application is updated to obtain the target sub-application. The management method according to claim 8, wherein, according to the combination rule, updating the initial sub-application to obtain the target sub-application comprises: According to the combination rule, the functional units constituting the initial sub-application are expanded to obtain the target sub-application; and/or According to the combination rule, the functional units constituting the initial sub-application are trimmed to obtain the target sub-application. The management method according to any one of claims 1 to 4, wherein before obtaining information of at least one functional unit to be combined and generating a combination rule, the management method further comprises: The overall application is generated according to the divisible application management rules. The management method according to claim 10, wherein generating the overall application according to the splittable application management rule comprises: Extracting basic functional units of the initial application and permission groups involved in the basic functional units according to the functions of the initial application and the permissions involved in the functions; Extracting subsidiary functional units of the initial application according to different permissions and permission groups; The splitting and combining information is recorded, wherein the splitting and combining information represents the dependency relationship between the subsidiary functional unit and the basic functional unit and the functional unit information. The management method according to claim 10, wherein generating the overall application according to the splittable application management rule comprises: The overall application is developed according to the detachable application management rules, wherein the overall application includes split combination information and at least one of the functional units, the functional units include basic functional units and subsidiary functional units, and the split combination information represents the dependency relationship between the subsidiary functional units and the basic functional units and the functional unit information. The management method according to claim 10, wherein generating the overall application according to the splittable application management rule comprises: According to the splittable application management rule, the initial application is split to obtain at least one The functional unit and splitting and combining information, wherein the functional unit includes a basic functional unit and an auxiliary functional unit, and the splitting and combining information represents the dependency relationship between the auxiliary functional unit and the basic functional unit and the functional unit information. An application management system, comprising: A combination rule management module is configured to obtain information of at least one functional unit to be combined and generate a combination rule, wherein the total application is divided into a plurality of functional units, and the functional unit to be combined is one of the plurality of functional units; The sub-application generation module is configured to generate a target sub-application according to the combination rule, wherein the target sub-application is composed of at least one of the functional units to be combined. An electronic device, comprising: one or more processors; A memory having one or more programs stored thereon, wherein when the one or more programs are executed by the one or more processors, the one or more processors implement the application management method according to any one of claims 1 to 13. A computer-readable medium having a computer program stored thereon, wherein when the program is executed by a processor, the processor implements the application management method according to any one of claims 1 to 13.