CN116974434A

CN116974434A - Display method and electronic equipment

Info

Publication number: CN116974434A
Application number: CN202210426387.1A
Authority: CN
Inventors: 杨德志; 孙靓
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2022-04-22
Filing date: 2022-04-22
Publication date: 2023-10-31
Also published as: WO2023202406A1

Abstract

The application provides a display method and electronic equipment, relates to the technical field of electronic equipment, and can effectively clean a keep-alive application process and solve various problems caused by the keep-alive of the application process. The method is applied to the electronic equipment with the display screen, and comprises the following steps: and receiving a first operation of a user, and responding to the first operation, acquiring details of the application, wherein the details of the application comprise whether the application is resident in the background of the electronic equipment. The details of the application are displayed and used for indicating that the user can avoid the application resident in the background of the electronic device by uninstalling the application or not installing the application. And receiving a second operation of the user, and unloading the application in response to the second operation.

Description

Display method and electronic equipment

Technical Field

The present application relates to the field of electronic devices, and in particular, to a display method and an electronic device.

Background

Currently, android-based (Android)The electronic devices of the system have taken up a significant market share. In these electronic devices, some application processes may have a need to run in the background all the time, so to avoid that these application processes are checked out or suspended, the electronic device may use various keep-alive strategies to ensure the continuous running of these application processes.

However, as the background running application processes of the electronic device are increased, various problems such as system blocking and numerous advertisements of the electronic device occur, which brings inconvenience to users. Therefore, in order to ensure the running stability of the electronic device, a plurality of schemes for cleaning application processes are provided in the prior art, but the schemes may only be capable of cleaning partial keep-alive application processes, solving the problem of partial blocking of the electronic device, and not effectively solving various problems brought by the keep-alive application processes to the electronic device.

Disclosure of Invention

The application provides a display method and electronic equipment, which can effectively clean a keep-alive application process and solve various problems brought to the electronic equipment by the keep-alive application process.

In order to achieve the above purpose, the application adopts the following technical scheme:

in a first aspect, the present application provides a display method applied to an electronic device having a display screen, where the method includes: receiving a first operation of a user; in response to the first operation, acquiring details of the application, wherein the details of the application comprise whether the application is resident in the background of the electronic equipment; displaying details of the application, wherein the details of the application are used for indicating a user to avoid the application from residing in the background of the electronic device by uninstalling the application or not installing the application; receiving a second operation of the user; in response to the second operation, the application is uninstalled.

Based on the technical scheme, the electronic equipment can acquire and display the details of the application according to the operation of the user, and the details of the application comprise whether the application can be resident in the background of the electronic equipment, namely whether the application is a keep-alive application, so that the user can decide whether to install or uninstall an application according to the details of the application. Therefore, by informing the user whether an application exists in the keep-alive behavior, the user can decide whether to install or uninstall the application by himself, convenience can be brought to the user, and the efficiency of man-machine interaction is improved. If the user selects to uninstall or not install the keep-alive application, the problem that the application cannot be thoroughly checked out can be solved, so that various problems brought by the keep-alive application to the electronic equipment are avoided.

In one possible design, the details of the application may further include one or more of an explanation of the background resident, an impact of the background resident on the electronic device, and a number of processes that the application initiates while the background resident on the electronic device. Based on the design, a user can more clearly know the influence possibly brought by the keep-alive application on the electronic equipment, whether to install or uninstall an application can be more reasonably judged, and convenience is brought to the user.

In one possible design, the details of the application are determined based on the target characteristics of the application, which may be used for keep-alive applications; wherein the target features include one or more of: services, static broadcasting, inter-application mutual pulling, message pushing, timed wake-up, calling Dalvik virtual machine DEX byte codes through an API, calling ELF codes through the API, and calling the API in the ELF codes.

In one possible design, the target features of the application include static features of the application and/or dynamic features of the application; the static characteristics of the application are obtained by analyzing the codes of the installation packages corresponding to the application, and the dynamic characteristics of the application are obtained by constructing the codes of the installation packages corresponding to the sandboxed running application.

In this design, the target features of the application may include static features and dynamic sandboxed features of the application. Since the application may do some confusion, encryption, etc. in the configuration file, the behavior that the application may have may not be fully detected by merely detecting the static features of the application. Thus, the behavior of the application in real running can also be obtained by obtaining the dynamic sandboxed feature of the application. In addition, certain actions of an application may need to be triggered under certain conditions, such as: the electronic device is triggered under the condition that the electric quantity of the electronic device is 80%, so that possible behaviors of the application can not be comprehensively detected only by detecting the dynamic sandbox characteristics of the application, and therefore, behaviors of the application which are not detected when the application is run by using the dynamic sandbox can be obtained by obtaining the static characteristics of the application. In summary, by detecting the static features and the dynamic sandbox features of the application, that is, by combining the static detection and the dynamic sandbox detection, some behaviors possibly existing in the application can be more comprehensively obtained, and the accuracy of the generated application details is improved.

In one possible design, in response to a first operation, obtaining details of an application includes: in response to the first operation, details of the application are obtained from the server.

In one possible design, the obtaining of the details of the application from the server includes: sending a request message to a server, wherein the request message comprises version of an operating system of the electronic equipment and/or identification information of an application; details of the application are received from the server. Based on the design, the details of the application received by the electronic equipment are adapted to the current electronic equipment, the server only returns a part of the application details, the application details can be prevented from being stolen by others, the information safety is improved, the information transmission quantity between the server and the electronic equipment can be reduced, and the communication efficiency between the server and the electronic equipment is improved.

In a second aspect, the present application provides a display method, applied to a server, the method including: receiving a request message from an electronic device; sending the application details to the electronic equipment according to the request message; the details of the application include, among other things, whether the application will reside in the background of the electronic device.

In one possible design, the details of the application may further include one or more of an explanation of the background resident, an impact of the background resident on the electronic device, and a number of processes that the application initiates while the background resident on the electronic device.

In one possible design, the request message includes identification information of a version and/or an application of an operating system of the electronic device; transmitting details of the application to the electronic device according to the request message, including: determining details of an application corresponding to the electronic device according to the version of an operating system of the electronic device and/or identification information of the application; and sending the details of the application corresponding to the electronic device.

In one possible design, sending details of an application to an electronic device according to a request message includes: and sending the details of all the applications to the electronic equipment according to the request message.

In one possible design, the method may further include, prior to receiving the request message from the electronic device: generating details of the application according to the target characteristics of the application, wherein the target characteristics of the application can be used for keep-alive application; wherein the target features include one or more of: services, static broadcasting, inter-application mutual pulling, message pushing, timed wake-up, calling Dalvik virtual machine DEX byte codes through an API, calling ELF codes through the API, and calling the API in the ELF codes.

In a third aspect, the present application provides an electronic device having functionality to implement the method as described in the first aspect and any one of the designs. The functions can be realized by hardware, and can also be realized by executing corresponding software by hardware. The hardware or software includes one or more modules corresponding to the functions described above.

In a fourth aspect, the application provides an electronic device comprising a processor, a memory and a display screen, the memory and the display screen being coupled to the processor, the memory being for storing computer program code, the computer program code comprising computer instructions, the processor reading the computer instructions from the memory to cause the electronic device to perform the method as described in the second aspect and any one of the designs described above. Alternatively, the memory may be provided separately from the processor or integrated with the processor.

In one possible design, the electronic device further includes a communication interface operable to communicate with other devices (e.g., a server). By way of example, the communication interface may be a transceiver, an input/output interface, an interface circuit, an output circuit, an input circuit, a pin or related circuit, or the like.

In a fifth aspect, the present application provides a server having the functionality to implement the method as described in the second aspect and any one of the designs. The functions can be realized by hardware, and can also be realized by executing corresponding software by hardware. The hardware or software includes one or more modules corresponding to the functions described above.

In a sixth aspect, the present application provides a server comprising a processor and a memory coupled to the processor, the memory for storing computer program code, the computer program code comprising computer instructions, the processor reading the computer instructions from the memory to cause the server to perform the method as described in the second aspect and any one of the designs above. Alternatively, the memory may be provided separately from the processor or integrated with the processor.

In one possible design, the server may further include a communication interface operable to communicate with other devices (e.g., electronic devices) by the server. By way of example, the communication interface may be a transceiver, an input/output interface, an interface circuit, an output circuit, an input circuit, a pin or related circuit, or the like.

In a seventh aspect, the present application provides a computer readable storage medium comprising a computer program or instructions which, when run on a computer, cause the computer to perform the method as described in the first aspect and any of the designs described above, or cause the computer to perform the method as described in the second aspect and any of the designs described above.

In an eighth aspect, the present application provides a computer program product comprising: a computer program or instructions which, when run on a computer, causes the computer to perform the method as described in the first aspect and any of the designs described above, or causes the computer to perform the method as described in the second aspect and any of the designs described above.

In a ninth aspect, the present application provides a chip system, comprising at least one processor and at least one interface circuit, the at least one interface circuit being configured to perform a transceiving function and to send instructions to the at least one processor, when executing the instructions, performing the method according to the first aspect and any one of the designs described above, or performing the method according to the second aspect and any one of the designs described above.

In a tenth aspect, the present application provides a communication system, including the electronic device provided in the third aspect or the fourth aspect, and the server provided in the fifth aspect or the sixth aspect.

It should be noted that the technical effects of any one of the designs in the second aspect to the tenth aspect may be referred to the technical effects of the corresponding design in the first aspect, and will not be described herein.

Drawings

FIG. 1 is a flow chart of a conventional method for cleaning an application process;

FIG. 2 is a flow chart of another method for cleaning an application process according to the prior art;

fig. 3 is a schematic diagram of a communication system according to an embodiment of the present application;

fig. 4 is a schematic hardware structure of a server according to an embodiment of the present application;

fig. 5 is a schematic hardware structure of an electronic device according to an embodiment of the present application;

FIG. 6 is a block diagram of a software architecture of an electronic device and a server according to an embodiment of the present application;

FIG. 7 is a flowchart of a method for generating details of an application according to an embodiment of the present application;

FIG. 8 is a schematic flow chart of a display method according to an embodiment of the present application;

FIG. 9 is a schematic diagram of a set of interfaces provided in accordance with an embodiment of the present application;

FIG. 10 is a schematic diagram of another set of interfaces provided in accordance with an embodiment of the present application;

FIG. 11 is a schematic diagram of another set of interfaces provided in accordance with an embodiment of the present application;

FIG. 12 is a schematic view of another set of interfaces provided in accordance with an embodiment of the present application;

FIG. 13 is a schematic diagram of another set of interfaces provided in accordance with an embodiment of the present application;

FIG. 14 is a schematic view of another set of interfaces provided in accordance with an embodiment of the present application;

FIG. 15 is a schematic view of another set of interfaces provided in accordance with an embodiment of the present application;

FIG. 16 is a schematic view of another set of interfaces provided in accordance with an embodiment of the present application;

FIG. 17 is a flowchart of another display method according to an embodiment of the present application;

fig. 18 is a schematic structural diagram of an electronic device according to an embodiment of the present application;

fig. 19 is a schematic structural diagram of a server according to an embodiment of the present application;

fig. 20 is a schematic structural diagram of a chip system according to an embodiment of the present application.

Detailed Description

The display method and the electronic device provided by the embodiment of the application are described in detail below with reference to the accompanying drawings.

The terms "comprising" and "having" and any variations thereof, as referred to in the description of the application, are intended to cover non-exclusive inclusion. For example, a process, method, system, article, or apparatus that comprises a list of steps or elements is not limited to only those listed but may optionally include other steps or elements not listed or inherent to such process, method, article, or apparatus.

It should be noted that, in the embodiments of the present application, words such as "exemplary" or "such as" are used to mean serving as an example, instance, or illustration. Any embodiment or design described herein as "exemplary" or "e.g." in an embodiment should not be taken as preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary" or "such as" is intended to present related concepts in a concrete fashion.

In the description of the present application, unless otherwise indicated, the meaning of "a plurality" means two or more. "and/or" herein is merely an association relationship describing an association object, and means that three relationships may exist, for example, a and/or B may mean: a exists alone, A and B exist together, and B exists alone.

Currently, there may be a need for application processes in an electronic device to run in the background all the time, so to avoid that the application processes are checked out or suspended, the electronic device may use various keep-alive strategies to ensure the continuous running of the application processes. It can be appreciated that the keep-alive policy is a means by which a user actively kills an application process for protecting himself from killing. Or, the keep-alive strategy is a means that the application process can be restarted immediately after the application process is used for being checked and killed after the electronic equipment system automatically triggers and cleans the application process. However, as the background running application processes are more and more, various problems such as system blocking, numerous advertisements and the like of the electronic equipment occur, and inconvenience is brought to users. Therefore, in order to ensure the running stability of the electronic device, many schemes for cleaning the application process are given in the prior art.

By way of example, FIG. 1 illustrates an existing scheme for cleaning up application processes. Triggering the memory searching and killing under the condition of insufficient memory of the electronic equipment, traversing an application process (or simply referred to as a process), screening out the process with the lowest priority, judging whether the process is perceived by a user, if so, adding a white list, and abandoning searching and killing; if not, the process is checked and killed. And judging whether the memory of the electronic equipment reaches the expectation or not, if so, ending the memory checking and killing process, and if not, continuing the memory checking and killing process. In this scheme, the electronic device may only search for application processes with low priority and imperceptible to the user, but in general, the priority of the application process with keep-alive is higher, and the scheme may not be able to search for the application process with keep-alive. And, even if the keep-alive application process can be killed, the keep-alive application process is frequently pulled up after being killed, so that the keep-alive application process cannot be completely closed. In addition, the scheme can trigger the process of memory check and kill only when the memory of the electronic equipment is low, and can only solve the problem of partial blocking of the electronic equipment, but when the memory of the electronic equipment is enough, some useless keep-alive application processes can always run in the background, and the scheme does not perform any processing on the useless application processes, so that the waste of resources of the electronic equipment can be caused, and the power consumption of the electronic equipment can be increased.

By way of example, FIG. 2 illustrates yet another existing scheme for cleaning application processes. After an application (or application program) is started, judging whether the application is started in an Activity type, if so, determining that the application is actively clicked to start or legally started by a user, and then recovering a previously disabled wake-up starting component, namely restarting the previously checked application process; if not, determining that the application is background startup. And judging whether the white list is allowed to be started, if so, judging that the application is actively clicked or legally started, recovering the forbidden wake-up starting component before restoring, and if not, cleaning the application process. In this scheme, only can clear up the application process that starts and be located outside the white list in the backstage, can not clear up other types of application process, say: an application process which is started by the active click of a user (namely, manually wakes up) and always runs in the background cannot be cleaned.

Therefore, the above solutions may not be capable of effectively cleaning the keep-alive application process, and may not be capable of effectively solving various problems caused by the keep-alive application process to the electronic device.

Based on the method, the application provides a display method, which can effectively clean the application process with keep-alive, solves various problems brought to the electronic equipment by the keep-alive of the application process, improves the efficiency of man-machine interaction and brings convenience to users.

Fig. 3 is a schematic diagram of a communication system to which a display method according to an embodiment of the present application is applied. As shown in fig. 3, the communication system includes at least one electronic device 100 and a server 200.

Alternatively, the electronic device 100 may be a mobile phone (mobile phone), a personal computer (personal computer, PC), a tablet (Pad), a notebook, a desktop, a notebook, a computer with a transceiver function, a Virtual Reality (VR) terminal device, an augmented reality (augmented reality, AR) terminal device, a wearable device, a vehicle-mounted device, an artificial intelligence (artificial intelligence, AI) device, or the like. Operating systems installed on electronic device 100 include, but are not limited toOr other operating system. In some embodiments, the electronic device 100 may be a stationary device or a portable device. The application is not limited to the particular type of electronic device 100, nor to the operating system installed.

Alternatively, the server 200 may be a device or server having a computing function, such as a cloud server or a network server. The server 200 may be a server, a server cluster formed by a plurality of servers, or a cloud computing service center.

In some embodiments, the electronic device 100 may obtain details of various applications from the server 200 and display the details of the various applications. The application may be an application already installed on the electronic device 100 or an application not installed on the electronic device 100. The details of the application may include, but are not limited to, whether the application supports the process to reside in the background (or whether the application is a keep-alive application, or whether the application has a background-resident behavior, or whether the application has a keep-alive behavior, etc.), relevant interpretations of the background-resident, the impact of the process to reside in the background on the electronic device, etc. The application details may be used to assist the user in determining whether to install an application or uninstall an application.

Alternatively, the server 200 in the embodiment of the present application may be implemented by different devices. For example, the server 200 in the embodiment of the present application may be implemented by the communication device in fig. 4. Fig. 4 is a schematic hardware structure of a server 200 according to an embodiment of the present application. The server 200 comprises at least one processor 401, communication lines 402, a memory 403 and at least one communication interface 404.

The processor 401 may be a general purpose central processing unit (central processing unit, CPU), microprocessor, application-specific integrated circuit (ASIC), or one or more integrated circuits for controlling the execution of the program of the present application.

Communication line 402 may include a pathway to transfer information between the aforementioned components.

A communication interface 404 for communicating with other devices. In the embodiment of the present application, the communication interface may be a module, a circuit, a bus, an interface, a transceiver, or other devices capable of implementing a communication function, for communicating with other devices. Alternatively, when the communication interface is a transceiver, the transceiver may be a separately provided transmitter that is operable to transmit information to other devices, or a separately provided receiver that is operable to receive information from other devices. The transceiver may also be a component that integrates the functions of transmitting and receiving information, and embodiments of the present application are not limited to the specific implementation of the transceiver.

The memory 403 may be, but is not limited to, a read-only memory (ROM) or other type of static storage device that can store static information and instructions, a random access memory (random access memory, RAM) or other type of dynamic storage device that can store information and instructions, or an electrically erasable programmable read-only memory (electrically erasable programmable read-only memory, EEPROM), a compact disc read-only memory (compact disc read-only memory) or other optical disc storage, a compact disc storage (including compact disc, laser disc, optical disc, digital versatile disc, blu-ray disc, etc.), a magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer. The memory 403 may be stand alone and be connected to the processor 401 by a communication line 402. Memory 403 may also be integrated with processor 401.

Wherein the memory 403 is used for storing computer-executable instructions for implementing the inventive arrangements and is controlled for execution by the processor 401. The processor 401 is configured to execute computer-executable instructions stored in the memory 403, thereby implementing the display method provided in the following embodiments of the present application.

Alternatively, the computer-executable instructions in the embodiments of the present application may be referred to as application code, instructions, computer programs, or other names, and the embodiments of the present application are not limited in detail.

In a particular implementation, processor 401 may include one or more CPUs, such as CPU0 and CPU1 of FIG. 4, as an embodiment.

In a particular implementation, as one embodiment, server 200 may include multiple processors, such as processor 401 and processor 405 in FIG. 4. Each of these processors may be a single-core (single-CPU) processor or may be a multi-core (multi-CPU) processor. A processor herein may refer to one or more devices, circuits, and/or processing cores for processing data (e.g., computer program instructions).

The server 200 may be a general-purpose device or a special-purpose device, and the embodiment of the present application is not limited to the type of server 200. The server 200 may be a device having a similar structure to that of fig. 4.

It should be understood that the structure illustrated in the embodiments of the present application does not constitute a specific limitation on the server 200. In other embodiments of the application, server 200 may include more or fewer components than shown, or certain components may be combined, or certain components may be split, or a different arrangement of components. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

Taking an electronic device as an example of a mobile phone, fig. 5 shows a schematic structural diagram of the electronic device 100.

Electronic device 100 may include a processor 510, an external memory interface 520, an internal memory 521, a universal serial bus (universal serial bus, USB) interface 530, a charge management module 540, a power management module 541, a battery 542, an antenna 1, an antenna 2, a mobile communication module 550, a wireless communication module 560, an audio module 570, a sensor module 580, keys 590, a motor 591, an indicator 592, a camera 593, a display screen 594, and a subscriber identity module (subscriber identification module, SIM) card interface 595, among others.

Processor 510 may include one or more processing units, such as: processor 510 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 510 for storing instructions and data. In some embodiments, the memory in processor 510 is a cache memory. The memory may hold instructions or data that has just been used or recycled by the processor 510. If the processor 510 needs to reuse the instruction or data, it may be called directly from the memory. Repeated accesses are avoided and the latency of the processor 510 is reduced, thereby improving the efficiency of the system.

In some embodiments, processor 510 may include one or more interfaces.

The charge management module 540 is configured to receive a charge input from a charger. The charger can be a wireless charger or a wired charger.

The power management module 541 is configured to connect the battery 542, the charge management module 540, and the processor 510. The power management module 541 receives input from the battery 542 and/or the charge management module 540 and provides power to the processor 510, the internal memory 521, the display screen 594, the camera 593, the wireless communication module 560, and the like.

The wireless communication function of the electronic device 100 can be implemented by the antenna 1, the antenna 2, the mobile communication module 550, the wireless communication module 560, 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 electronic device 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 550 may provide a solution for wireless communication including 2G/3G/4G/5G, etc., applied on the electronic device 100. The mobile communication module 550 may include at least one filter, switch, power amplifier, low noise amplifier (low noise amplifier, LNA), etc.

The wireless communication module 560 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 electronic device 100.

In some embodiments, antenna 1 and mobile communication module 550 of electronic device 100 are coupled, and antenna 2 and wireless communication module 560 are coupled, such that electronic device 100 may communicate with a network and other devices through wireless communication techniques.

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

The display screen 594 is used to display images, videos, and the like. The display screen 594 includes a display panel. In some embodiments, electronic device 100 may include 1 or N displays 594, N being a positive integer greater than 1. In some embodiments of the application, a display screen 594 may be used to display details of the application.

The electronic device 100 may implement shooting functions through an ISP, a camera 593, a video codec, a GPU, a display screen 594, an application processor, and the like.

The camera 593 is used to capture still images or video. In some embodiments, the electronic device 100 may include 1 or N cameras 593, N being a positive integer greater than 1.

The external memory interface 520 may be used to connect an external memory card, such as a Micro SD card, to enable expansion of the memory capabilities of the electronic device 100.

The internal memory 521 may be used to store computer-executable program code that includes instructions. The internal memory 521 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 created during use of the electronic device 100 (e.g., audio data, phonebook, etc.), and so on. The processor 510 performs various functional applications of the electronic device 100 and data processing by executing instructions stored in the internal memory 521 and/or instructions stored in a memory provided in the processor.

The electronic device 100 may implement audio functionality through an audio module 570, an application processor, or the like. Such as music playing, recording, etc.

The audio module 570 is configured to convert digital audio information to an analog audio signal output and also to convert an analog audio input to a digital audio signal. The audio module 570 may also be used to encode and decode audio signals. In some embodiments, the audio module 570 may be provided in the processor 510 or some functional modules of the audio module 570 may be provided in the processor 510.

Alternatively, the sensor module 580 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 light sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, an ambient light sensor 180L, a bone conduction sensor 180M, and the like.

The keys 590 include a power key, a volume key, etc. The keys 590 may be mechanical keys. Or may be a touch key. The electronic device 100 may receive key inputs, generating key signal inputs related to user settings and function controls of the electronic device 100.

Motor 591 may generate a vibration alert.

The indicator 592 may be an indicator light, may be used to indicate a state of charge, a change in charge, may be used to indicate a message, missed call, notification, or the like.

The SIM card interface 595 is used to connect to a SIM card.

The foregoing illustrates the structure of the electronic device 100 in the embodiment of the present application by using a mobile phone, but the structure and the form of the electronic device 100 are not limited. The embodiment of the application does not limit the structure and the form of the electronic device 100. For example: the structure of the electronic device 100 may also take the form of a server 200 such as that shown in fig. 4, to which the present application is not limited.

In other embodiments of the application, the electronic device may include more or fewer components than shown in FIG. 5, or certain components may be combined, certain components may be separated, certain components may be replaced, or different arrangements of components. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

Fig. 6 is a block diagram of a software structure of the electronic device 100 and a block diagram of the server 200 according to an embodiment of the present application.

Alternatively, the software system of the electronic device 100 may employ a layered architecture, an event driven architecture, a micro-core architecture, a micro-service architecture, or a cloud architecture. Embodiments of the application are configured in a layered manner The system is an example illustrating the software architecture of the electronic device 100.

The layered architecture divides the software into several layers, each with distinct roles and branches. The layers communicate with each other through a software interface. In some embodiments, the Android system is divided into four layers, from top to bottom, an application layer, an application framework layer, an Zhuoyun row (Android run) and system libraries, and a kernel layer, respectively.

The application layer may include a series of application packages. As shown in FIG. 6, the application package may include applications such as calendars, maps, settings, browsers, application markets, gallery, navigation, and so forth.

In some embodiments of the present application, application programs such as a setting, a browser, an application market, and the like have a function of displaying details of various applications, and the electronic device detects a related operation of the application programs by a user, and in response to the operation, the electronic device acquires details of the various applications from the server, and displays the details of the various applications on a related interface of the application programs.

The application framework layer provides an application programming interface (application programming interface, API) and programming framework for application programs of the application layer. The application framework layer includes a number of predefined functions.

As shown in fig. 6, the application framework layer may include a window manager, a content provider, a view system, a phone manager, a resource manager, a notification manager, and the like.

The window manager is used for managing window programs. The window manager can acquire the size of the display screen, judge whether a status bar exists, lock the screen, intercept the screen and the like.

The content provider is used to store and retrieve data and make such data accessible to applications. The data may include video, images, audio, calls made and received, browsing history and bookmarks, phonebooks, etc.

The view system includes visual controls, such as controls to display text, controls to display pictures, and the like. The view system may be used to build applications. The display interface may be composed of one or more views. For example, a display interface including a text message notification icon may include a view displaying text and a view displaying a picture.

The telephony manager is used to provide the communication functions of the electronic device 100. Such as the management of call status (including on, hung-up, etc.).

The resource manager provides various resources for the application program, such as localization strings, icons, pictures, layout files, video files, and the like.

The notification manager allows the application to display notification information in a status bar, can be used to communicate notification type messages, can automatically disappear after a short dwell, and does not require user interaction. Such as notification manager is used to inform that the download is complete, message alerts, etc. The notification manager may also be a notification in the form of a chart or scroll bar text that appears on the system top status bar, such as a notification of a background running application, or a notification that appears on the screen in the form of a dialog window. For example, a text message is presented in a status bar, a prompt tone is emitted, and an indicator light blinks, etc.

Android run time includes a core library and virtual machines. Android run time is responsible for scheduling and management of the Android system.

The core library consists of two parts: one part is a function which needs to be called by java language, and the other part is a core library of android.

The application layer and the application framework layer run in a virtual machine. The virtual machine executes java files of the application program layer and the application program framework layer as binary files. The virtual machine is used for executing the functions of object life cycle management, stack management, thread management, security and exception management, garbage collection and the like.

The system library may include a plurality of functional modules. For example: surface manager (surface manager), media Libraries (Media Libraries), three-dimensional graphics processing Libraries (e.g., openGL ES), 2D graphics engines (e.g., SGL), etc.

The surface manager is used to manage the display subsystem and provides a fusion of 2D and 3D layers for multiple applications.

Media libraries support a variety of commonly used audio, video format playback and recording, still image files, and the like. The media library may support a variety of audio and video encoding formats, such as MPEG4, h.264, MP3, AAC, AMR, JPG, PNG, etc.

The three-dimensional graphic processing library is used for realizing three-dimensional graphic drawing, image rendering, synthesis, layer processing and the like.

The 2D graphics engine is a drawing engine for 2D drawing.

The kernel layer is a layer between hardware and software. The kernel layer at least comprises a network driver, a display driver, a camera driver, an audio driver and a sensor driver.

As shown in fig. 6, the server 200 includes a schedule analysis module 601, a storage module 602, and a communication module 603. Wherein the schedule analysis module 601 is used for analyzing and generating details of various applications. The storage module 602 is used for storing details of various applications generated by the schedule analysis module 601, and the communication module 603 is used for transmitting the stored details of various applications to other devices (for example, the electronic device 100).

The electronic device 100 hardware, software, and workflow for interacting with the server 200 are illustrated below in connection with a scenario in which a user opens an application marketplace.

Illustratively, when a touch operation is received by a touch sensor of the electronic device 100, a corresponding hardware terminal is sent to the kernel layer. The kernel layer processes the touch operation into the original input event (including information of touch coordinates, time stamp of touch operation, etc.). The original input event is stored at the kernel layer. The application framework layer acquires an original input event from the kernel layer, and identifies a control corresponding to the input event. Such as: the touch operation is an operation of clicking on an application market of the application layer, which starts a network driver by calling a kernel layer, and transmits a request message, which can be used to acquire details of various applications in the application market, to the server 200 through the wireless communication module 160 or the mobile communication module 150.

Accordingly, the server 200 receives the request message of the electronic device 100 through the communication module 603, and returns details of various applications stored in the storage module 602 to the electronic device 100 through the communication module 603. Accordingly, after the electronic device 100 receives the details of the various applications through the wireless communication module 160 or the mobile communication module 150, the kernel layer is invoked to start the display driver, and the details of the various applications are displayed through the display screen 594.

The following embodiments are all described with the electronic device 100 as a mobile phone and the server 200 as a server.

The embodiment of the application provides a display method, a server generates details of various applications, and the details of the applications include, but are not limited to, whether an application supports a process to reside in the background (or whether the application is a keep-alive application or whether the application has a background resident behavior or whether the application is a keep-alive behavior, etc.), relevant explanation of the background resident, influence of the application process resident in the background on electronic equipment, and the like. The server may then send some or all of the details of the various applications to the handset, which may display the details of the applications. Therefore, the user can decide whether to install or uninstall an application by himself or herself by informing the user of the existence of an application and the influence possibly caused to the electronic device, thereby bringing convenience to the user and improving the efficiency of man-machine interaction. If the user still chooses to install an application after knowing the behavior of the application and the influence that may be caused to the electronic device, it is stated that the behavior of the application and the influence that may be caused to the electronic device are acceptable to the user, so that the user experience is not affected. If the user selects to uninstall or not install an application after knowing the behavior of the application and the influence possibly caused to the electronic device, the problem that the keep-alive application cannot be thoroughly searched and killed can be solved, so that various problems brought to the electronic device by the keep-alive application process are avoided.

The process by which the server generates details of various applications will be described first.

By way of example, fig. 7 shows a flow diagram of a method for a server to generate details of various applications, as shown in fig. 7, the method comprising the following steps.

S701, the server acquires target characteristics of the application.

It will be appreciated that an application may be an application developed by a developer that is then submitted to an application marketplace, a network, a cloud, etc., where the server may obtain the application.

Among the features of the application include a variety of, for example: development characteristics, composition characteristics, operational characteristics, etc. Development characteristics may refer to development languages, development frameworks, etc. used by an application, composition characteristics may refer to components constituting one application, etc., and operation characteristics may refer to characteristics of an application operating in an electronic device, etc.

In the embodiment of the application, the target feature of the application is an operation feature of the application in the electronic equipment system, which can be used for reflecting the behavior of the application when the application runs in the electronic equipment system, and can correspond to the system service for keeping the application alive, namely the target feature can be used for keeping the application alive. Optionally, the target features of the application include one or more of static features, dynamic sandboxed features (i.e., dynamic features). Wherein the static and/or dynamic sandboxed features of an application may be understood as system services used by an application during operation, which may be used to keep alive the processes of an application, such as: these system services may immediately restart the process of an application after it is killed, or ensure that the process of an application is not killed, etc. The static characteristics of an application may refer to system services configured in a configuration file of the application (e.g., a file in an installation package of the application), and the dynamic sandboxed characteristics of the application may refer to system services actually used during the running process of the application. For one application, the static and dynamic sandboxed features that it includes may be the same or different. The target features of an application may include one or more static features at the same time, or one or more dynamic sandboxed features at the same time. For different applications, their corresponding static and dynamic sandboxed features may be the same or different.

By way of example, static features of an application include, but are not limited to, services, static broadcasts, inter-application cross-pulls, registration pushes, wake-on-time, dalvik (Dalvik) virtual machine DEX application programming interfaces (application programming interface, APIs), executable link formats (executable linkable format, ELF) APIs, and the like.

Wherein, the service is one of android components, and is an application component running in the background without a user interface. The service may be launched by other components of the application (e.g., activity, etc.). Alternatively, after a service is started, it may run all the way in the background of the system.

The broadcast receiver (Broadcast Receiver) is also one of the android components, which is a listener for listening to broadcast messages in the system. Among them, broadcast Receiver is classified into a static registered broadcast (i.e., static broadcast) and a dynamic registered broadcast (i.e., dynamic broadcast). For example, the static broadcast may be configured in an android management. The static broadcast may reside in the system, which may still exist after the application process is finished. Dynamic broadcasting does not reside in the system and ends with the end of the application process.

Inter-application cross-pulling may also be referred to as inter-application wake-up, where one application may be restarted (or wake-up) by another application after being killed, for example: if the camera application is killed, the camera application can be restarted by the browser application when the browser application is started.

Registration push refers to message push that an application is actively doing, for example: the application may push messages proactively at a particular time and/or under a particular scenario. In order to realize registration pushing of the application, a process of keeping the application alive in the background of the system is needed so that the application can keep communication with the server, and when data sent by the server is received, the application creates notification and pushes out.

Timed wake-up refers to the timed wake-up of an application process by setting a timer.

DEX may refer to a file format executable in a virtual machine included in Android Runtime in the software architecture of the electronic device shown in FIG. 6, and DEX API refers to a DEX bytecode called through the API.

An ELF may refer to the format of executable code of the kernel layer in the software architecture of the electronic device shown in FIG. 6, and an ELF API refers to calling ELF code through an API.

Optionally, the ELF code may also call an API in the electronic device system, which is not specifically limited by the present application.

Alternatively, the static characteristics of an application may be obtained by analyzing the code of the installation package to which the application corresponds.

By way of example, the server may obtain static characteristics of various applications by way of static analysis. The static analysis refers to a means for obtaining the functions of the application program by various technical means such as word analysis and grammar analysis under the condition that the code of the application program is not operated. For example: an Android Package (APK) file corresponding to an application includes android management files such as xml, classes, dex, res, etc., and a plaintext android management file can be obtained by decompiling the APK file, and various information such as a component, a component authority, a component starting position, application basic information, etc. are defined in the file, and static characteristics of the application can be obtained by analyzing the plaintext android management file.

Exemplary dynamic sandboxed features of an application include, but are not limited to, services (services), static broadcasts, inter-application cross-pulls, registration pushes, timed wakes, DEX APIs, ELF APIs, and the like. Specific description of each dynamic sandbox feature is referred to above and will not be repeated here.

Among other things, sandboxes (saddboxes) are a security mechanism that provides an isolated environment for executing applications, i.e. different applications are isolated to run in different environments. Alternatively, the dynamic sandboxed feature of an application may be obtained by building code for the sandbox running the corresponding installation package for the application. By modifying source codes of an operating system, a sandbox is constructed, virtualized disks, memories, network resources and the like are utilized to respectively run application programs, and then the running behavior of the application is detected, so that the dynamic sandbox characteristics of the application can be obtained. In view of the prior art in construction of sandboxes, reference is made to the relevant description of the prior art for its specific implementation.

It should be noted that the static features and the dynamic sandboxed features described above are described by taking the android operating system as an example, which is only an exemplary description for facilitating understanding of the present application, and not limiting the present application, and other features may also be included in practical applications. And, for different operating systems, for example: iOS, android, harmony, windows, etc., which may or may not include static features and dynamic sandboxed features that may be the same.

Since the application may do some confusion, encryption, etc. in the configuration file, the behavior that the application may have may not be fully detected by merely detecting the static features of the application. Thus, the behavior of the application in real running can also be obtained by obtaining the dynamic sandboxed feature of the application. In addition, certain actions of an application may need to be triggered under certain conditions, such as: the electronic device is triggered under the condition that the electric quantity of the electronic device is 80%, so that possible behaviors of the application can not be comprehensively detected only by detecting the dynamic sandbox characteristics of the application, and therefore, behaviors of the application which are not detected when the application is run by using the dynamic sandbox can be obtained by obtaining the static characteristics of the application. In summary, by detecting the static features and the dynamic sandbox features of the application, that is, by combining the static detection and the dynamic sandbox detection, some behaviors possibly existing in the application can be more comprehensively obtained, and the accuracy of the generated application details is improved.

S702, the server generates details of the application according to the target characteristics of the application.

Alternatively, the server may generate details of one or more applications.

Illustratively, the server analyzes the detected target features of the application by the schedule analysis module 601 shown in fig. 6, generating details of the application.

By way of example, table 1 shows an example of details of a server-generated application.

TABLE 1

Wherein, as shown in Table 1, an "application ID" may be used to identify different applications. The "application name" is the name of one application. The "package name" is the name of the installation package to which the application corresponds. The "hash value" may be used to identify different versions of an application, and may be obtained by calculating through various hash algorithms, which is not limited in the present application, and in view of the fact that the method for calculating the "hash value" is the prior art, the specific implementation thereof may refer to the prior art, and will not be described in detail herein. The "technical means ID" is used to identify the keep-alive policy employed by an application. The "technical means name" is the name of the keep-alive strategy adopted by an application. The "number of processes" is the number of processes that a keep-alive policy employed by an application may start in the background of the system (or the number of processes that an application starts when the electronic device is resident in the background). The "lowest version supported" is the lowest version of the operating system supported by the technical means. The "highest version supported" is the highest version of the operating system supported by the technical means.

An "impact" is a "technical means" employed by an application or an impact that an application supports background resident behavior may be brought to an electronic device. For example, an "impact" may cause a device to get stuck, such as by "too many applications running in the background," and some applications may push advertisements in the background, affecting the user experience "such information.

"description" is a relative introduction (or explanation) to "technical means" or "background residency", and by way of example, "description" may refer to information such as "background residency" that an application will always run in the background when it is not closed by other means after it is started.

"whether or not background resident behavior is supported" refers to whether or not a background resident behavior is supported by an application (or whether or not an application will run in the background all the time, or whether or not an application is a keep-alive application, or whether or not an application will take a keep-alive policy, or whether or not an application is stored in a keep-alive behavior, etc.). It will be appreciated that if an application employs a number of "technologies," it is illustrated that the application supports background resident behavior, and if an application does not employ any "technologies," it is illustrated that the application does not support background resident behavior.

In some embodiments, the details of the server-generated application may include only applications that support background resident behavior or only details of applications that do not support background resident behavior.

In other embodiments, the details of the server-generated application may include not only details of the application that supports the background resident behavior, but also details of the application that does not support the background resident behavior.

The details of the application shown in table 1 are not limiting to the present application, and in practical applications, the details of the application may include more or less contents than those shown in table 1.

Alternatively, one application may employ one or more keep-alive strategies. That is, one "application ID" (or "application name") may correspond to a plurality of different "technology IDs" (or "technology names"), and the "supported lowest version" and/or the "supported highest version" corresponding to the different "technology IDs" may be the same or different.

By way of example, keep-alive strategies that may be employed by an application include, but are not limited to, setting a service as a foreground service; monitoring static broadcasting; by setting a timer, the process of the application is awakened at fixed time; inter-application mutual pulling; the dual process keep-alive policy starts two processes when an application is opened, and when one process is killed, the other running process wakes up the killed process again, etc. An application may also combine the aforementioned policies to achieve process keep-alive. Further keep-alive strategies can also refer to the prior art.

The details of the server-generated browser may be as shown in table 2, for example.

TABLE 2

As shown in table 2, the keep-alive policy adopted by the browser is "file lock", when the keep-alive policy is adopted, the number of processes started by the background is 6, the lowest version of the supported operating system is android 2, the highest version of the supported operating system is android 12, and the background resident behavior is supported. It will be understood that "file lock" refers to a manner of acquiring a file lock of one process by another process in a multi-process manner to determine whether the other process is closed. If one process successfully acquires the file lock of the other process, the other process is closed, the other process is immediately pulled up (or called wakening, starting and the like) to keep alive the process, if the file lock of the other process is not successfully acquired, the other process is not closed, and the other process does not need to be pulled up. Optionally, the file lock may be allocated by the electronic device for a started process, after one process creates a sub-file, the sub-file is locked according to the allocated file lock, and after the locking is completed, the other process may be instructed to monitor the state of the file lock of itself.

It should be noted that the details of the browser shown in table 2 are only exemplary illustrations for facilitating understanding of the present application, and do not limit the present application.

Optionally, the technical means corresponding to an application may be determined according to one or more of the target features of the application, i.e. the keep-alive policy adopted by an application may be determined according to one or more of the target features, i.e. the details of an application may be determined according to the target features of the application.

Optionally, after generating the details of the application, the server may also store the generated details of the application. Subsequently, the details of the application may be sent to the mobile phone for display by the mobile phone.

Optionally, the details of these applications may also be used for some other operations, such as: for determining the level of these applications, etc., the application details of the present application are not limited to this.

It should be noted that, the foregoing examples are described in terms of details of the server generating the application, and in some other embodiments, the process of generating the details of the application may be performed by the electronic device, which is not limited by the present application.

Fig. 8 is a schematic flow chart of a display method according to an embodiment of the present application, and as shown in fig. 8, the method includes the following steps:

S801, the mobile phone receives a target operation (namely a first operation) of a user.

Wherein the target operation may be used to indicate details of the handset display application. Alternatively, the application may be an application already installed on the mobile phone, or may be an application not installed on the mobile phone.

Taking the scenario in which the user launches the application marketplace to display details of the application as an example.

In some embodiments, the target operation may be an operation by a user to launch an application marketplace. As shown in fig. 9 (1), the mobile phone displays a main interface 900, and various applications are included in the main interface 900, and different applications may be used to implement different functions. Among these multiple applications is application marketplace 901. For example: the target operation may be, for example, a click operation of the application market 901 by a user.

In other embodiments, the target operation may also be an operation in which the user views an application in the application marketplace.

In some examples, as shown in (1) of fig. 10, the handset displays a main interface 1000, where the main interface 1000 includes an application marketplace 1001. The mobile phone detects a click operation such as a user's icon on the application market 1001, and in response to the operation, as shown in (2) in fig. 10, the mobile phone may display a main interface 1010 of the application market, wherein various types of applications are included in the main interface 1010, such as: games, video, music, etc. The user can set up to download and install a certain application according to the actual demand. Optionally, a search field 1012 may be included in the main interface 1010, where the search field 1012 may be used to quickly find different applications, and a navigation field 1013 may be used to quickly enter different sub-interfaces of the application marketplace. In this example, the target operation may be an operation by which the user views a certain application in the main interface 1010, for example: the target operation may be, for example, a click operation of the display area 1011 of a certain application by the user in the main interface 1010.

In other examples, as shown in (1) of FIG. 11, the user may also view the application in other ways, based on the main interface 1010 of the application marketplace shown in (2) of FIG. 10. Optionally, one or more option buttons are included in the navigation bar 1013 included in the main interface 1010, with different option buttons being available to enter different interfaces. The handset detects a click operation such as the user's "my" option 1014 on the main interface 1010, and in response thereto, the handset may display the interface 1100 as shown in (2) of fig. 11. Among other things, some services are included in interface 1100, such as: update management 1101, installation management 1102, and the like. The update management 1101 may be used to view an application that needs to be updated in an application installed in a current mobile phone, and a user may update a version of the application installed in the mobile phone through the update management 1101 according to an actual requirement. Installation management 1102 may be used to view applications that are currently installed in the handset. For example: the target operation may be, for example, a click operation by the user on the update management 1101, or the installation management 1102.

Optionally, other services may be included in interface 1100, such as: installation package management, cleanup acceleration, fast application management, setup, etc., and in view of these services being prior art, the detailed description thereof will be referred to the prior art and will not be described further herein.

Taking the scenario in which the user starts the setup application to display details of the application as an example.

For example, the target operation may be an operation of viewing an application through a setup application. As shown in fig. 12 (1), the mobile phone displays a main interface 1200, and one or more applications including a setting application 1201 are included in the main interface 1200. The mobile phone detects a click operation such as a user's icon of the setting application 1201, and in response to the operation, as shown in (2) in fig. 12, the mobile phone displays a setting interface 1210 in which a notification option 1211, an application, and a service option 1212 are included in the setting interface 1210. The notification option 1211 may be used to view applications installed in the handset that have an automatic push message function, and the application and service option 1212 may be used to manage applications installed in the handset, such as: uninstallation, rights management, startup management, and the like. For example: the target operation is such as a click operation of the notification option 1211 by the user, or the application and service option 1212.

Optionally, other setting options may also be included in the setting interface 1210, such as: WLAN, bluetooth, mobile network, desktop and wallpaper, sound and vibration, etc.

Taking the scenario of a user searching for an application as an example.

By way of example, the target operation may be an operation by the user for searching for an application. Taking a user search application through a browser as an example, as shown in (1) in fig. 15, a main interface 1500 is displayed by a mobile phone, the browser 1501 is included in the main interface 1500, and the mobile phone detects an operation by the user for starting the browser 1501, for example: the mobile phone detects a click operation such as a user on an icon of the browser 1501, and in response to the operation, as shown in (2) in fig. 15, the mobile phone displays a search interface 1510, and a search box 1511, a search button 1512, and the like are included in the mobile phone search interface 1510. Search box 1511 may be used for user input of content desired to be searched and search button 1512 may be used to initiate a search function. For example: the target operation may be an operation in which the user inputs the name of the application (e.g., game 1) in search box 1511 and clicks search button 1512.

Optionally, some other options may also be included in the search interface 1510, such as: recommendation, video, selection, entertainment, etc., and in view of these options being prior art, reference is made to the prior art for a specific description thereof.

In other possible scenarios, the target operation may also be an operation of an icon of the application by the user, such as a key operation, a voice operation, a gesture operation, or the like of an icon of the application on a mobile phone desktop (such as the main interface 900 shown in (1) of fig. 9).

It should be noted that the above-mentioned target operations are only exemplary, and in practical applications, the target operations may include more cases.

S802, responding to the target operation, and acquiring the application details by the mobile phone.

In one possible implementation, if the process of generating the details of the application is performed by the handset, the handset may obtain the details of the application generated by itself from its own memory or other device. It will be appreciated that after the mobile phone generates the details of the application, the details of the application may be stored in its own memory, or may be sent to other devices for storage.

In another possible implementation, if the process of generating the details of the application is performed by the server, the handset may obtain the details of the application from the server.

In some embodiments, the server may send details of all applications generated to the handset. Accordingly, the handset receives details of all applications from the server. Therefore, the server can directly send all application details to the mobile phone without screening and other operations, so that the calculation amount of the server can be reduced, and the working efficiency of the server is improved.

In other embodiments, the server may send details of the generated partial application to the handset. Accordingly, the handset receives details of the partial application from the server.

In a possible example, in a case where the details of the application supporting the background resident behavior and the details of the application not supporting the background resident behavior are included in the server-generated application details at the same time, the server may send only the details of the application supporting the background resident behavior to the mobile phone, or send only the details of the application not supporting the background resident behavior to the mobile phone. Optionally, the mobile phone may further determine details of applications other than the partial application according to the received details of the partial application. In another possible example, before the handset receives details of various applications sent by the server, the handset may first send to the server a version of the handset's current operating system and/or applications currently viewed by the user (or applications to be displayed by the handset). And then the server can screen out details of the corresponding application according to the current operating system version of the mobile phone and/or the application currently viewed by the user.

Such as: assuming that the current operating system version of the mobile phone is android 11, the server determines that the supported version is higher than or equal to the application of android 11 according to the "supported highest version" in the example shown in table 1.

For another example: assuming that the application currently viewed by the user is a browser, the server determines details of the browser from the "application ID" (and/or "application name") in the example shown in table 1.

For another example, assuming that the version of the current operating system of the mobile phone is android 11 and the application currently viewed by the user is a browser, the server determines whether the version supported by the browser includes android 11 according to the "supported highest version" and the "application ID" (and/or "application name") in the examples shown in table 1, if so, the server may send details corresponding to the browser to the mobile phone, if not, the server may determine that the browser does not support the background behavior, and the server may send information such as "description", influence, etc. in the examples shown in table 1 to the mobile phone.

Therefore, the details of the application received by the mobile phone are adapted to the current mobile phone, the server only returns part of the application details, the application details can be prevented from being stolen by others, the information safety is improved, the information transmission quantity between the server and the electronic equipment can be reduced, and the communication efficiency between the server and the electronic equipment is improved.

Optionally, after the handset receives the details of the application from the server, the handset may also store the details of the application for subsequent use.

S803, the mobile phone displays the application details.

Alternatively, the mobile phone may display only details of the application supporting the background resident behavior or details of the application not supporting the background resident behavior, or may display details of the application supporting the background resident behavior and details of the application not supporting the background resident behavior at the same time, which is not limited in the present application.

For example: the mobile phone can determine how to display the details of the application according to the received details of the application, for example: in the case where the mobile phone receives only details of the application supporting the background resident behavior, the mobile phone may display only details of the application supporting the background resident behavior, and may not display details of other applications than the application. Or, the mobile phone may determine details of other applications except the part of applications according to the received details of the applications supporting the background resident behavior, and then only display details of other applications except the part of applications, or simultaneously display details of the applications supporting the background resident behavior and details of the applications not supporting the background resident behavior. Also, in the case where the mobile phone receives only details of an application that does not support the background resident behavior, the display manner is similar to the foregoing manner.

Optionally, in the case that the mobile phone displays only details of a part of the applications, the mobile phone may also display a prompt message to prompt the user about other applications except for the part of the applications. Such as: the mobile phone only displays details of the application supporting the background resident behavior, the prompt information may be, for example, "if the application does not display related information about whether the application supports the background resident behavior, it is explained that the application does not support the background resident behavior". And, for example: the mobile phone only displays details of the application that does not support the background resident behavior, the prompt information may be, for example, "if the application does not display the related information about whether the background resident is supported, it is explained that the application supports the background resident behavior".

Alternatively, the handset may display a portion of the details of the application first and then display the other portion of the details of the application. Of course, the mobile phone may also directly display all details of the application, and the application is not limited thereto.

Taking a scenario in which the mobile phone displays details of an application through the application market as an example.

As shown in fig. 9 (1), the handset detects a click operation such as a user's icon on the application marketplace 901, and in response to this operation, in some examples, as shown in fig. 9 (2), the handset displays a main interface 910 of the application marketplace. Among other things, a plurality of applications are included in the application marketplace's main interface 910, which may alternatively be applications that are not installed on the handset. The icon, name, and details 912 of the application are included in the display area 911 of each application. In this example, considering that there is a limit to the size of the display area 911 of each application, only a part of the details of the application (i.e., the first details) such as those shown in table 1 above may be included in the details 912 of the application, for example, only the relevant information of "whether background resident is supported". Optionally, the mobile phone detects an operation by the user for indicating that the mobile phone displays other details of the application, for example, the mobile phone detects a tap (or click) of the application details 912 by the user, as shown in (3) in fig. 9, and the mobile phone may display other details of the application (i.e., the second details), for example: the "description", "influence", "number of processes", and the like shown in table 1 above are not particularly limited thereto by the present application. Alternatively, the mobile phone may hover display other details of the application, such as hover window 920, or may skip to a new interface, and the application is not limited in this regard.

In other examples, as shown in (1) of fig. 10, the handset detects a click operation such as the user on the application marketplace 1001, and in response to this operation, as shown in (2) of fig. 10, the handset displays a main interface 1010 of the application marketplace, including in the main interface 1010 a plurality of applications, which may alternatively be applications that are not installed on the handset. The display area 1011 of each application includes an icon, a name, and the like of the application. Also, considering that there is a limit to the size of the display area 1011 for each application, the handset may not display the details of the application in the main interface 1010. The mobile phone detects an operation by the user for instructing the mobile phone to display details of the application, for example, the mobile phone detects a click operation by the user on the display area 1011 of the application (such as music), and in response to the operation, as shown in (3) of fig. 10, the mobile phone displays an interface 1020, in which a details display area 1021 of the application is included in the interface 1020, which can be used to display details of the application such as shown in table 1, for example: "whether background residency is supported", "description", "influence", "number of processes", etc., and the present application is not limited in this regard.

Or, the mobile phone detects the detail operation of the user for indicating the mobile phone display application, for example: the mobile phone detects a click operation of the display area 1011 of the application by the user, and in response to the operation, the mobile phone displays the detail interface 1030 of the application as shown in (4) of fig. 10. Details 1031 of the application are included in the details interface 1030 of the application. Alternatively, only a part of the details of the application such as those shown in table 1 above may be included in the details 1031 of the application, for example, only the relevant information of "whether background resident is supported". When the mobile phone detects an operation of the user for instructing the mobile phone to display other details of the application, for example, when the mobile phone detects an operation such as a tap (or click) of the details 1031 of the application by the user, the mobile phone redisplays other details of the application, for example, like other details 920 of the application shown in (3) of fig. 9: the "description", "influence", "number of processes", and the like shown in table 1 above are not particularly limited thereto by the present application.

In still other examples, as shown in (2) of fig. 11, the handset detects a click operation, such as a user's click on the update management 1101, and in response to this operation, as shown in (3) of fig. 11, the handset may display an interface 1110 including one or more applications to be updated in the interface 1110, such as: music 1, music 2, games 4, etc. The details of each application may be displayed in a manner such as that described in (3) of fig. 10, or in a manner such as that shown in (4) of fig. 10. Optionally, a drop-down button 1111 may also be included in interface 1110 that may be used to hide or display details of the application, and/or other information of the application (e.g., size of the installation package, version of the installation package, etc.).

Alternatively, the handset detects a click operation such as a user on the installation management 1102, and in response to this operation, the handset may display an interface 1120, as shown in (4) of fig. 11, including one or more applications installed by the handset in the interface 1120. Likewise, the details of each application may be displayed in a manner such as that shown in (3) of fig. 10, or in a manner such as that shown in (4) of fig. 10. Optionally, a drop down button 1121 may also be included in interface 1120 that may be used to hide or display details of the application, and/or other information (e.g., an unload button, a manage button, etc.).

Taking a scenario in which the mobile phone displays details of an application by setting as an example.

As shown in (2) in fig. 12, the handset detects a click operation such as a user on the notification option 1211, and in response to the operation, the handset displays a notification interface 1220 including one or more applications already installed in the handset in the notification interface 1220, as shown in (3) in fig. 12. Optionally, other options may be included in the notification interface 1220, such as desktop icon corner marks, lock screen notifications, batch management, etc., and, given that these options are prior art, reference is made to the prior art for specific description and implementation. Wherein the icon, name, and details 1222 of each application are included in the display area 1221 of each application. Also, considering that there is a limit to the size of the display area 1221 of each application, only a part of the details of the application such as those shown in table 1 above may be included in the details 1222 of the application, for example, only the relevant information of "whether background resident is supported". Optionally, the mobile phone detects an operation by the user for instructing the mobile phone to display other details of the application, for example, the mobile phone detects a tap (or click) or the like by the user on the details 1222 of the application, similar to the other details 920 of the application shown in (3) in fig. 9, the mobile phone may display other detailed information of the application, for example: the "description", "influence", "number of processes", and the like shown in table 1 above are not particularly limited thereto by the present application.

Alternatively, in response to a click operation such as the user on the notification option 1211 in the interface 1210, as shown in (3) in fig. 13, details of the application are not displayed in the notification interface 1300 first. The mobile phone detects an operation of the user for indicating details of the mobile phone display application, such as: the mobile phone detects a click operation such as a user clicking on the display region 1301 of the application, and in response to the operation, as shown in (4) in fig. 13, the mobile phone displays an interface 1310, in which a detail display region 1311 of the application is included in the interface 1310, which may be used to display details in the application such as shown in table 1, such as: "whether background residency is supported", "description", "influence", "number of processes", etc., and the present application is not limited in this regard. Alternatively, in interface 1310, the handset may also display details of the application in a manner such as that shown in fig. 10 (4). The descriptions of (1) and (2) in fig. 13 may refer to the descriptions of (1) and (2) in fig. 12, respectively.

Of course, the handset may also display various applications in other ways, such as: the "batch management" shown in (3) in fig. 12 or (3) in fig. 13 further shows various applications such as those shown in (3) in fig. 12 or (3) in fig. 13, and details of the applications are displayed in a batch management interface in a manner such as those shown in fig. 12, 13, etc., to which the present application is not limited.

As shown in (2) of fig. 14, the handset detects a click operation such as the user's application and service option 1212, and in response to the operation, the handset displays an application management interface 1400 as shown in (3) of fig. 14, in which one or more applications for which the handset has been installed are included in the application management interface 1400. Optionally, other options may be included in the application management interface 1400, such as: application management, application launch management, service management, etc., which are not described in detail herein given that these options are prior art. The details of each application may be displayed in a manner such as that shown in fig. 12 or in a manner such as that shown in fig. 13, to which the present application is not limited. The description of fig. 14 (1) refers to the description of fig. 12 (1).

Taking the details of the browser display application used by the mobile phone as an example.

As shown in (2) in fig. 15, the mobile phone detects an operation in which the user inputs the name of the application (e.g., game 1) in the search box 1511 and clicks the search button 1512, and in response to the operation, as shown in (3) in fig. 15, the mobile phone displays a search interface 1520 in which the searched game 1 is included in the search interface 1520 and a detail display area 1521 of the game 1 is included in the search interface 1520, which can be used to display details of the application such as shown in table 1, such as: "whether background residency is supported", "description", "influence", "number of processes", etc., and the present application is not limited in this regard. Alternatively, in the interface 1520, the handset may display details of the application in a manner such as that shown in (3) of fig. 12, or may display details of the application in a manner such as that shown in (4) of fig. 13.

Alternatively, as shown in fig. 16 (3), the handset does not display the details of the application in the search interface 1600. Upon detecting a click operation such as a user's click on the display area 1601 of the application, the handset displays an interface 1610 in response to the operation, as shown in (4) of fig. 16, wherein a detail display area 1611 of the application is included in the interface 1610, which may be used to display details of the application such as those shown in table 1, such as: "whether background residency is supported", "description", "influence", "number of processes", etc., and the present application is not limited in this regard. Alternatively, in the interface 1610, the handset may display details of the application in a manner such as that shown in (3) of fig. 12, or may display details of the application in a manner such as that shown in (4) of fig. 13. The descriptions of fig. 16 (1) and (2) may refer to the descriptions of fig. 15 (1) and (2), respectively.

In other possible scenarios, the mobile phone detects a target operation such as a key operation, a voice operation, a gesture operation, etc. of an icon of an application (for example, an icon of the application in the interface 900 shown in fig. 9 (1), an interface 1000 shown in fig. 10 (1), an interface 1200 shown in fig. 12 (1), an interface 1500 shown in fig. 15 (1), etc.), and in response to the target operation, the mobile phone may display details of the application directly on the current interface in a manner such as that shown in fig. 12 (3), or may display details of the application in a manner such as that shown in fig. 13 (4). The handset may also jump to a new interface on which the details of the application are displayed in a manner such as that shown in fig. 12 (3), or in a manner such as that shown in fig. 13 (4). The handset may also jump to other relevant interfaces of applications with the functionality to display details of the application (e.g., application marketplace as shown in fig. 10, setup application as shown in fig. 12, browser as shown in fig. 15, etc.) to display details of the application.

Optionally, after the details of the application are displayed by the mobile phone, the mobile phone may also install or uninstall the corresponding application according to the operation of the user.

It should be noted that, the scenario of displaying the details of the application by the mobile phone cannot be exhausted, and the details of the application can be displayed by the mobile phone on the interface of displaying the application by adopting the method provided by the embodiment of the application, which is not limited by the application.

It should be noted that, the above interfaces are only schematic, and in practical applications, more or less content may be included in each interface, and more or less interfaces may be included, which is not particularly limited by the present application.

Fig. 17 is a schematic flow chart of another display method according to an embodiment of the present application, where the method includes the following steps:

s1701, the electronic equipment receives a first operation of a user.

Wherein a specific description of the first operation may be referred to the above-described related description of the target operation.

S1702, in response to the first operation, the electronic device sends a request message to a server. Accordingly, the server receives the request message from the electronic device.

Wherein the request message may be used to instruct the server to send details of the application to the electronic device. Details of the application include whether the application will reside in the background of the electronic device.

Optionally, the details of the application may further include one or more of: the explanation of the background resident, the influence of the background resident on the electronic equipment, and the number of processes started when the application is in the background resident of the electronic equipment. Of course, details of the application may also include other contents among details of the application such as those shown in table 1, to which the present application is not limited. It is understood that the details of the application may include details of one or more applications.

In some embodiments, the request message includes version of an operating system of the electronic device and/or identification information of an application, where the identification information of the application may be used to indicate an application to be displayed by the electronic device.

In other embodiments, the request message may not include the version of the operating system and the identification information of the application of the electronic device.

S1703, the server determines the application details according to the request message.

In some embodiments, in the event that the request message includes version of the operating system of the electronic device and/or identification information of the application, the server may determine details of the application corresponding to the current electronic device.

In other embodiments, the server may determine that details of all applications generated need to be sent without including version of the operating system of the electronic device and identification information of the applications in the request message.

S1704, the server sends the details of the application to the electronic device. Accordingly, the electronic device receives details of the application from the server.

In some embodiments, the server may send details of the application corresponding to the current electronic device to the electronic device.

In other embodiments, the server may send details of all applications generated to the electronic device.

Alternatively, for details of an application, the server may send all details of the application to the electronic device at one time, or may be sent to the electronic device multiple times, which is not limited by the present application.

S1705, the electronic device displays details of the application.

Wherein the details of the application may be used to instruct the user to avoid the application residing in the background of the electronic device by uninstalling the application or not installing the application.

Alternatively, the electronic device may display a portion of the details of the application first and then display other portions of the details of the application. Such as: the electronic device may display an overview of the details of the application first, which may be generated by the server according to the details of the application, such as shown in table 1, or may be generated by the electronic device after receiving the details of the application transmitted by the server according to the received details of the application. For example: an overview of this detail may be whether the application will reside in the background of the electronic device, etc. The electronic device then receives a user operation such as: clicking, tapping, etc. on an overview of the displayed application details, the electronic device redisplays a detailed description of the application details, for example: the details of the application may be, of course, other content such as that shown in table 1, and the application is not limited thereto.

Alternatively, the electronic device may display all details of the application at the same time, and the detailed manner of displaying the application by the electronic device is not particularly limited in the present application.

S1706, the electronic equipment receives a second operation of the user.

Wherein the second operation may be an uninstall operation of the user on the number of applications.

S1707, in response to the second operation, the electronic device uninstalls the application.

Based on the technical scheme, the server generates details of the application, and the details of the application include, but are not limited to, whether the application supports the process to reside in the background (or whether the application is a keep-alive application or whether the application has background resident behaviors, and the like), relevant explanation of the background resident, influence of the application process to the electronic equipment caused by the background resident, and the like. The server may then send some or all of the application details to the handset, which may display the application details. Therefore, the user can decide whether to install or uninstall an application by himself or herself by informing the user of the existence of an application and the influence possibly caused to the electronic device, thereby bringing convenience to the user and improving the efficiency of man-machine interaction. If the user still chooses to install an application after knowing the behavior of the application and the influence that may be caused to the electronic device, it is stated that the behavior of the application and the influence that may be caused to the electronic device are acceptable to the user, so that the user experience is not affected. If the user selects to uninstall an application or not install the application after knowing the behavior of the application and the influence possibly caused to the electronic device, the problem that the keep-alive application cannot be thoroughly searched and killed can be solved, so that various problems brought to the electronic device by the keep-alive application process are avoided.

The foregoing description of the solution provided by the embodiments of the present application has been mainly presented in terms of a method. It will be appreciated that the electronic device and the server, in order to implement the above-described functions, comprise corresponding hardware structures and/or software modules that perform the respective functions. The various illustrative units and algorithm steps described in connection with the embodiments disclosed herein may be implemented as hardware or a combination of hardware and computer software. Whether a function is implemented as hardware or computer-driven hardware depends upon the particular application and design constraints imposed on the solution. Those skilled in the art may implement the described functionality using different approaches for each particular application, but such implementation is not to be considered as beyond the scope of the embodiments of the present application.

The embodiment of the application can divide the functional modules of the electronic device and the server according to the method example, for example, each functional module can be divided corresponding to each function, and two or more functions can be integrated in one processing unit. The integrated units may be implemented in hardware or in software functional modules. It should be noted that, in the embodiment of the present application, the division of the units is schematic, which is merely a logic function division, and other division manners may be implemented in actual practice.

As shown in fig. 18, a schematic structural diagram of an electronic device 1800 according to an embodiment of the present application is provided, and the electronic device 1800 may be used to implement the methods described in the above method embodiments. By way of example, the electronic device 1800 may include: a processing unit 1801, a communication unit 1802, and a display unit 1803.

Wherein the processing unit 1801 is configured to execute step S802 in fig. 8 by the support electronic device 1800. And/or the processing unit 1801 is used to execute step S1707 in fig. 17, which is executed by the support electronic device 1800. And/or the processing unit 1801 is further configured to support the electronic device 1800 to perform other steps performed by the electronic device in embodiments of the application.

The communication unit 1802 is configured to execute step S801 in fig. 8 in support of the electronic apparatus 1800. And/or the communication unit 1802 is configured to execute the step S1701, the step S1702, the step S1704, the step S1706, and the like in fig. 17, which are executed by the support electronic device 1800. And/or the communication unit 1802 is also configured to support the electronic device 1800 to perform other steps performed by the electronic device in embodiments of the application.

A display unit 1803 for executing step S803 in fig. 8, which is executed by the support electronic device 1800. And/or the display unit 1803 is used to execute step S1705 in fig. 17, which is executed by the support electronic device 1800. And/or the display unit 1803 is further configured to support the electronic device 1800 to perform other steps performed by the electronic device in embodiments of the application.

Optionally, the electronic device 1800 shown in fig. 18 may further include a storage unit (not shown in fig. 18) that stores programs or instructions. The processing unit 1801, when executing the program or instructions, enables the electronic device 1800 shown in fig. 18 to perform the methods shown in fig. 8 and/or 17.

The technical effects of the electronic device 1800 shown in fig. 18 may refer to the technical effects of the methods shown in fig. 8 and 17, and will not be described herein. The processing unit 1801, which is referred to in the electronic device 1800 illustrated in fig. 18, may be implemented by a processor or a processor-related circuit component, and may be a processor or a processing module. The communication unit may be implemented by a transceiver or transceiver-related circuit component, and may be a transceiver or transceiver module. The display unit 1803 may be implemented by a display screen related component.

As shown in fig. 19, a schematic structural diagram of a server 1900 according to an embodiment of the present application is provided, where the server 1900 may be used to implement the methods described in the above method embodiments. By way of example, the server 1900 may specifically include: processing unit 1901, communication unit 1902.

The processing unit 1901 is configured to execute step S701 and step S702 in fig. 7 by the support server 1900. And/or the processing unit 1901 is configured to execute the support server 1900 to execute step S1703 in fig. 17. And/or the processing unit 1901 is further configured to support the server 1900 to perform other steps performed by the server in the embodiment of the present application.

The communication unit 1902 is configured to execute the support server 1900 to execute step S1702, step S1704, and the like in fig. 17. And/or the communication unit 1902 is further configured to support the server 1900 to perform other steps performed by the server in the embodiment of the present application.

Optionally, the server 1900 shown in fig. 19 may further include a storage unit (not shown in fig. 19) in which a program or instructions are stored. When executed by the processing unit 1901, causes the server 1900 shown in fig. 19 to perform the methods shown in fig. 7 and/or 17.

The technical effects of the server 1900 shown in fig. 19 may refer to the technical effects of the methods shown in fig. 8 and 17, and will not be described herein. The processing unit 1901 referred to in the server 1900 shown in fig. 19 may be implemented by a processor or a processor-related circuit component, and may be a processor or a processing module. The communication unit may be implemented by a transceiver or transceiver-related circuit component, and may be a transceiver or transceiver module.

Embodiments of the present application also provide a chip system, as shown in FIG. 20, comprising at least one processor 2001 and at least one interface circuit 2002. The processor 2001 and interface circuit 2002 may be interconnected by wires. For example, the interface circuit 2002 may be used to receive signals from other devices. For another example, the interface circuit 2002 may be used to send signals to other devices (e.g., the processor 2001). Illustratively, the interface circuit 2002 may read instructions stored in the memory and send the instructions to the processor 2001. The instructions, when executed by the processor 2001, may cause the electronic device to perform the steps performed by the electronic device in the above embodiments, or cause the server to perform the steps performed by the server in the above embodiments. Of course, the system-on-chip may also include other discrete devices, which are not particularly limited in accordance with embodiments of the present application.

Alternatively, the processor in the system-on-chip may be one or more. The processor may be implemented in hardware or in software. When implemented in hardware, the processor may be a logic circuit, an integrated circuit, or the like. When implemented in software, the processor may be a general purpose processor, implemented by reading software code stored in a memory.

Alternatively, the memory in the system-on-chip may be one or more. The memory may be integral with the processor or separate from the processor, and the application is not limited. The memory may be a non-transitory processor, such as a ROM, which may be integrated on the same chip as the processor, or may be separately provided on different chips, and the type of memory and the manner of providing the memory and the processor are not particularly limited in the present application.

The system-on-chip may be, for example, a field programmable gate array (field programmable gate array, FPGA), an application specific integrated chip (application specific integrated circuit, ASIC), a system on chip (SoC), a central processing unit (central processor unit, CPU), a network processor (network processor, NP), a digital signal processing circuit (digital signal processor, DSP), a microcontroller (micro controller unit, MCU), a programmable controller (programmable logic device, PLD) or other integrated chip.

It should be understood that the steps in the above-described method embodiments may be accomplished by integrated logic circuitry in hardware in a processor or instructions in the form of software. The steps of the method disclosed in connection with the embodiments of the present application may be embodied directly in a hardware processor for execution, or in a combination of hardware and software modules in the processor for execution.

The embodiment of the application also provides a computer storage medium, in which computer instructions are stored, which when run on a computer, cause the computer to perform the method described in the above method embodiment.

An embodiment of the present application provides a computer program product comprising: computer program or instructions which, when run on a computer, cause the computer to perform the method described in the method embodiments described above.

In addition, the embodiment of the application also provides a device, which can be a chip, a component or a module, and can comprise a processor and a memory which are connected; the memory is configured to store computer-executable instructions, and when the apparatus is running, the processor may execute the computer-executable instructions stored in the memory, so that the apparatus performs the methods in the method embodiments described above.

The embodiment of the application also provides a communication system which comprises the electronic equipment and the server described in the embodiment.

The electronic device, the server, the computer storage medium, the computer program product or the chip, and the communication system provided in this embodiment are all configured to execute the corresponding methods provided above, so that the beneficial effects achieved by the electronic device, the server, the computer storage medium, the computer program product or the chip, and the communication system can refer to the beneficial effects in the corresponding methods provided above, and are not repeated herein.

It will be appreciated by those skilled in the art that, for convenience and brevity of description, only the above-described division of the functional modules is illustrated, and in practical application, the above-described functional allocation may be performed by different functional modules according to needs, i.e. the internal structure of the apparatus is divided into different functional modules to perform all or part of the functions described above.

In the several embodiments provided by the present application, it should be understood that the disclosed apparatus and method may be implemented in other manners. The embodiments may be combined or referenced to each other without conflict. The above-described apparatus embodiments are merely illustrative, e.g., the division of modules or units is merely a logical functional division, and there may be additional divisions in actual implementation, e.g., multiple units or components may be combined or integrated into another apparatus, or some features may be omitted, or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and the parts shown as units may be one physical unit or a plurality of physical units, may be located in one place, or may be distributed in a plurality of different places. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in the embodiments of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit. The integrated units may be implemented in hardware or in software functional units.

The integrated units, if implemented in the form of software functional units and sold or used as stand-alone products, may be stored in a readable storage medium. Based on such understanding, the technical solution of the embodiments of the present application may be essentially or a part contributing to the prior art or all or part of the technical solution may be embodied in the form of a software product stored in a storage medium, including several instructions for causing a device (may be a single-chip microcomputer, a chip or the like) or a processor (processor) to perform all or part of the steps of the methods of the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read Only Memory (ROM), a random access memory (random access memory, RAM), a magnetic disk, or an optical disk, or other various media capable of storing program codes.

The foregoing is merely illustrative of the present application, and the present application is not limited thereto, and any person skilled in the art will readily recognize that variations or substitutions are within the scope of the present application. Therefore, the protection scope of the application is subject to the protection scope of the claims.

Claims

1. A display method applied to an electronic device having a display screen, the method comprising:

receiving a first operation of a user;

in response to the first operation, acquiring details of an application, wherein the details of the application comprise whether the application is resident in the background of the electronic equipment;

displaying details of the application, wherein the details of the application are used for indicating the user to avoid that the application resides in the background of the electronic equipment by uninstalling the application or not installing the application;

receiving a second operation of the user;

and in response to the second operation, uninstalling the application.

2. The method of claim 1, wherein the details of the application further comprise one or more of an interpretation of the background residency, an impact the background residency has on the electronic device, a number of processes the application initiates while the background residency of the electronic device.

3. A method according to claim 1 or 2, characterized in that the details of the application are determined from target features of the application, which can be used to keep alive the application;

wherein the target features include one or more of:

services, static broadcasting, inter-application mutual pulling, message pushing, timed wake-up, calling Dalvik virtual machine DEX byte codes through an application programming interface API, calling executable link format ELF codes through the API, and calling APIs in the ELF codes.

4. A method according to claim 3, characterized in that the target features of the application comprise static features of the application and/or dynamic features of the application; the static characteristics of the application are obtained by analyzing codes of the installation packages corresponding to the application, and the dynamic characteristics of the application are obtained by constructing codes of the installation packages corresponding to the sandboxes for running the application.

5. The method of any of claims 1-4, wherein the obtaining details of an application in response to the first operation comprises:

in response to the first operation, details of the application are obtained from a server.

6. The method of claim 5, wherein the obtaining details of the application from a server comprises:

Sending a request message to the server, wherein the request message comprises the version of an operating system of the electronic equipment and/or the identification information of the application;

details of the application are received from the server.

7. A display method, applied to a server, the method comprising:

receiving a request message from an electronic device;

sending the application details to the electronic equipment according to the request message;

wherein the details of the application include whether the application will reside in the background of the electronic device.

8. The method of claim 7, wherein the details of the application further include one or more of an interpretation of the background residency, an impact the background residency has on the electronic device, a number of processes the application initiates while the background residency of the electronic device.

9. Method according to claim 7 or 8, characterized in that the request message comprises version of the operating system of the electronic device and/or identification information of the application;

transmitting details of an application to the electronic device according to the request message, including:

determining details of an application corresponding to the electronic equipment according to the version of an operating system of the electronic equipment and/or the identification information of the application;

And sending the details of the application corresponding to the electronic equipment.

10. Method according to claim 7 or 8, characterized in that sending details of an application to the electronic device according to the request message comprises:

and sending the details of all the applications to the electronic equipment according to the request message.

11. The method according to any of claims 7-10, wherein prior to receiving a request message from the electronic device, the method further comprises:

generating details of an application according to target features of the application, wherein the target features of the application can be used for keeping the application alive;

wherein the target features include one or more of:

services, static broadcasting, inter-application mutual pulling, message pushing, timed wake-up, calling Dalvik virtual machine DEX byte codes through an API, calling ELF codes through the API, and calling the API in the ELF codes.

12. The method according to claim 11, wherein the target features of the application comprise static features of the application and/or dynamic features of the application; the static characteristics of the application are obtained by analyzing codes of the installation packages corresponding to the application, and the dynamic characteristics of the application are obtained by constructing codes of the installation packages corresponding to the sandboxes for running the application.

13. An electronic device comprising a processor, a memory, and a display screen, the memory coupled to the processor, the memory for storing computer program code, the computer program code comprising computer instructions, the processor reading the computer instructions from the memory to cause the electronic device to perform the method of any of claims 1-6.

14. A server comprising a processor and a memory coupled to the processor, the memory for storing computer program code, the computer program code comprising computer instructions, the processor reading the computer instructions from the memory to cause the server to perform the method of any of claims 7-12.

15. A computer readable storage medium comprising a computer program or instructions which, when run on a computer, cause the computer to perform the method of any one of claims 1-6 or cause the computer to perform the method of any one of claims 7-12.

16. A computer program product, the computer program product comprising: computer program or instructions which, when run on a computer, cause the computer to perform the method of any one of claims 1-6 or cause the computer to perform the method of any one of claims 7-12.