CN117785394A

CN117785394A - Application management method, electronic device, and readable storage medium

Info

Publication number: CN117785394A
Application number: CN202211192489.8A
Authority: CN
Inventors: 徐浩
Original assignee: Huawei Device Co Ltd
Current assignee: Huawei Device Co Ltd
Priority date: 2022-09-28
Filing date: 2022-09-28
Publication date: 2024-03-29
Also published as: WO2024067256A1

Abstract

The application relates to the field of communication, in particular to the technical fields of an application management method, electronic equipment and a readable storage medium, wherein the method comprises the following steps: detecting a first user operation on a first application, wherein the first user operation is used for indicating to switch the state of the first application from an available state to a disabled state; switching the first application into a disabled state, reserving a first type module of the first application, and deleting a second type module of the first application; detecting a second user operation on the first application, wherein the second user operation is used for indicating that the state of the first application is switched from a disabled state to an available state; running a first application based on the reserved first type module, and installing a deleted second type module; the first application is switched to an available state. According to the application program, the memory space of the electronic equipment can be saved during the freezing application period, and when the user needs to use the application again, the application can be started, so that the waiting time of the user is reduced, and the user experience is improved.

Description

Application management method, electronic device, and readable storage medium

Technical Field

The present invention relates to the field of communications, and in particular, to an application management method, an electronic device, and a readable storage medium.

Background

With the popularization of intelligent electronic devices and the development of internet technology, electronic devices such as smart phones, notebook computers, tablet computers and the like have become indispensable products in daily life of people. A user may install a variety of Applications (APPs) on an electronic device to meet their own usage needs.

When the utilization rate of the application is not high, the user can choose to uninstall the application, so that the memory space is saved for the electronic equipment. But when the user needs to use the application again, the application needs to be reinstalled. Thus, not only the user data corresponding to the application is completely lost, but also the operation waiting time of reinstallation is long, so that the user experience is poor.

In view of the above problems, there are some application management schemes, such as freezing applications that are not commonly used by users, and corresponding application data can be stored on electronic devices such as mobile phones. However, the current application management scheme avoids the problem of user data loss of the corresponding application, but the frozen application data is not correspondingly deleted, and still occupies a larger memory space. Particularly, on some low-memory electronic devices, applications frozen based on the current application management schemes still occupy memory, and when a user needs to install a new application, the electronic device may fail to install the new application due to insufficient memory.

Disclosure of Invention

The embodiment of the application management method, the electronic device and the readable storage medium are used for reducing occupation of memory space of the electronic device, are simple in management mode and are beneficial to improving use experience of users.

In a first aspect, an embodiment of the present application provides an application management method, applied to an electronic device, where the method includes: detecting a first user operation on a first application, wherein the first user operation is used for indicating to switch the state of the first application from an available state to a disabled state; switching the first application into a disabled state, reserving a first type module of the first application, and deleting a second type module of the first application; detecting a second user operation on the first application, wherein the second user operation is used for indicating that the state of the first application is switched from a disabled state to an available state; running a first application based on the reserved first type module, and downloading and installing the deleted second type module; the first application is switched to an available state.

For example, the first application may be a WeChat ^TM Naughty medicine ^TM Microblog ^TM Application programs such as music, and in the embodiment of the present application, the first application may also be described as application a. The first user operation may be, for example, a related operation of the user to instruct to freeze the first application, which will be described in detail below, and will not be described in detail herein. The first type of module may be, for example, an entry module, configured to trigger a start-up operation of the first application. The second type of module may be, for example, a feature module for supporting the first application to provide the functionality required by the user. The second user operation may be, for example, a related operation of the user to instruct to defrost the first application, which will be described in detail below, and will not be described in detail herein. The electronic device determines the entry module and the characteristic module of the application A when detecting the first user operation of the application A by the user and selecting the application A to be in a disabled operation state. The entry module of application a is reserved while the feature module is deleted. While the electronic device switches application a to the disabled state. When the electronic device detects a second user operation on the application A in the disabled state, the application A is switched from the disabled state to the available state, and the application A is operated based on the reserved entry module, and the electronic device downloads and installs the characteristic module of which the application A is deleted.

Based on the scheme, the electronic equipment can delete the temporarily unnecessary characteristic modules when the first application is frozen, so that the memory space of the electronic equipment can be saved. And when the user needs to use the first application again, the electronic device can quickly start and run the first application based on the reserved entry module, so that the waiting time of the user is reduced, and the use experience of the user is improved.

In a possible implementation of the first aspect, the method further includes: the first application comprises historical user data, wherein the historical user data is application data correspondingly generated by the electronic device in response to user operation on an interface of the first application; and, the method comprises: in response to a first user operation, historical user data is retained.

For example, the historical user data may include account data generated by the user when using the first application, and data such as user preferences and setting habits of various functions of the first application.

In a possible implementation of the first aspect, the method further includes: the electronic device includes a module list corresponding to the first application, wherein the module list includes at least identification information and path information of the first type module and the second type module, and deleting the second type module of the first application includes: based on the identification information and the path information of the second type module recorded in the module list, accessing the storage space where the second type module is located and deleting the second type module.

For example, the corresponding application package at application a (i.e., the first application described above) may include a plurality of modules, where each module may be, for example, a HAP package. The modules of these applications a can be divided into an entry module and a property module according to functions and roles. And, when the application a is installed, the electronic device may generate a module list corresponding to the application a, for recording identification information and path information of each module. The entry module and the characteristic module may be, for example, the first type module and the second type module, respectively. When the electronic device detects the freezing operation of the user, that is, the first user operation, the electronic device may access the storage space where the second type modules are located according to the identification information and the path information of the second type modules recorded in the module list, and delete each second type module.

It will be appreciated that an application program, such as application a, may or may not include an entry module and a plurality of feature modules, and is not limited in this regard.

In a possible implementation of the first aspect, the method further includes: installing the deleted second type of module, comprising: and sequentially installing the second type modules based on the identification information of the second type modules recorded in the module list.

For example, the electronic device confirms the second type module to be installed based on the identification information of the second type module, and queries the second type module, such as the characteristic module, corresponding to the deletion of the first application through the application market or the application store of the electronic device. The electronic device may then download the queried second type of module and install it.

In a possible implementation of the first aspect, the method further includes: the order in which the second modules are installed in turn may be determined by any one of the following means: counting the use frequency of the user on the first application based on the functions correspondingly provided by the second type modules based on the historical user data, and determining the order from high to low according to the use frequency based on the counting result; based on the size of the data volume corresponding to the second type module, determining the sequence from small to large or the sequence from large to small according to the data volume; an order in which the second type of modules for providing the first function are preferentially downloaded is determined based on the first function used by the user operation instruction on the interface of the running first application.

For example, when the electronic device installs the deleted feature module of the application a, the feature module with higher frequency of use by the user may be preferentially installed according to the historical user data retained in the storage space of the application a. Or, the electronic device may preferably install the model module with a large data volume or the feature module with a small data volume according to the data volume corresponding to the feature module. And the characteristic module corresponding to the function can be preferentially installed according to the current click of the user on a certain function of the application A.

In addition, the electronic device may install the feature modules corresponding to the functions of the user preference according to the historical user data, and then install other feature modules according to the order of the data volume from large to small or from small to large. That is, the above-described modes of determining the order of installing the characteristic modules may be used alone or in combination, and are not limited thereto.

In a possible implementation of the first aspect, the method further includes: the second type module includes a deleted first version and an update published second version, and installing the deleted second type module includes: installing a second type module of the first version based on the default setting; or, installing the second version of the second type module based on the user settings, wherein the user settings are for specifying an operation to install the update published second type module.

For example, when the second type module of the application a is installed, in order to conform to the use habit of the user, the electronic device defaults to install the version corresponding to the second type module when deleted, that is, the first version. In addition, the electronic device may also install, according to the setting of the user, an updated version corresponding to each second type module, where the updated version may be a version compatible with the electronic device, that is, the second version.

In one possible implementation of the first aspect, the electronic device displays a desktop, where the desktop includes an icon of the first application, and switches the first application to the disabled state, including: in a possible implementation of the first aspect, the method further includes: and switching the icon of the first application from a first display mode to a second display mode, wherein the first display mode is a mode indicating that the first application is in an available state, and the second display mode is a mode indicating that the first application is in a disabled state.

In a possible implementation of the first aspect, the method further includes: the first application is switched to an available state, comprising: and switching the icon of the first application from the second display mode to the first display mode.

In a possible implementation of the first aspect, the method further includes: the first user operation includes: pressing the icon of the first application on the desktop for a long time, and selecting the operation of setting the first application to be in a disabled state; or, pressing the icon of the first application on the desktop for a long time, and dragging the icon of the first application to a target folder, wherein the target folder comprises the application program in a disabled state.

In a possible implementation of the first aspect, the method further includes: the second user operation includes: pressing the icon of the first application on the desktop for a long time, and selecting the operation of setting the first application to be in an available state; or, an operation of opening the target folder and dragging the icon of the first application from the target folder to the desktop.

In a second aspect, an embodiment of the present application provides an application management apparatus, including: the packet management subsystem is used for responding to the detected first user operation on the first application and switching the first application into a disabled state; or, in response to the detected second user operation on the first application, switching the first application to an available state, wherein the first user operation is used for indicating that the state of the first application is switched from the available state to a disabled state, and the second user operation is used for indicating that the state of the first application is switched from the disabled state to the available state; and, the packet management subsystem includes: the scanning module is used for responding to the first user operation or the second user operation, scanning a module list of the first application, and determining identification information and path information of a first type module and a second type module of the first application; the installation management module is used for responding to the first user operation, reserving a first type module of the first application and deleting a second type module of the first application; and installing the deleted second class module in response to a second user operation.

In a third aspect, an embodiment of the present application provides an electronic device, including: one or more processors; one or more memories; the one or more memories store one or more programs that, when executed by the one or more processors, cause the electronic device to perform the application management methods provided in the first aspect and various possible implementations described above.

In a fourth aspect, embodiments of the present application provide a computer-readable storage medium having stored thereon instructions that, when executed on a computer, cause the computer to perform the application management method provided in the first aspect and various possible implementations described above.

In a fifth aspect, embodiments of the present application provide a computer program product comprising a computer program/instruction which, when executed by a processor, implements the application management method provided in the first aspect and various possible implementations described above.

Drawings

Fig. 1a is a schematic diagram of a refrigeration application scenario provided in an embodiment of the present application.

Fig. 1b is a schematic diagram of a thawing application scenario provided in an embodiment of the present application.

Fig. 2 is a schematic diagram of a mobile phone system architecture according to an embodiment of the present application.

Fig. 3a is a schematic diagram illustrating an interaction process between user behavior and system behavior of the mobile phone 100 during a refrigeration application according to an embodiment of the present application.

Fig. 3b is a schematic diagram illustrating an interaction process between user behavior and system behavior of the mobile phone 100 during application thawing according to an embodiment of the present application.

Fig. 4 is a process flow diagram of a refrigeration application provided in an embodiment of the present application.

Fig. 5a is a schematic diagram of an operation procedure interface of a long press target application of a refrigeration application according to an embodiment of the present application.

Fig. 5b is a schematic diagram of an operation procedure interface of selecting a freezing target application for a freezing application according to an embodiment of the present application.

Fig. 5c is a schematic diagram of an operation procedure interface for confirming a freezing target application of a freezing application according to an embodiment of the present application.

Fig. 5d is an interface schematic diagram of successful target application freezing of a freezing application according to an embodiment of the present application.

Fig. 6a is a schematic diagram of an operation procedure interface of a drag target application of another refrigeration application according to an embodiment of the present application.

Fig. 6b is an interface schematic diagram of target application freezing success of another freezing application according to an embodiment of the present disclosure.

Fig. 7 is a diagram illustrating a desktop icon change before and after freezing according to an embodiment of the present application.

Fig. 8 is a schematic diagram illustrating module change before and after application of freezing according to an embodiment of the present application.

Fig. 9 shows a change of another desktop icon and an application module list of the interface of the mobile phone 100 according to the embodiment of the present application.

Fig. 10 is a process flow diagram of a defrosting application according to an embodiment of the present application.

Fig. 11a is a schematic diagram of an operation procedure interface of a long-press target application of a defrosting application according to an embodiment of the present application.

Fig. 11b is a schematic diagram of an operation procedure interface of a defrosting application for confirming a defrosting target application according to an embodiment of the present application.

Fig. 11c is an interface schematic diagram of successful thawing of a target application of a thawing application according to an embodiment of the present application.

Fig. 12a is a schematic diagram illustrating an operation procedure interface of a click freezing chamber of another defrosting application provided in the embodiment of the present application.

Fig. 12b is a schematic diagram of an operation procedure interface of a drag target application of another unfreezing application according to an embodiment of the present application.

Fig. 12c is a schematic diagram of an operation procedure interface for dragging to a blank position in another defrosting application according to the embodiment of the present application.

Fig. 12d is a schematic diagram of a thawing success interface of another thawing application provided in the present embodiments.

Fig. 13 is a diagram illustrating a desktop icon change before and after thawing according to an embodiment of the present application.

Fig. 14 is a schematic diagram illustrating module changes before and after thawing by using the embodiment of the present application.

Fig. 15 is a schematic structural diagram of a mobile phone 100 according to an embodiment of the present application.

Detailed Description

In order to make the objects, technical solutions and advantages of the embodiments of the present application more clear, the technical solutions provided by the embodiments of the present application will be described in detail below with reference to the accompanying drawings and specific embodiments of the present application.

It should be further stated that, in the embodiment of the present application, the steps in the method and the flow are numbered for convenience of reference, but not for limiting the sequence, and the sequence exists among the steps, and the description is based on the text.

Fig. 1a to 1b show application scenarios of an application management method.

By way of example, fig. 1a shows a schematic view of a scenario of a refrigeration application according to an embodiment of the present application.

As shown in fig. 1a, the scenario includes a cell phone 100. When the frequency of use of an application on the mobile phone 100 is not high, for example, a sports health APP installed on the mobile phone 100, the user may rarely use the application. Thus, during periods of non-use of the application, the user may perform a freezing operation on the application by pressing the icon for a long time, for example, the user may press the application icon 101 of the sports health APP for a long time, and select the operation of the "freeze" option in the operation window displayed by the mobile phone 100. It will be appreciated that the application is in an unusable state during freezing. When the user needs to use the application, the frozen application program can be correspondingly unfrozen, so that the application can be restored to a usable state.

Fig. 1b shows a schematic view of a scenario of a thawing application according to an embodiment of the present application.

As shown in fig. 1b, the scenario includes a cell phone 100. When a user needs to use a frozen application, the user needs to defrost the application before using the frozen application. For example, after the sports health APP on the mobile phone 100 is frozen, the user needs to use the application, and the user performs the thawing process by pressing the application icon 101 of the sports health APP for a long time and selecting the "thawing" option.

However, as described above, when the application is frozen, the existing application management scheme simply freezes the application, and the frozen application data and related files are still stored in the memory space of the electronic device. According to the scheme, although the fact that the related data of the application program used by a user cannot be lost is guaranteed, a large amount of memory is occupied by corresponding application data.

In order to solve the above problems, an embodiment of the present application provides an application management method, which is applied to an electronic device. Specifically, the method classifies related applications into an entry module and a property module that can be independently operated by dividing the related applications into an entry module and a property module when installing the applications. Wherein each application may include an entry module and a plurality of property modules, the entry module may implement The application program is started and run, and the characteristic module can be a software module for realizing other functions of the application program, for example, for realizing WeChat ^TM APP shakes a software module of function. Based on the above, when the electronic device detects the freezing operation of the user and performs the freezing processing on the application program specified by the user, the electronic device can keep the entry module of the application and the user data generated correspondingly to the application in the use process of the user, and delete the characteristic module of the application. When the electronic device detects the thawing operation of the user and thawing the application program appointed by the user, the electronic device can directly start and run the application based on the access module of the application, and then download each characteristic module related to the application program according to the use requirement of the user or the default sequence.

Therefore, based on the application management method provided by the embodiment of the application, the characteristic module part occupying a larger memory space can be deleted when the application is frozen, so that the memory resource of the electronic equipment can be saved. When the application is unfreezed, the method can rapidly start the application based on the reserved inlet module, so that rapid response to user operation is realized, and the use experience of a user is improved. And the user data which is reserved along with the entry module can also enable the corresponding application program to quickly recover to the setting of the last use of the user when thawing, accords with the use habit of the user, and is also beneficial to improving the use experience of the user.

It will be appreciated that the methods of freezing applications provided herein, suitable electronic devices may include, but are not limited to, the above-described cell phone 100, personal computers (personal computer, PCs) (including laptop computers, desktop computers, tablet computers, etc.), servers, wearable devices, head mounted displays, mobile email devices, car set devices, portable gaming devices, portable music players, reader devices, televisions with multiple processors embedded or coupled therein, or other electronic devices with multiple processors.

For convenience of description, the specific implementation procedure of the refrigeration application provided in the embodiment of the present application will be described in detail below with reference to the mobile phone 100 as an example.

FIG. 2 provides a schematic block diagram of a distributed operating system architecture according to an embodiment of the present application. The system architecture can be applied to the electronic devices such as the mobile phone 100 and the like, and is used for implementing the application management method provided by the embodiment of the application. It will be appreciated that the distributed operating system shown in FIG. 2 may be, for example, hong Monte ^TM Operating system (Harmonyos) ^TM ) There is no limitation in this regard.

As shown in fig. 2, the distributed operating system architecture may include an application layer, an application framework layer, a system services layer, and a kernel layer.

The application layer may include a series of installed applications, among other things. The applications may include desktop Launcher (desktop), settings, and music applications, for example, calendars, WLANs, bluetooth, cameras, gallery, phone calls, maps, video, etc., without limitation.

It will be appreciated that with great luck ^TM Operating system (Harmonyos) ^TM ) For example, the application packages (Application Package, apk) corresponding to the applications installed in the distributed operating system illustrated in fig. 2 may include a plurality of hong-and-Monte capability packages (HarmonyOS Ablilty Package, HAP) and a package information file (pack. Info) for describing each HAP attribute. The HAP is a module package generated by packaging code, resources, third party libraries (libs), and application configuration files (config. Json). The HAP package may include an entry module (entry. HAP), each application package must have and only one entry. HAP for the same device type, and may be installed and run independently. The ingress module may also include the Abilities, resources, libs and config.

It will be appreciated that the module that the system first runs after the user clicks the application icon is the portal module, which is responsible for the main functions of the application. Taking exercise health APP as an example, the main functions of the application are functions of setting exercise targets by users, recording exercise conditions of the users and the like.

The HAP package may or may not include a feature module (HAP), and may also include one or more feature modules. In some embodiments, the feature modules (feature. Haps) may include Abilities, resources, libs and config. Json. In other embodiments, each feature module may also include only libs and config. Json, or only resources and config. Json, etc. The feature module (feature. Hap) including the Abiliy can operate independently, while the feature module (feature. Hap) not including the Abiliy can provide assistance for the operation of other modules, for example, can provide assistance for the operation of the entry module (entry. Hap).

Some additional functions of the application, unlike the portal module of the application, are provided by a feature module (feature. Hap), such as the "connect sports bracelet" function in sports health APP.

It will be appreciated that attribute information of each HAP may be included in the pack. Info, such as a packet Name (Name) of each HAP, a module type (module-type) of each HAP as "entry" or "feature", a device type (device-type) in which each HAP supports operation, and the like.

It will be appreciated that in some embodiments, the portal module and the properties module may be stored under an installation directory of the application, such as "/app/bundleName/entry. Hap/app/bundleName/featureA. Hap".

The application framework layer is a User program framework, a package management subsystem, a capability (capability) framework, and a User Interface (UI) framework. Wherein the user program framework comprises a package administration subsystem.

The application framework layer may provide a multi-lingual user program framework of Java, C, C++, JS, etc. for applications of the distributed operating system, as well as a multi-lingual application programming interface (Application Programming Interface, API) for various software and hardware services to be externally opened.

Packet management subsystem: and the system is responsible for managing the application package and providing the information inquiry, installation, updating, unloading, storage and other capabilities of the application package.

It will be appreciated that the installation and uninstallation of applications may be implemented by the package administration subsystem. The module list corresponding to the target application may be stored in a database corresponding to the packet management subsystem, and when the electronic device installs the target application, the packet management subsystem may store the module list corresponding to the target application in the corresponding database. The module list may include identification information such as names or module numbers of the entry modules and the feature modules included in the target application.

The package management subsystem may include a scan module and an installation management module. In application management, the scanning module may be configured to scan a module list of the application program, determine a type of each HAP packet, and thereby determine an entry module and a characteristic module of the scanned target application. The installation management module can delete the read characteristic module based on the detected freezing operation; or the characteristic module of the corresponding application may be downloaded and installed based on the detection of the thawing operation.

It will be appreciated that in some embodiments, during thawing of an application, the installation management module of the package management subsystem may default to downloading the deleted properties module of the corresponding application instead of the properties module corresponding to the latest application version. In other embodiments, the installation management module may also delete the old version of the object or file or directly download the latest version of the directory or file if it detects that the user needs to download the latest version of the object application.

Capability (availability) framework: abilityis an abstraction of the capabilities that an application possesses and is also an important component of an application program. An application may have multiple capabilities (i.e., may contain multiple absintbilities), harmonyos ^TM The support applications are deployed in units of Abilitys. Abilitys can be divided into two types, feature Abilitys (FAs) and Feature Abilitys (PAs). Wherein, the FA supports Page Abilitys: page templates are templates uniquely supported by the FA for providing the ability to interact with the user, with UI interfaces. The PA supports Service Abilityand Data Abilitywherein the Service template is used for providing the capability of running tasks in the background, and the Data template is used for providing unified Data access abstraction to the outside without UI interface.

A user interface frame: the most important function of the user interface is to establish a connection between the user and the system background, the system background converts data into visual contents through the UI and displays the visual contents to the user, and meanwhile, the user also transmits operation instructions (including data) to the system background through the UI.

In the application, a user transmits an operation instruction of application management to a system background through a user interface framework. The user interface frame may also display application icons processed by the application management method in the present application.

The system service layer is the core of the distributed operating system and provides services for application programs in the application layer and software development kits (software development kit, SDK) through the application framework layer.

The graphic subsystem mainly comprises modules such as a UI component, a layout, an animation, a font, an input event, window management, rendering and drawing, and the like, an application framework based on a lightweight system is constructed, and the application development of an OpenHarmony system of the Internet of things equipment with smaller hardware resources is met.

Distributed data management (distributed data service, DDS) provides applications with the ability to distribute database data among different devices. By invoking the distributed data interface, the application saves the data into a distributed database. The distributed data service can isolate data belonging to different applications based on the combination of the account number, the application and the database, so that the data among the different applications can not be accessed mutually through the distributed data service.

Distributed soft bus: with reference to a computer hardware bus, an intangible bus is built between 1+8+N devices, and the bus has the characteristics of self discovery, self networking, high bandwidth and low time delay. The distributed soft bus is formed by constructing an 'intangible' bus between 1+8+N devices (1 is a mobile phone, 8 stands for car set, sound box, earphone, watch, bracelet, flat panel, large screen, personal computer (personal computer, PC), augmented reality (augmented reality, AR) and Virtual Reality (VR), N generally refers to other Internet of things (internet of things, IOT) devices, and has the characteristics of automatic discovery, instant use, ad hoc network (heterogeneous network networking), high bandwidth, low time delay, high reliability and the like.

Public base library subsystem: the public base stores the general base components of OpenHarmony. These base components may be used by the OpenHarmony business subsystems and upper layer applications. The public base subsystem provides the functions of KV (key value) storage, file operation, timer, dump system attribute and JS API (device query, data storage).

The kernel layer is a layer between hardware and software. The kernel layer of the operating system includes: a core subsystem and a driver subsystem. The kernel subsystem can adopt a multi-kernel design between the distributed operating systems, so that the kernel subsystem supports the selection of an appropriate OS kernel for different resource-constrained devices.

A kernel abstraction layer (kernel abstract layer, KAL) on the kernel subsystem provides underlying kernel capabilities to upper layers including process/thread management, memory management, file system, network management, peripheral management, etc., by masking multi-kernel differences.

The driving framework provided by the driving subsystem is an ecologically open foundation of the hardware of the distributed operating system, and provides unified peripheral access capability and driving development and management framework. The inner core layer at least comprises a display driver, a camera driver, an audio driver and a sensor driver.

Based on the system architecture shown in fig. 2, fig. 3a and fig. 3b respectively show a schematic diagram of an interaction process between user behavior and system behavior of the mobile phone 100 during application management according to an embodiment of the present application. In other embodiments, the execution subject of the system behaviors shown in fig. 3a and 3b may be the electronic device such as the PC, which is not limited herein.

As shown in fig. 3a, the user behavior includes: the user performs the operation of the freezing application. The operation manner of ejecting the shortcut of the long-press application icon as shown in operations (1) to (3) in fig. 5a to 5d, or the operation manner of dragging the long-press application icon to the freezing chamber 610 as shown in operation (4) in fig. 6a to 6b, etc. are specifically referred to the following related description, and will not be repeated herein.

The system behavior of the mobile phone 100 is performed by responding to the user behavior, as shown in fig. 3a, the window manager of the mobile phone 100 acquires an event corresponding to the user behavior, matches the display task of the corresponding operation, and the user selects an application to be frozen according to the displayed operation task. The package management subsystem detects the application selected by the user through the user behavior, scans and reads the module list of the application, and finds an entry module and a characteristic module. And deleting the characteristic module, and reserving the entry module and the data generated by the user. The window manager controls the display of updated desktop icon states after freezing the application, the application is successfully frozen, and the user cannot use the application during the application freezing period.

With continued reference to fig. 3b, the user actions include: the user performs an operation of thawing the application. The manner of ejecting the shortcut of the long-press application icon as shown in operations (5) to (6) of fig. 11a to 11c, or the manner of dragging the long-press application icon out of the freezing chamber 610 as shown in operations (7) to (9) of fig. 12a to 12d, etc. are described in detail with reference to the following related descriptions, and will not be repeated here.

It can be understood that the system behavior of the mobile phone 100 is performed by responding to the user behavior, as shown in fig. 3b, the window manager of the mobile phone 100 acquires an event corresponding to the user behavior, matches the display task of the corresponding operation, and the user selects an application that needs to be thawed. The package management subsystem detects the application selected by the user through the user behavior, and the scanning module scans the characteristic modules deleted by the application, acquires the module names, downloads the deleted characteristic modules and installs the deleted characteristic modules. The window manager controls the desktop icon state to be updated after the application is unfrozen, the application is successfully unfrozen, and a user can use the application.

The overall flow of a refrigeration application is described in detail below in conjunction with fig. 4, which shows a process flow diagram of a refrigeration application in accordance with an embodiment of the present application. It can be understood that the execution subject of each step in the flow shown in fig. 4 is the mobile phone 100, and the execution subject will not be repeated in the following steps. In other embodiments, the execution subject of each step shown in fig. 4 may be an electronic device such as a PC, which is not limited herein.

As shown in fig. 4, the flow includes the steps of:

401: a user operation for freezing the target application is detected.

For example, the user may perform a freezing operation on an application icon to be frozen on the desktop of the mobile phone 100, where the operation may be, for example, selecting to freeze by pressing the application icon for a long time, or dragging the corresponding application icon to a frozen folder, etc., which is not limited herein. Accordingly, the mobile phone 100 may detect the user operation for the refrigeration application described above.

By way of example, fig. 5 a-5 d illustrate related interface schematic diagrams during operation of some refrigeration applications, according to embodiments of the present application.

As shown in fig. 5a, the mobile phone 100 displays various application icons on the main interface. Referring to operation (1) of fig. 5a, when the user selects the frozen application a, the user presses the application icon for a long time until the interface pops up the shortcut 510 of the application. With continued reference to fig. 5b, a corresponding shortcut is popped up over the application after long pressing of the application icon. In other embodiments, the shortcut 510 of the application may also be displayed below the application icon, or elsewhere centered on the application icon, without limitation. The user performs operation (2) according to the prompt to click "freeze". With further reference to fig. 5c, after the user clicks on the freeze, a final confirmation operation is displayed on the interface of the mobile phone 100, and the user performs operation (3) to confirm the freeze application a again. In some embodiments, the user need not perform operation (3), without limitation. The handset 100 may set the application icon of the frozen application program to gray after performing steps 402 to 406 described below, as shown in fig. 5 d.

In other embodiments, reference may also be made to the alternative modes of operation of the refrigeration application shown in figures 6a to 6 b. As shown in fig. 6a, the user selects a target application that needs to be frozen, for example application a. Referring to operation (4) of fig. 6a, the user selects an application icon that finds the application a, and long-presses the drag icon into the freezing chamber 610. It is understood that in embodiments of the present application, the freezer compartment 610 refers to a folder for storing frozen application icons. The operation of placing an application program into the freezing chamber 610 may trigger a process of freezing the application.

With further reference to fig. 6a, the system detects a user operation, freezing application a dragged to the freezer compartment 610. After the handset 100 performs steps 402 to 406 described below, the refresh application icon sets the application icon to gray as shown in fig. 6 b.

In other embodiments, the mobile phone 100 may also detect that the user operation for the freezing application is pressing the application icon for several seconds, such as pressing the application icon for 5s, etc., which is not limited herein.

402: and reading a module list of the target application, and determining an entry module and a characteristic module of the target application.

Illustratively, the user operation for the frozen target application is based on detection. When the mobile phone 100 installs the target application, a module list corresponding to the target application is stored in a corresponding database, and the module list may include identification information such as names or module numbers of the entry modules and the characteristic modules included in the target application. The list of modules is scanned to determine an entry module and a feature module for the target application, wherein the application is divided into an entry module and a plurality of feature modules.

It will be appreciated that, as described above, the portal and feature modules of each application may exist, for example, in the form of HAP packages, namely entry. The portal module and the characteristics module may be stored under the installation catalog of the respective application. By way of example, the storage path corresponding to the feature module a of a certain application program may be "/app/bundleName/entry/entry.hap/app/bundleName/featureA/featurea.hap" or other paths, which are not limited herein.

403: and reserving an entry module of the target application and user data correspondingly generated in the process of using the target application by a user, and deleting a characteristic module of the target application.

Illustratively, after finding the entry module based on the read target application module list, the mobile phone 100 reserves the codes and resources of the application entry module and the user data correspondingly generated in the process of using the target application by the user, and deletes the codes and resources of the target application characteristic module. The user data corresponding to the target application is data set in the application using process of the user, information such as the using frequency of the functional module, and the like, for example, the duration and the number of sports set when the user uses the sports health APP, or the sports mode selected by the user, and the like.

It can be understood that the reserved code and resource of the target application entry module and the memory space occupied by the user data correspondingly generated in the process of using the target application by the user are small compared with the memory occupied by the target application. The method is convenient for the user to defrost and use later, and the memory space of the electronic equipment is not affected.

It can be understood that the feature module runs some additional functions of the application, and the code and resource of the feature module occupy a larger memory space, so that the memory space of the electronic device can be saved after deletion. For example, taobao ^TM Additional functional modules such as a ballon farm in an application may save some memory space if deleted during a refrigeration application. Generally, the additional functions are more and the occupied memory is large, so that after the characteristic module is deleted, the memory space of the mobile phone is saved. In addition, in order to enable a user to defrost the application, the additional function of the application can be used more quickly, and when codes and resources of the characteristic module are deleted, the file name of the characteristic module is reserved, so that the characteristic module can be downloaded quickly when the user needs to use the application.

404: and switching the display mode of the application icon displayed on the desktop corresponding to the target application into a corresponding mode in a frozen state.

Illustratively, after the user selected application is successfully frozen, the handset 100 refreshes the desktop icon, setting the frozen application icon to gray from the original color. As shown in fig. 5d, after application a has been frozen successfully, the application icon corresponding to application a is set to gray. In other embodiments, as shown in fig. 6b, after the application a is dragged into the freezing chamber and successfully frozen by the mobile phone 100, the icon corresponding to the application a may be set to gray. In other embodiments, after freezing the application, the application icon color of the corresponding application may be switched to another color, such as black, without limitation.

405: the freezing process of the target application is completed.

Illustratively, the freezing application is successful based on steps 401 through 405 described above.

At this time, the state parameters corresponding to the frozen target application may be changed from the available state to the disabled state. Thus, the user cannot use the application during its freezing. If the user carelessly touches the frozen application, the mobile phone 100 can intercept the click event of the user according to the recorded current state parameter of the target application, for example, the desktop starter operated by the mobile phone 100 can intercept the click event of the user according to the related parameter recorded in the package management subsystem and in the disabled state of the application, so as not to respond to the operation of the user. In other embodiments, when the user clicks on the frozen target application, the mobile phone 100 may also pop up a prompt message, which may alert the user, for example, "the application is frozen, please use after thawing". In other embodiments, the mobile phone 100 may alert the user by vibration, etc., without limitation.

It will be appreciated that the frozen target application only retains the code and resources of the application entry module and the corresponding user data of the target application. Referring to fig. 8, the application area is divided into one entry module and a plurality of characteristic modules. Taking an application a as an entry module and two feature modules as an example, the mobile phone 100 scans and reads the entry module and the feature module of the application, deletes the codes and resources of the feature module of the application, and only reserves the codes and resources of the application entry module and the user data corresponding to the target application. The memory space occupied by the mobile phone 100 after the application of freezing is very small compared with the memory space before the application of freezing, so that the memory space of the mobile phone 100 is saved. As shown in fig. 7, after the freezing is successful, the icon color of the corresponding application on the interface of the mobile phone 100 may be switched from the icon color before the freezing to the color in the unusable state, for example, to gray, so as to mark that the freezing of the application is successful.

The following describes another mobile phone 100 interface desktop icon and application module list change during application freezing process with reference to fig. 9.

The main interface of the mobile phone 100 displays various applications as shown in fig. 9. And the user executes specific operation to select the APP01 application from various applications displayed on the main interface of the mobile phone 100 for freezing treatment. With continued reference to fig. 9, upon detecting a user operation, the scanning module of the packet management subsystem of the mobile phone 100 scans the module list of the APP01 application selected by the user, and reads the entry module and the characteristic module of the application. The installation management module of the package management subsystem deletes the characteristic modules (featureA and featureB) of the APP01 application, and reserves the entry module and user generation of the APP01 application. The packet management subsystem may also change the state parameters of the APP01 application from an available state to a disabled state upon deletion of the feature module of the APP01 application. Therefore, when the user clicks the APP01 application, the desktop application can intercept the clicking event of the user according to the APP01 application state recorded by the package management subsystem, so that the clicking operation of the user is not responded. The successfully frozen application icon is set to gray, as shown in fig. 9, and the mobile phone 100 refreshes the application icon of the APP01 application, sets the application icon to gray, and in other embodiments, may set the application icon to other colors, such as setting the application icon to black, without limitation.

It will be appreciated that during application freezing, the user cannot use the application. If the user wants to reuse the frozen application, the application needs to be thawed first. The application management method further comprises thawing treatment of the application.

The specific flow of target application thawing is described in detail below in conjunction with fig. 10.

FIG. 10 illustrates a process flow diagram for thawing a target application in accordance with an embodiment of the present application. It can be understood that the execution subject of each step in the flow shown in fig. 10 is the mobile phone 100, and the execution subject will not be repeated in the following steps. In other embodiments, the execution subject of each step shown in fig. 10 may be the electronic device such as the PC, which is not limited herein.

As shown in fig. 10, the flow includes the steps of:

1001: a user operation for thawing the target application is detected.

Illustratively, a user operation for thawing the target application is detected. Taking the mobile phone 100 as an example, referring to fig. 11a, when a user needs to use a frozen target application, the user needs to defrost the target application. For example, the user selects the thawing application a, and the user performs operation (5) of pressing the freezing application for a long time until a selection page confirming thawing is popped up. Further execution of operation (6) in fig. 11b thaws the application. The thawing operation may be performed by double clicking or triple clicking on the frozen application icon, which is not limited herein.

In other embodiments, as shown in fig. 12a, the user performs operation (7) to click on the freezing chamber 610, and the user selects a target application to be thawed according to the freezing application displayed by the freezing chamber 610. Taking application a as an example, the user presses the corresponding icon for a long time, performs operation (8) shown in fig. 12b to drag the icon of application a out of the freezing chamber 610, and continues to perform operation (9) shown in fig. 12c to drag the icon to the blank of the display interface.

In other embodiments, the detection of the user operation for thawing the target application may be long pressing the target application icon to be thawed for several seconds, for example, long pressing the target application icon to be thawed 5s, which is not limited herein.

1002: and reading a model list of the target application, and determining identification information of the characteristic module to be downloaded.

Illustratively, the identification information of the feature module that needs to be downloaded is determined based on detecting a user operation for thawing the target application, reading a model list of the target application. When the mobile phone 100 installs the target application, a module list corresponding to the target application is stored in a corresponding database, and the module list may include identification information such as names or module numbers of the entry modules and the characteristic modules included in the target application. And (3) determining an entry module and a characteristic module of the target application by scanning the module list, and further reading the module name of the deleted characteristic module.

It will be appreciated that only the code and resource of the application property module is deleted when the target application is frozen, and the code and resource file corresponding to the entry module of the target application, etc. are not deleted. The handset 100 can quickly find missing feature modules. In some embodiments, the property module of the target application may be stored under the application installation directory "app/bundleName/featureA/featurea.hap", and the mobile phone 100 only needs to scan and read the "app/bundleName/featureA/featurea.hap" folder.

1003: and downloading each characteristic module of the target application, and finishing the installation of each characteristic module.

Illustratively, the download installation executes the step 1002 to read the codes and resources of the feature module whose target application is deleted, and the downloaded codes and resources are stored in the corresponding module name folder.

It will be appreciated that when thawing the target application, the target application need not be re-downloaded. Because the portal module is preserved when the target application is frozen, the functionality of the portal module of the target application can be used after the target application is opened, while the handset 100 already downloads the feature module in the background.

It will be appreciated that in some embodiments, the downloading order may be determined according to the size of the feature module, where the feature module occupies a large memory defined as a large packet and occupies a small memory defined as a small packet. For example, download a small packet before downloading a large packet. In other embodiments, the usage habits of the user may be determined based on stored user-generated data, with the corresponding feature modules being downloaded preferentially. For example, defrosting and panning ^TM When APP, according to the user data correspondingly generated in the process of using the target application, the user is found to frequently use the 'Taobaosheng' function. The mobile phone 100 can preferentially download the feature module of the function according to the usage habit of the user.

In other embodiments, during the download process, the user triggers an uninstalled feature module, which is placed in the first download list by the handset 100 for preferential download. For example, in Taobao ^TM In the APP thawing process, the user clicks "red package check-in", but the feature module corresponding to the function is not yet installed, at this time, the mobile phone 100 places the feature module at the first place of the download list, and downloads and installs the feature module preferentially, and the user has little waiting time. Other feature modules are downloaded in sequence according to the size of the occupied memory space, and are not limited herein.

It will be appreciated that in downloading the target application characteristics module, the handset 100 preferably installs a pre-frozen version of the target application for ease of use by the user. In some embodiments, the latest version may also be installed at the option of the user, e.g., during thawing and panning ^TM In APP, the mobile phone 100 takes precedence in order to conform to the usage habit of the userInstallation of Taobao ^TM Versions of APP before freezing. When the user selects the latest version, the mobile phone 100 installs the latest version according to the user's selection, without limitation.

1004: and switching the display mode of the application icon displayed on the desktop corresponding to the target application into a unfreezing state corresponding mode.

Illustratively, after the target application selected by the user is successfully thawed, the mobile phone 100 refreshes the desktop icon, and the thawed application icon is set to the color before freezing from the original gray. As shown in fig. 11c, after application a thaws successfully, the application icon resumes the pre-frozen color.

In other embodiments, as shown in fig. 12d, application a is pulled out of freezer compartment 610 after thawing is successful, and the application icon resumes the pre-frozen color, without limitation.

1005: and finishing the thawing process of the target application.

Illustratively, steps 1001 to 1005 are performed, where the mobile phone 100 successfully thaws the target application, and the user can normally use the function of the feature module of the application.

It will be appreciated that upon thawing the target application, the handset 100 adjusts the state parameters of the target application from a disabled state to an available state. After thawing, the user can click on the icon of the target application, and start and use the target application.

It will be appreciated that the application icon of the target application after thawing is restored from the grey color at the time of freezing to the color before freezing. As shown in fig. 13, when the icon returns to the pre-freezing color, the target application returns to normal, and the user can use various functions operated by the feature module. After thawing, the packet management subsystem can adjust the state parameters of the target application from the disabled state to the available state, and then the user can click on the icon of the target application to run the target application.

The change of the module before and after thawing of the target application is further described with reference to fig. 14. The target application is divided into an entry module and a plurality of property modules, here exemplified by one entry module and two property modules. As shown in fig. 14, the target application to be thawed retains the corresponding user data generated by the portal module and the user during use of the target application. Continuing with the thawing process from step 1001 to step 1005, referring to fig. 14, the mobile phone 100 scans the missing feature module and downloads the feature module of the target application through the application market, and downloads and installs the feature module of the featureA and the feature module of the featureB through the application market. After installation of the corresponding feature modules, the user may then use the corresponding target applications based on the functionality provided by the corresponding feature modules. With continued reference to FIG. 14, a successfully thawed application contains an entry module and all properties module, at which point the user can use the full functionality of the application.

It will be appreciated that when thawing the target application, the user can directly open the target application without waiting and can directly use the functions of the portal module because the portal module is preserved when thawing. The mobile phone 100 downloads the feature module in the background while the user uses the portal module function, and the thawing process is fast and convenient, and has no waiting time basically.

Fig. 15 shows a schematic structural diagram of the mobile phone 100 according to an embodiment of the present application.

As shown in fig. 15, the mobile phone 100 may include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (universal serial bus, USB) interface 130, a charge management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, an earphone interface 170D, a sensor module 180, keys 190, a motor 191, an indicator 192, a camera 193, a display 194, a user identification module (subscriber identification module, SIM) card interface 195, and the like. The sensor module 180 may include a pressure sensor 180A, a gyroscope sensor 180B, an air pressure sensor 180C, a magnetic sensor 180D, an acceleration sensor 180E, a distance sensor 180F, a proximity sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, an ambient light sensor 180L, and the like.

It should be understood that the structure illustrated in the embodiments of the present invention is not limited to the specific embodiment of the mobile phone 100. In other embodiments of the present application, the handset 100 may include more or fewer components than shown, or certain components may be combined, or certain components may be split, or different arrangements of components may be provided. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

The processor 110 may include one or more processing units, such as: the processor 110 may include an application processor (application processor, AP), a modem processor, a graphics processor (graphics processing unit, GPU), an image signal processor (image signal processor, ISP), a controller, a video codec, a digital signal processor (digital signal processor, DSP), a baseband processor, and/or a neural network processor (neural-network processing unit, NPU), etc. Wherein the different processing units may be separate devices or may be integrated in one or more processors.

The controller can generate operation control signals according to the instruction operation codes and the time sequence signals to finish the control of instruction fetching and instruction execution.

A memory may also be provided in the processor 110 for storing instructions and data. In some embodiments, the memory in the processor 110 is a cache memory. The memory may hold instructions or data that the processor 110 has just used or recycled. If the processor 110 needs to reuse the instruction or data, it can be called directly from the memory. Repeated accesses are avoided and the latency of the processor 110 is reduced, thereby improving the efficiency of the system.

In some embodiments, the processor 110 may include one or more interfaces. The interfaces may include an integrated circuit (inter-integrated circuit, I2C) interface, an integrated circuit built-in audio (inter-integrated circuit sound, I2S) interface, a pulse code modulation (pulse code modulation, PCM) interface, a universal asynchronous receiver transmitter (universal asynchronous receiver/transmitter, UART) interface, a mobile industry processor interface (mobile industry processor interface, MIPI), a general-purpose input/output (GPIO) interface, a subscriber identity module (subscriber identity module, SIM) interface, and/or a universal serial bus (universal serial bus, USB) interface, among others.

The USB interface 130 is an interface conforming to the USB standard specification, and may specifically be a Mini USB interface, a Micro USB interface, a USB Type C interface, or the like. The USB interface 130 may be used to connect to a charger to charge the mobile phone 100, or may be used to transfer data between the mobile phone 100 and a peripheral device. And can also be used for connecting with a headset, and playing audio through the headset. The interface may also be used to connect other electronic devices, such as AR devices, etc.

It should be understood that the connection relationship between the modules illustrated in the embodiment of the present invention is only illustrative, and is not limited to the structure of the mobile phone 100. In other embodiments of the present application, the mobile phone 100 may also use different interfacing manners, or a combination of multiple interfacing manners in the foregoing embodiments.

The charge management module 140 is configured to receive a charge input from a charger. The charger can be a wireless charger or a wired charger. In some wired charging embodiments, the charge management module 140 may receive a charging input of a wired charger through the USB interface 130. The power management module 141 is used for connecting the battery 142, and the charge management module 140 and the processor 110. The power management module 141 receives input from the battery 142 and/or the charge management module 140 to power the processor 110, the internal memory 121, the display 194, the camera 193, the wireless communication module 160, and the like.

The wireless communication function of the mobile phone 100 may be implemented by the antenna 1, the antenna 2, the mobile communication module 150, the wireless communication module 160, a modem processor, a baseband processor, and the like.

The antennas 1 and 2 are used for transmitting and receiving electromagnetic wave signals. Each antenna in the handset 100 may be used to cover a single or multiple communication bands. Different antennas may also be multiplexed to improve the utilization of the antennas. For example: the antenna 1 may be multiplexed into a diversity antenna of a wireless local area network. In other embodiments, the antenna may be used in conjunction with a tuning switch.

The mobile communication module 150 may provide a solution for wireless communication including 2G/3G/4G/5G, etc. applied to the handset 100. The wireless communication module 160 may provide solutions for wireless communication including wireless local area network (wireless local area networks, WLAN) (e.g., wireless fidelity (wireless fidelity, wi-Fi) network), bluetooth (BT), global navigation satellite system (global navigation satellite system, GNSS), frequency modulation (frequency modulation, FM), near field wireless communication technology (near field communication, NFC), infrared technology (IR), etc. applied to the handset 100.

In some embodiments, the antenna 1 and the mobile communication module 150 of the handset 100 are coupled, and the antenna 2 and the wireless communication module 160 are coupled, so that the handset 100 can communicate with a network and other devices through wireless communication technology. The wireless communication techniques may include the Global System for Mobile communications (global system for mobile communications, GSM), general packet radio service (general packet radio service, GPRS), code division multiple access (code division multiple access, CDMA), wideband code division multiple access (wideband code division multiple access, WCDMA), time division code division multiple access (time-division code division multiple access, TD-SCDMA), long term evolution (long term evolution, LTE), BT, GNSS, WLAN, NFC, FM, and/or IR techniques, among others. The GNSS may include a global satellite positioning system (global positioning system, GPS), a global navigation satellite system (global navigation satellite system, GLONASS), a Beidou satellite navigation system (beidou navigation satellite system, BDS), a quasi zenith satellite system (quasi-zenith satellite system, QZSS) and/or a satellite based augmentation system (satellite based augmentation systems, SBAS).

The mobile phone 100 implements display functions through a GPU, a display 194, an application processor, and the like. The GPU is a microprocessor for image processing, and is connected to the display 194 and the application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. Processor 110 may include one or more GPUs that execute program instructions to generate or change display information.

The display screen 194 is used to display images, videos, and the like. The display 194 includes a display panel. The display panel may employ a liquid crystal display (liquid crystal display, LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode (AMOLED) or an active-matrix organic light-emitting diode (matrix organic light emitting diode), a flexible light-emitting diode (flex), a Mini-LED, a Micro-OLED, a quantum dot light-emitting diode (quantum dot light emitting diodes, QLED), or the like. In some embodiments, the cell phone 100 may include 1 or N display screens 194, N being a positive integer greater than 1.

The mobile phone 100 may implement photographing functions through an ISP, a camera 193, a video codec, a GPU, a display 194, an application processor, and the like.

The ISP is used to process data fed back by the camera 193. For example, when photographing, the shutter is opened, light is transmitted to the camera photosensitive element through the lens, the optical signal is converted into an electrical signal, and the camera photosensitive element transmits the electrical signal to the ISP for processing, so that the electrical signal is converted into an image visible to the naked eye.

The camera 193 is used to capture still images or video. The object generates an optical image through the lens and projects the optical image onto the photosensitive element. The photosensitive element may be a charge coupled device (charge coupled device, CCD) or a Complementary Metal Oxide Semiconductor (CMOS) phototransistor. The photosensitive element converts the optical signal into an electrical signal, which is then transferred to the ISP to be converted into a digital image signal. The ISP outputs the digital image signal to the DSP for processing. The DSP converts the digital image signal into an image signal in a standard RGB, YUV, or the like format. In some embodiments, the cell phone 100 may include 1 or N cameras 193, N being a positive integer greater than 1.

The external memory interface 120 may be used to connect an external memory card, such as a Micro SD card, to extend the memory capabilities of the handset 100. The external memory card communicates with the processor 110 through an external memory interface 120 to implement data storage functions. For example, files such as music, video, etc. are stored in an external memory card.

The internal memory 121 may be used to store computer executable program code that includes instructions. The internal memory 121 may include a storage program area and a storage data area. The storage program area may store an application program (such as a sound playing function, an image playing function, etc.) required for at least one function of the operating system, etc. The storage data area may store data (e.g., audio data, phonebook, etc.) created during use of the handset 100, etc. In addition, the internal memory 121 may include a high-speed random access memory, and may further include a nonvolatile memory such as at least one magnetic disk storage device, a flash memory device, a universal flash memory (universal flash storage, UFS), and the like. The processor 110 performs various functional applications and data processing of the mobile phone 100 by executing instructions stored in the internal memory 121 and/or instructions stored in a memory provided in the processor.

The handset 100 may implement audio functions through an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, an earphone interface 170D, an application processor, and the like. Such as music playing, recording, etc.

The audio module 170 is used to convert digital audio information into an analog audio signal output and also to convert an analog audio input into a digital audio signal. The audio module 170 may also be used to encode and decode audio signals. In some embodiments, the audio module 170 may be disposed in the processor 110, or a portion of the functional modules of the audio module 170 may be disposed in the processor 110.

The speaker 170A, also referred to as a "horn," is used to convert audio electrical signals into sound signals. The handset 100 may listen to music, or to hands-free calls, through the speaker 170A.

A receiver 170B, also referred to as a "earpiece", is used to convert the audio electrical signal into a sound signal. When the handset 100 is answering a telephone call or voice message, the voice can be received by placing the receiver 170B close to the human ear.

Microphone 170C, also referred to as a "microphone" or "microphone", is used to convert sound signals into electrical signals. When making a call or transmitting voice information, the user can sound near the microphone 170C through the mouth, inputting a sound signal to the microphone 170C. The handset 100 may be provided with at least one microphone 170C. In other embodiments, the mobile phone 100 may be provided with two microphones 170C, and may implement a noise reduction function in addition to collecting sound signals. In other embodiments, the mobile phone 100 may further be provided with three, four or more microphones 170C to collect sound signals, reduce noise, identify the source of sound, implement directional recording, etc.

The earphone interface 170D is used to connect a wired earphone. The headset interface 170D may be a USB interface 130 or a 3.5mm open mobile electronic device platform (open mobile terminal platform, OMTP) standard interface, a american cellular telecommunications industry association (cellular telecommunications industry association of the USA, CTIA) standard interface.

The pressure sensor 180A is used to sense a pressure signal, and may convert the pressure signal into an electrical signal. In some embodiments, the pressure sensor 180A may be disposed on the display screen 194. The pressure sensor 180A is of various types, such as a resistive pressure sensor, an inductive pressure sensor, a capacitive pressure sensor, and the like. The capacitive pressure sensor may be a capacitive pressure sensor comprising at least two parallel plates with conductive material. The capacitance between the electrodes changes when a force is applied to the pressure sensor 180A. The handset 100 determines the strength of the pressure from the change in capacitance. When a touch operation is applied to the display 194, the mobile phone 100 detects the intensity of the touch operation according to the pressure sensor 180A. The mobile phone 100 may also calculate the position of the touch based on the detection signal of the pressure sensor 180A. In some embodiments, touch operations that act on the same touch location, but at different touch operation strengths, may correspond to different operation instructions. For example: and executing an instruction for checking the short message when the touch operation with the touch operation intensity smaller than the first pressure threshold acts on the short message application icon. And executing an instruction for newly creating the short message when the touch operation with the touch operation intensity being greater than or equal to the first pressure threshold acts on the short message application icon.

The fingerprint sensor 180H is used to collect a fingerprint. The mobile phone 100 can utilize the collected fingerprint characteristics to realize fingerprint unlocking, access an application lock, fingerprint photographing, fingerprint incoming call answering and the like.

The touch sensor 180K, also referred to as a "touch device". The touch sensor 180K may be disposed on the display screen 194, and the touch sensor 180K and the display screen 194 form a touch screen, which is also called a "touch screen". The touch sensor 180K is for detecting a touch operation acting thereon or thereabout. The touch sensor may communicate the detected touch operation to the application processor to determine the touch event type. Visual output related to touch operations may be provided through the display 194. In other embodiments, the touch sensor 180K may be disposed on the surface of the mobile phone 100 at a different location than the display 194. In the present application, during the process of executing the freezing application and the thawing application, the user performs corresponding operations on the display screen 194 of the mobile phone 100, and the touch sensor may transmit the detected user touch operation to the application processor to determine the touch event type, so that the mobile phone 100 performs freezing and thawing processing of the application.

The keys 190 include a power-on key, a volume key, etc. The keys 190 may be mechanical keys. Or may be a touch key. The handset 100 may receive key inputs, generating key signal inputs related to user settings and function control of the handset 100.

The motor 191 may generate a vibration cue. The motor 191 may be used for incoming call vibration alerting as well as for touch vibration feedback. For example, touch operations acting on different applications (e.g., photographing, audio playing, etc.) may correspond to different vibration feedback effects. The motor 191 may also correspond to different vibration feedback effects by touching different areas of the display screen 194. Different application scenarios (such as time reminding, receiving information, alarm clock, game, etc.) can also correspond to different vibration feedback effects. The touch vibration feedback effect may also support customization.

The indicator 192 may be an indicator light, may be used to indicate a state of charge, a change in charge, a message indicating a missed call, a notification, etc.

The SIM card interface 195 is used to connect a SIM card. The SIM card may be inserted into the SIM card interface 195 or removed from the SIM card interface 195 to enable contact and separation with the handset 100.

Reference in the specification to "one embodiment" or "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one example implementation or technique disclosed in accordance with embodiments of the present application. The appearances of the phrase "in one embodiment" in various places in the specification are not necessarily all referring to the same embodiment.

The disclosure of the embodiments of the present application also relates to an operating device for executing the text. The apparatus may be specially constructed for the required purposes, or it may comprise a general-purpose computer selectively activated or reconfigured by a computer program stored in the computer. Such a computer program may be stored in a computer readable medium, such as, but is not limited to, any type of disk including floppy disks, optical disks, CD-ROMs, magnetic-optical disks, read-only memories (ROMs), random Access Memories (RAMs), EPROMs, EEPROMs, magnetic or optical cards, application Specific Integrated Circuits (ASICs), or any type of media suitable for storing electronic instructions, and each may be coupled to a computer system bus. Furthermore, the computers referred to in the specification may include a single processor or may be architectures employing multiple processors for increased computing power.

Additionally, the language used in the specification has been principally selected for readability and instructional purposes, and may not have been selected to delineate or circumscribe the disclosed subject matter. Accordingly, the present application example disclosure is intended to be illustrative, but not limiting, of the scope of the concepts discussed herein.

Claims

1. An application management method applied to an electronic device, comprising:

detecting a first user operation on a first application, wherein the first user operation is used for indicating to switch the state of the first application from an available state to a disabled state;

switching the first application into a disabled state, reserving a first type module of the first application, and deleting a second type module of the first application;

detecting a second user operation on a first application, wherein the second user operation is used for indicating that the state of the first application is switched from a forbidden state to an available state;

running the first application based on the reserved first type module, and installing the deleted second type module;

and switching the first application into an available state.

2. The method of claim 1, wherein the first application comprises historical user data, wherein the historical user data is application data correspondingly generated by the electronic device in response to user operations on an interface of the first application; and, the method comprises:

the historical user data is retained in response to the first user operation.

3. The method of claim 2, wherein the electronic device comprises a list of modules corresponding to the first application, wherein the list of modules comprises at least identification information and path information for the first type of module and the second type of module, and wherein,

the deleting the second type module of the first application includes:

based on the identification information and the path information of the second type module recorded in the module list, accessing the storage space where the second type module is located and deleting the second type module.

4. A method according to claim 3, wherein said installing said deleted second class of modules comprises:

and sequentially installing the second type modules based on the identification information of the second type modules recorded in the module list.

5. The method of claim 4, wherein the order in which the second type of modules are installed in turn is determined by any one of:

counting the use frequency of the user on the first application based on the functions correspondingly provided by the second type modules based on the historical user data, and determining the order from high to low according to the use frequency based on the counting result;

Based on the size of the data volume corresponding to the second type module, determining the sequence from small to large or the sequence from large to small according to the data volume;

an order of preferentially downloading second type modules for providing the first function is determined based on a first function used by a user operation instruction on an interface of the running first application.

6. The method of any one of claims 1 to 5, wherein the second type of module comprises a deleted first version and an update published second version, and wherein,

the installing the deleted second type module includes:

installing the second type module of the first version based on a default setting; or,

and installing the second type module of the second version based on user settings, wherein the user settings specify operations to install the update published second type module.

7. The method of any of claims 1-6, wherein the electronic device displays a desktop, the desktop including an icon of a first application, and the switching the first application to a disabled state comprises:

and switching the icon of the first application from a first display mode to a second display mode, wherein the first display mode is a mode indicating that the first application is in an available state, and the second display mode is a mode indicating that the first application is in a disabled state.

8. The method of claim 7, wherein the switching the first application to an available state comprises:

and switching the icon of the first application from the second display mode to the first display mode.

9. The method of claim 7 or 8, wherein the first user operation comprises:

pressing the icon of the first application on the desktop for a long time, and selecting an operation of setting the first application to a disabled state; or,

and long-pressing the icon of the first application on the desktop, and dragging the icon of the first application to a target folder, wherein the target folder comprises application programs in a disabled state.

10. The method of claim 9, wherein the second user operation comprises:

long-pressing an icon of the first application on the desktop, and selecting an operation of setting the first application to an available state; or,

and opening the target folder and dragging the icon of the first application from the target folder to the desktop.

11. An application management apparatus, comprising: the package management subsystem is used for responding to the detected first user operation on the first application and switching the first application into a disabled state; or, in response to a detected second user operation on a first application, switching the first application to an available state, wherein the first user operation is used for indicating that the state of the first application is switched from the available state to a disabled state, and the second user operation is used for indicating that the state of the first application is switched from the disabled state to the available state; and, in addition, the processing unit,

The packet management subsystem includes:

the scanning module is used for responding to the first user operation or the second user operation, scanning the module list of the first application and determining the identification information and the path information of the first type module and the second type module of the first application;

the installation management module is used for responding to the first user operation, reserving a first type module of the first application and deleting a second type module of the first application; and installing the deleted second class module in response to the second user operation.

12. An electronic device, comprising: one or more processors; one or more memories; the one or more memories stores one or more programs that, when executed by the one or more processors, cause the electronic device to perform the application management method of any of claims 1-10.

13. A computer readable storage medium having stored thereon instructions which, when executed on a computer, cause the computer to perform the application management method of any of claims 1 to 10.