WO2023202406A1 - Procédé d'affichage et dispositif électronique - Google Patents

Procédé d'affichage et dispositif électronique Download PDF

Info

Publication number
WO2023202406A1
WO2023202406A1 PCT/CN2023/087335 CN2023087335W WO2023202406A1 WO 2023202406 A1 WO2023202406 A1 WO 2023202406A1 CN 2023087335 W CN2023087335 W CN 2023087335W WO 2023202406 A1 WO2023202406 A1 WO 2023202406A1
Authority
WO
WIPO (PCT)
Prior art keywords
application
details
electronic device
server
computer
Prior art date
Application number
PCT/CN2023/087335
Other languages
English (en)
Chinese (zh)
Inventor
杨德志
孙靓
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2023202406A1 publication Critical patent/WO2023202406A1/fr

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
    • G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
    • G06F3/0484—Interaction techniques based on graphical user interfaces [GUI] for the control of specific functions or operations, e.g. selecting or manipulating an object, an image or a displayed text element, setting a parameter value or selecting a range
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533—Hypervisors; Virtual machine monitors
    • G06F9/45558—Hypervisor-specific management and integration aspects

Definitions

  • the present application relates to the technical field of electronic equipment, and in particular to display methods and electronic equipment.
  • the present application provides a display method and electronic device, which can effectively clean up the application process that is kept alive, and solve various problems caused by the application process keeping alive to the electronic device.
  • the method includes: receiving the user's first operation; in response to the first operation, obtaining the details of the application.
  • the details of the application include whether the application will be displayed on the screen. Residing in the background of the electronic device; displaying the details of the application, and the details of the application are used to instruct the user to avoid the application from persisting in the background of the electronic device by uninstalling the application or not installing the application; receiving the second operation of the user; in response to the second operation, Uninstall the app.
  • the electronic device can obtain and display the details of the application according to the user's operation.
  • the details of the application include whether it will be resident in the background of the electronic device, that is, whether the application is a keep-alive application, so that the user can Decide whether to install or uninstall an application.
  • the user can decide whether to install or uninstall an application, which can bring convenience to the user and improve the efficiency of human-computer interaction. If the user chooses to uninstall or not install the keep-alive application, it can solve the problem that the application cannot be completely checked and killed, thereby avoiding various problems caused by the keep-alive application to the electronic device.
  • the details of the application also include one or more of an explanation of background persistence, the impact of background persistence on the electronic device, and the number of processes started when the application resides in the background of the electronic device. Based on this design, users can have a clearer understanding of the impact that keep-alive applications may have on electronic devices, and can then make more reasonable decisions about whether to install or uninstall an application, bringing convenience to users.
  • the details of the application are determined based on the target characteristics of the application.
  • the target characteristics of the application can be used to keep the application alive.
  • the target characteristics include one or more of the following: service, static broadcast, inter-application mutual pull, Push messages, scheduled wake-up, call Dalvik virtual machine DEX bytecode through API, call ELF code through API, and API called in ELF code.
  • the target characteristics of the application include the static characteristics of the application and/or the dynamic characteristics of the application; the static characteristics of the application are obtained by analyzing the code of the installation package corresponding to the application, and the dynamic characteristics of the application are obtained by constructing a sandbox to run the corresponding application. The code of the installation package is obtained.
  • the target characteristics of the application can include the static characteristics and dynamic sandbox characteristics of the application. Since the application may perform some operations such as obfuscation, encryption, etc. in the configuration file, it may not be possible to fully detect possible behaviors of the application only by detecting the static characteristics of the application. Therefore, the real runtime behavior of the application can also be obtained by obtaining the dynamic sandbox characteristics of the application. In addition, some behaviors of the application may need to be triggered under certain conditions, such as triggering when the power of the electronic device is 80%. Therefore, it may not be possible to fully detect possible behaviors of the application only by detecting the dynamic sandbox characteristics of the application.
  • obtaining application details in response to the first operation includes: obtaining application details from the server in response to the first operation.
  • obtaining application details from the server includes: sending a request message to the server, where the request message includes the version of the operating system of the electronic device and/or identification information of the application; and receiving application details from the server.
  • the application details received by the electronic device can be adapted to the current electronic device.
  • the server only returns part of the application details, which can prevent the application details from being stolen by others, improve the security of the information, and also reduce the number of server and The amount of information transmitted between electronic devices improves the communication efficiency between servers and electronic devices.
  • this application provides a display method, applied to a server.
  • the method includes: receiving a request message from an electronic device; sending application details to the electronic device according to the request message; wherein the application details include whether the application will be displayed on the electronic device. Permanent backstage.
  • the details of the application also include one or more of an explanation of background persistence, the impact of background persistence on the electronic device, and the number of processes started when the application resides in the background of the electronic device.
  • the request message includes the version of the operating system of the electronic device and/or the identification information of the application; sending application details to the electronic device according to the request message includes: according to the version of the operating system of the electronic device and/or The identification information of the application determines the details of the application corresponding to the electronic device; and sends the details of the application corresponding to the electronic device to the electronic device.
  • sending application details to the electronic device according to the request message includes: sending all application details to the electronic device according to the request message.
  • the method before receiving the request message from the electronic device, the method also includes: generating application details according to the target characteristics of the application, which can be used to keep the application alive; wherein the target characteristics include one or more of the following: Categories: services, static broadcasts, inter-application interactions, push messages, scheduled wake-ups, calling Dalvik virtual machine DEX bytecode through API, calling ELF code through API, and APIs called in ELF code.
  • the target characteristics of the application include static characteristics of the application and/or dynamic characteristics of the application; the static characteristics of the application are obtained by analyzing the code of the installation package corresponding to the application, and the dynamic characteristics of the application are obtained by constructing Get the code of the installation package corresponding to the sandbox running application.
  • the present application provides an electronic device, which has the function of implementing the method described in the above first aspect and any one of the designs.
  • This function can be implemented by hardware, or it can be implemented by hardware executing corresponding software.
  • the hardware or software includes one or more modules corresponding to the above functions.
  • the application provides an electronic device, including a processor, a memory, and a display screen.
  • the memory, the display screen, and the processor are coupled.
  • the memory is used to store computer program code.
  • the computer program code includes computer instructions.
  • the processor obtains instructions from the memory.
  • the computer instructions are read to cause the electronic device to execute the method described in the above second aspect and any one of the designs.
  • the memory is provided independently of the processor, or it can be integrated with the processor.
  • the electronic device further includes a communication interface, which can be used for the electronic device to communicate with other devices (such as a server).
  • the communication interface may be a transceiver, an input/output interface, an interface circuit, an output circuit, an input circuit, a pin or a related circuit, etc.
  • this application provides a server that has the function of implementing the method described in the above second aspect and any one of the designs.
  • This function can be implemented by hardware, or it can be implemented by hardware executing corresponding software.
  • the hardware or software includes one or more modules corresponding to the above functions.
  • the application provides a server, including a processor and a memory.
  • the memory is coupled to the processor.
  • the memory is used to store computer program code.
  • the computer program code includes computer instructions.
  • the processor reads the computer instructions from the memory, so that The server executes the method described in the above second aspect and any one of the designs.
  • the memory is provided independently of the processor, or it can be integrated with the processor.
  • the server also includes a communication interface, which can be used for the server to communicate with other devices (such as electronic devices).
  • the communication interface may be a transceiver, an input/output interface, an interface circuit, an output circuit, an input circuit, a pin or a related circuit, etc.
  • the present application provides a computer-readable storage medium.
  • the computer-readable storage medium includes a computer program or instructions.
  • the computer program or instructions When the computer program or instructions are run on a computer, the computer executes the above-mentioned first aspect and any of the above.
  • a method is designed, or a computer is caused to execute the method described in the above second aspect and any one of the designs.
  • the present application provides a computer program product.
  • the computer program product includes: a computer program or an instruction.
  • the computer program or instruction When the computer program or instruction is run on a computer, it causes the computer to execute the above-mentioned first aspect and any of the designs therein. The method described above, or causing the computer to perform the method described in the above second aspect and any one of the designs.
  • the present application provides a chip system, including at least one processor and at least one interface circuit.
  • the at least one interface circuit is used to perform transceiver functions and send instructions to at least one processor.
  • When at least one processor executes the instructions When at least one processor performs the method described in the above-mentioned first aspect and any one of the designs, or performs the method described in the above-mentioned second aspect and any one of the designs.
  • this application provides a communication system, including the electronic device provided in the third or fourth aspect, and the server provided in the fifth or sixth aspect.
  • Figure 1 is a schematic flow chart of an existing method for cleaning application processes
  • Figure 2 is a schematic flow chart of another existing method of cleaning application processes
  • Figure 3 is a schematic diagram of a communication system provided by an embodiment of the present application.
  • Figure 4 is a schematic diagram of the hardware structure of a server provided by an embodiment of the present application.
  • Figure 5 is a schematic diagram of the hardware structure of an electronic device provided by an embodiment of the present application.
  • Figure 6 is a software structure block diagram of an electronic device and server provided by an embodiment of the present application.
  • Figure 7 is a schematic flowchart of a method for generating application details provided by an embodiment of the present application.
  • Figure 8 is a schematic flowchart of a display method provided by an embodiment of the present application.
  • Figure 9 provides a set of interface schematic diagrams for an embodiment of the present application.
  • Figure 10 provides another set of interface schematic diagrams for an embodiment of the present application.
  • Figure 11 provides another set of interface schematic diagrams for an embodiment of the present application.
  • Figure 12 provides another set of interface schematic diagrams for an embodiment of the present application.
  • Figure 13 provides another set of interface schematic diagrams for an embodiment of the present application.
  • Figure 14 provides another set of interface schematic diagrams for an embodiment of the present application.
  • Figure 15 provides another set of interface schematic diagrams for an embodiment of the present application.
  • Figure 16 provides another set of interface schematic diagrams for an embodiment of the present application.
  • Figure 17 is a schematic flowchart of another display method provided by an embodiment of the present application.
  • Figure 18 is a schematic structural diagram of an electronic device provided by an embodiment of the present application.
  • Figure 19 is a schematic structural diagram of a server provided by an embodiment of the present application.
  • Figure 20 is a schematic structural diagram of a chip system provided by an embodiment of the present application.
  • the keep-alive policy is a means for the application process to protect itself from being checked and killed after the user actively checks and kills it.
  • the keep-alive policy is a means for the electronic device system to automatically trigger a cleaning application process so that the application process can be restarted immediately after being killed.
  • the application processes running in the background become more More and more, electronic devices will have various problems such as system lags and excessive advertisements, causing inconvenience to users. Therefore, in order to ensure the stability of the operation of electronic equipment, many solutions for cleaning application processes are provided in the existing technology.
  • Figure 1 shows an existing solution for cleaning application processes.
  • memory scanning is triggered, and the application process (or process for short) is traversed, filtering out the process with the lowest priority, and then determining whether the process will be perceived by the user. If so, add it to the whitelist and give up. Check and kill; if not, check and kill the process. Then it is judged whether the memory of the electronic device meets the expectations. If it meets the expectations, the memory scanning and killing process is ended. If it does not meet the expectations, the memory scanning and killing process continues. In this solution, the electronic device will only kill application processes that have low priority and are invisible to users.
  • FIG. 2 shows yet another existing solution for cleaning up application processes.
  • the application or application
  • the whitelist is allowed to be started. If the whitelist is allowed to be started, it is determined that the application is actively clicked or started legally, and the previously disabled wake-up startup component is restored. If the whitelist is not allowed to be started, the application process is cleaned up.
  • the above solutions may not be able to effectively clean up the application processes that are kept alive, and cannot effectively solve the various problems caused to the electronic devices due to the application processes being kept alive.
  • the present application provides a display method that can effectively clean up the application process that is kept alive, solve various problems caused to electronic devices due to application process keeping alive, improve the efficiency of human-computer interaction, and bring convenience to users.
  • FIG. 3 is a schematic diagram of a communication system in which a display method provided by an embodiment of the present application is applied.
  • the communication system includes at least one electronic device 100 and a server 200 .
  • the electronic device 100 may be, for example, a mobile phone (mobile phone), a personal computer (PC), a tablet computer (Pad), a notebook computer, a desktop computer, a notebook computer, a computer with a transceiver function, a virtual reality reality, VR) terminal equipment, augmented reality (AR) terminal equipment, wearable devices, vehicle-mounted equipment, artificial intelligence (artificial intelligence, AI) equipment and other terminal equipment.
  • Operating systems installed on the electronic device 100 include but are not limited to or other operating systems.
  • the electronic device 100 may be a fixed device or a portable device. This application does not limit the specific type of the electronic device 100 or the operating system installed.
  • the server 200 may be a device or server with computing functions such as a cloud server or a network server.
  • Server 200 may be one server, or a server cluster composed of multiple servers, or It is a cloud computing service center.
  • the electronic device 100 can obtain details of various applications from the server 200 and display the details of various applications.
  • the application may be an application 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 process persistence in the background (or whether the application is a keep-alive application, whether the application has background persistence behavior, or whether the application has keep-alive behavior, etc.), background Related explanations of persistence, the impact of processes resident in the background on electronic devices, etc.
  • the app details can be used to assist users in determining whether to install an app or uninstall an app.
  • the server 200 in the embodiment of this application can be implemented by different devices.
  • the server 200 in the embodiment of the present application can be implemented by the communication device in Figure 4.
  • Figure 4 shows a schematic diagram of the hardware structure of the server 200 provided by the embodiment of the present application.
  • the server 200 includes at least one processor 401, a communication line 402, a memory 403 and at least one communication interface 404.
  • the processor 401 can be a general central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more processors used to control the execution of the program of the present application. integrated circuit.
  • CPU central processing unit
  • ASIC application-specific integrated circuit
  • Communication line 402 may include a path that carries information between the above-mentioned components.
  • the communication interface may be a module, a circuit, a bus, an interface, a transceiver, or other devices that can implement communication functions for communicating with other devices.
  • the transceiver can be an independently configured transmitter, which can be used to send information to other devices.
  • the transceiver can also be an independently configured receiver, which can be used to receive information from other devices. The device receives the information.
  • the transceiver may also be a component that integrates the functions of sending and receiving information. The embodiments of this application do not limit the specific implementation of the transceiver.
  • Memory 403 may be 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 that can store information and instructions.
  • a dynamic storage device can also be an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disk storage, optical disc storage (including compressed optical discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), disk storage media or other magnetic storage devices, or can be used to carry or store desired program code in the form of instructions or data structures and can be used by a computer Any other medium for access, but not limited to this.
  • the memory 403 may exist independently and be connected to the processor 401 through a communication line 402. Memory 403 may also be integrated with processor 401.
  • the memory 403 is used to store computer execution instructions for implementing the solution of the present application, and is controlled by the processor 401 for execution.
  • the processor 401 is used to execute computer execution instructions stored in the memory 403, thereby implementing the display method provided by the following embodiments of the present application.
  • the computer execution instructions in the embodiments of the present application may also be called application codes, instructions, computer programs or other names, which are not specifically limited in the embodiments of the present application.
  • the processor 401 may include one or more CPUs, such as CPU0 and CPU1 in FIG. 4 .
  • the server 200 may include multiple processors, such as the processor 401 and the processor 405 in FIG. 4 . Each of these processors can be a single-CPU
  • the processor may also be a multi-core (multi-CPU) processor.
  • a processor here may refer to one or more devices, circuits, and/or processing cores for processing data (eg, computer program instructions).
  • the above-mentioned server 200 may be a general device or a dedicated device, and the embodiment of this application does not limit the type of the server 200.
  • the server 200 may be a device with a similar structure as shown in FIG. 4 .
  • the structure illustrated in the embodiment of the present application does not constitute a specific limitation on the server 200 .
  • the server 200 may include more or less components than shown in the figures, or some components may be combined, some components may be separated, or different components may be arranged.
  • the components illustrated may be implemented in hardware, software, or a combination of software and hardware.
  • FIG. 5 shows a schematic structural diagram of the electronic device 100 .
  • the electronic device 100 may include a processor 510, an external memory interface 520, an internal memory 521, a universal serial bus (USB) interface 530, a charging management module 540, a power management module 541, a battery 542, an antenna 1, an antenna 2 , mobile communication module 550, wireless communication module 560, audio module 570, sensor module 580, button 590, motor 591, indicator 592, camera 593, display screen 594, and subscriber identification module (subscriber identification module, SIM) card interface 595 wait.
  • a processor 510 an external memory interface 520, an internal memory 521, a universal serial bus (USB) interface 530, a charging management module 540, a power management module 541, a battery 542, an antenna 1, an antenna 2 , mobile communication module 550, wireless communication module 560, audio module 570, sensor module 580, button 590, motor 591, indicator 592, camera 593, display screen 594, and subscriber identification module (subscriber identification module, SIM) card interface 595 wait.
  • the processor 510 may include one or more processing units.
  • the processor 510 may include an application processor (application processor, AP), a modem processor, a graphics processing unit (GPU), and an image signal processor. (image signal processor, ISP), controller, video codec, digital signal processor (digital signal processor, DSP), baseband processor, and/or neural network processor (neural-network processing unit, NPU), etc.
  • application processor application processor, AP
  • modem processor a graphics processing unit
  • GPU graphics processing unit
  • image signal processor image signal processor
  • ISP image signal processor
  • controller video codec
  • digital signal processor digital signal processor
  • DSP digital signal processor
  • baseband processor baseband processor
  • neural network processor neural-network processing unit
  • the controller can generate operation control signals based on the instruction operation code and timing signals to complete the control of fetching and executing instructions.
  • the processor 510 may also be provided with a memory for storing instructions and data.
  • the memory in processor 510 is cache memory. This memory may hold instructions or data that have been recently used or recycled by processor 510 . If processor 510 needs to use the instructions or data again, it can be called directly from the memory. Repeated access is avoided and the waiting time of the processor 510 is reduced, thus improving the efficiency of the system.
  • processor 510 may include one or more interfaces.
  • the charge management module 540 is used to receive charging input from the charger.
  • the charger can be a wireless charger or a wired charger.
  • the power management module 541 is used to connect the battery 542, the charging management module 540 and the processor 510.
  • the power management module 541 receives input from the battery 542 and/or the charging management module 540 and supplies power to the processor 510, internal memory 521, display screen 594, camera 593, wireless communication module 560, etc.
  • the wireless communication function of the electronic device 100 can be implemented through the antenna 1, the antenna 2, the mobile communication module 550, the wireless communication module 560, the modem processor and the baseband processor.
  • Antenna 1 and Antenna 2 are used to transmit and receive electromagnetic wave signals.
  • Each antenna in electronic device 100 may be used to cover a single or multiple communication frequency bands. Different antennas can also be reused to improve antenna utilization. For example: Antenna 1 can be reused as a diversity antenna for a wireless LAN. In other embodiments, antennas may be used in conjunction with tuning switches.
  • the mobile communication module 550 can provide wireless communication including 2G/3G/4G/5G etc. applied on the electronic device 100. Communication solutions.
  • the mobile communication module 550 may include at least one filter, switch, power amplifier, low noise amplifier (LNA), etc.
  • the wireless communication module 560 can provide applications on the electronic device 100 including wireless local area networks (WLAN) (such as wireless fidelity (Wi-Fi) network), Bluetooth (bluetooth, BT), and global navigation satellites.
  • WLAN wireless local area networks
  • Wi-Fi wireless fidelity
  • Bluetooth bluetooth, BT
  • global navigation satellites Global navigation satellite system, GNSS
  • frequency modulation frequency modulation, FM
  • near field communication technology near field communication, NFC
  • infrared technology infrared, IR
  • the antenna 1 of the electronic device 100 is coupled to the mobile communication module 550, and the antenna 2 is coupled to the wireless communication module 560, so that the electronic device 100 can communicate with the network and other devices through wireless communication technology.
  • the electronic device 100 implements display functions through a GPU, a display screen 594, an application processor, and the like.
  • the GPU is an image processing microprocessor and is connected to the display screen 594 and the application processor. GPUs are 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 alter display information.
  • the display screen 594 is used to display images, videos, etc.
  • Display 594 includes a display panel.
  • the electronic device 100 may include 1 or N display screens 594, where N is a positive integer greater than 1.
  • display screen 594 may be used to display details of the application.
  • the electronic device 100 can implement the shooting function through an ISP, a camera 593, a video codec, a GPU, a display screen 594, an application processor, and the like.
  • Camera 593 is used to capture still images or video.
  • the electronic device 100 may include 1 or N cameras 593, where N is a positive integer greater than 1.
  • the external memory interface 520 can be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the electronic device 100.
  • an external memory card such as a Micro SD card
  • Internal memory 521 may be used to store computer executable program code, which includes instructions.
  • the internal memory 521 may include a program storage area and a data storage area.
  • the stored program area can store an operating system, at least one application program required for a function (such as a sound playback function, an image playback function, etc.).
  • the storage data area may store data created during use of the electronic device 100 (such as audio data, phone book, etc.).
  • the processor 510 executes various functional applications and data processing of the electronic device 100 by executing instructions stored in the internal memory 521 and/or instructions stored in a memory provided in the processor.
  • the electronic device 100 can implement audio functions through the audio module 570 and an application processor. Such as music playback, recording, etc.
  • the audio module 570 is used to convert digital audio information into analog audio signal output, and is also used to convert analog audio input into digital audio signals. 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 .
  • the sensor module 580 may include a pressure sensor 180A, a gyro 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, and a touch sensor 180K. , ambient light sensor 180L, bone conduction sensor 180M, etc.
  • the buttons 590 include a power button, a volume button, etc.
  • Key 590 may be a mechanical key. It can also be a touch button.
  • the electronic device 100 may receive key inputs and generate key signal inputs related to user settings and function control of the electronic device 100 .
  • Motor 591 can produce vibration prompts.
  • the indicator 592 may be an indicator light, which may be used to indicate charging status, power changes, or may be used to indicate messages, missed calls, notifications, etc.
  • the SIM card interface 595 is used to connect the SIM card.
  • the above only uses a mobile phone as an example to illustrate the structure of the electronic device 100 in the embodiment of the present application, but does not constitute a limitation on the structure and form of the electronic device 100 .
  • the embodiment of the present application does not limit the structure and form of the electronic device 100.
  • the structure of the electronic device 100 may also be in the form of the server 200 shown in FIG. 4 , and the present application is not limited thereto.
  • the electronic device may include more or less components than those shown in FIG. 5 , some components may be combined, some components may be separated, some components may be replaced, or some components may be replaced by different components. layout.
  • the components illustrated may be implemented in hardware, software, or a combination of software and hardware.
  • FIG. 6 is a software structure block diagram of the electronic device 100 and a module diagram of the server 200 provided by the embodiment of the present application.
  • the software system of the electronic device 100 may adopt a layered architecture, an event-driven architecture, a microkernel architecture, a microservice architecture, or a cloud architecture.
  • the embodiment of the present invention uses a layered architecture
  • the system is taken as an example to illustrate the software structure of the electronic device 100 .
  • the layered architecture divides the software into several layers, and each layer has clear roles and division of labor.
  • the layers communicate through software interfaces.
  • the Android system is divided into four layers, from top to bottom: application layer, application framework layer, Android runtime and system libraries, and kernel layer.
  • the application layer can include a series of application packages. As shown in Figure 6, the application package can include calendar, map, settings, browser, application market, gallery, navigation and other applications.
  • applications such as settings, browsers, and application markets have the function of displaying details of various applications.
  • the electronic device detects the user's related operations on these applications.
  • the electronic device obtains the details of various applications and displays the details of various applications on the relevant interfaces of these applications.
  • the application framework layer provides an application programming interface (API) and programming framework for applications in the application layer.
  • API application programming interface
  • the application framework layer includes some predefined functions.
  • the application framework layer can include window manager, content provider, view system, phone manager, resource manager, notification manager, etc.
  • a window manager is used to manage window programs.
  • the window manager can obtain the display size, determine whether there is a status bar, lock the screen, capture the screen, etc.
  • Content providers are used to store and retrieve data and make this data accessible to applications.
  • Said data can include videos, images, audio, calls made and received, browsing history and bookmarks, phone books, etc.
  • the view system includes visual controls, such as controls that display text, controls that display pictures, etc.
  • a view system can be used to build applications.
  • the display interface can be composed of one or more views. For example, include SMS notification graphics
  • the target display interface can include views that display text and views that display pictures.
  • the phone manager is used to provide communication functions of the electronic device 100 .
  • call status management including connected, hung up, etc.
  • the resource manager provides various resources to applications, such as localized strings, icons, pictures, layout files, video files, etc.
  • the notification manager allows applications to display notification information in the status bar, which can be used to convey notification-type messages and can automatically disappear after a short stay without user interaction.
  • the notification manager is used to notify download completion, message reminders, etc.
  • the notification manager can also be notifications that appear in the status bar at the top of the system in the form of charts or scroll bar text, such as notifications for applications running in the background, or notifications that appear on the screen in the form of conversation windows. For example, text information is prompted in the status bar, a beep sounds, the indicator light flashes, etc.
  • Android Runtime includes core libraries and virtual machines. Android runtime is responsible for the scheduling and management of the Android system.
  • the core library contains two parts: one is the functional functions that need to be called by the Java language, and the other is the core library of Android.
  • the application layer and application framework layer run in virtual machines.
  • the virtual machine executes the java files of the application layer and application framework layer into binary files.
  • the virtual machine is used to perform object life cycle management, stack management, thread management, security and exception management, and garbage collection and other functions.
  • System libraries can include multiple functional modules. For example: surface manager (surface manager), media libraries (Media Libraries), 3D graphics processing libraries (for example: OpenGL ES), 2D graphics engines (for example: SGL), etc.
  • the surface manager is used to manage the display subsystem and provides the fusion of 2D and 3D layers for multiple applications.
  • the media library supports playback and recording of a variety of commonly used audio and video formats, as well as static image files, etc.
  • the media library can support a variety of audio and video encoding formats, such as: MPEG4, H.264, MP3, AAC, AMR, JPG, PNG, etc.
  • the 3D graphics processing library is used to implement 3D graphics drawing, image rendering, composition, and layer processing.
  • 2D Graphics Engine is a drawing engine for 2D drawing.
  • the kernel layer is the layer between hardware and software.
  • the kernel layer at least includes network drivers, display drivers, camera drivers, audio drivers, and sensor drivers.
  • the server 200 includes a scheduling analysis module 601 , a storage module 602 , and a communication module 603 .
  • the scheduling analysis module 601 is used to analyze and generate details of various applications.
  • the storage module 602 is used to store the details of various applications generated by the scheduling analysis module 601, and the communication module 603 is used to send the stored details of various applications to other devices (for example, the electronic device 100).
  • the following is an example of the workflow of the electronic device 100 hardware, software, and interaction with the server 200 based on a scenario in which a user opens the application market.
  • the corresponding hardware terminal is sent to the kernel layer.
  • the kernel layer processes touch operations into original input events (including touch coordinates, timestamps of touch operations, and other information).
  • Raw input events are stored in the kernel layer.
  • the application framework layer obtains the original input event from the kernel layer and identifies the control corresponding to the input event.
  • the touch operation is to click on the application market of the application layer
  • the application market starts the network driver by calling the kernel layer, and sends a request message to the server 200 through the wireless communication module 160 or the mobile communication module 150.
  • the request message can be used to obtain details of various applications in the application market.
  • the server 200 receives the request message from the electronic device 100 through the communication module 603, and returns the details of various applications stored in the storage module 602 to the electronic device 100 through the communication module 603.
  • the electronic device 100 calls the kernel layer to start the display driver and displays the details of the various applications through the display screen 594.
  • the electronic device 100 is a mobile phone and the server 200 is a server.
  • the embodiment of the present application provides a display method.
  • the server generates details of various applications.
  • the application details include but are not limited to whether the application supports the process to persist in the background (or whether the application is a keep-alive application, or whether the application has a background persistence). Resident behavior, or whether the application has a keep-alive behavior, etc.), related explanations of background persistence, the impact of application processes resident in the background on electronic devices, etc.
  • the server can then send some or all of the details of various applications to the mobile phone, and the mobile phone can display the application details. In this way, by informing users of the existence of an application and its possible impact on electronic devices, users can decide whether to install or uninstall an application, which brings convenience to users and improves the efficiency of human-computer interaction.
  • the user still chooses to install the application after learning about the behavior of the application and the impact it may have on electronic devices, it means that the behavior of the application and the impact it may have on electronic devices are acceptable to the user, and therefore it is not acceptable to the user. Will not affect user experience. If the user chooses to uninstall or not install the application after learning about the behavior of an application and the impact it may have on electronic devices, this can solve the problem of the keep-alive application being unable to be completely checked and kill, thereby avoiding the keep-alive application process. Various problems caused to electronic equipment.
  • Figure 7 shows a schematic flowchart of a method for the server to generate details of various applications. As shown in Figure 7, the method includes the following steps.
  • the server obtains the target characteristics of the application.
  • applications can be applications developed by developers and then submitted to application markets, networks, clouds, etc., and the server can obtain these applications.
  • application characteristics include many types, such as: development characteristics, composition characteristics, operation characteristics, etc.
  • Development characteristics may refer to the development language, development framework, etc. used by the application
  • composition characteristics may refer to the components that constitute an application, etc.
  • operation characteristics may refer to the characteristics of the application running in electronic devices, etc.
  • the target characteristics of the application are the running characteristics of the application in the electronic device system, which can be used to reflect the behavior that exists when the application is running in the electronic device system, and which can correspond to the system service used to keep the application alive.
  • the target features can be used for keep-alive applications.
  • the target features of the application include one or more of static features and dynamic sandbox features (i.e., dynamic features).
  • the static characteristics and/or dynamic sandbox characteristics of an application can be understood as the system services used by an application during its running process. These system services can be used to keep the process of an application alive.
  • these system services can be used in the application's After the process is checked and killed, immediately restart the process of the application, or ensure that the process of an application is not checked and killed, etc.
  • the static characteristics of an application can refer to the system services configured in the application's configuration file (for example, the files in the installation package of the application), and the dynamic sandbox characteristics of the application can refer to the system services actually used during the running process of the application.
  • the static features and dynamic sandbox features may be the same or different.
  • An application's target characteristics may include both one or Multiple static features, or, include one or more dynamic sandbox features simultaneously.
  • the corresponding static features and dynamic sandbox features may be the same or different.
  • the static characteristics of the application include but are not limited to service (service), static broadcast, mutual pull between applications, registration push, scheduled wake-up, Dalvik virtual machine DEX application programming interface (application programming interface, API) ), executable linkable format (ELF) API, etc.
  • service is one of the components of Android. It is an application component that runs in the background without a user interface.
  • the service can be started by other components of the application (such as activities, etc.).
  • a service can always run in the background of the system.
  • Broadcast Receiver is also one of the components of Android. It is a listener used to monitor broadcast messages in the system. Among them, Broadcast Receiver is divided into statically registered broadcasts (i.e. static broadcasts) and dynamically registered broadcasts (i.e. dynamic broadcasts). For example, static broadcast can be configured in the AndroidManifest.xml file. Static broadcasts can persist in the system and can still exist after the application process ends. Dynamic broadcast will not persist in the system and will end when the application process ends.
  • Interaction between applications can also be called mutual awakening between applications. After one application is killed, it can be restarted (or awakened) through another application. For example: if the camera application is killed, when starting the browser application, that is The camera app can be relaunched through the browser app.
  • Registered push refers to the active push of messages by the application.
  • the application can proactively push messages.
  • a process of the application needs to be kept alive in the background of the system so that the application can maintain communication with the server.
  • the application When receiving data from the server, the application creates a notification and pushes it out.
  • Scheduled wake-up refers to regularly waking up an application process by setting a timer.
  • DEX can refer to the executable file format in the virtual machine included in Android Runtime in the software architecture of the electronic device shown in Figure 6.
  • DEX API refers to calling DEX bytecode through the API.
  • ELF can refer to the format of the executable code at the kernel layer in the software architecture of the electronic device shown in Figure 6.
  • ELF API refers to calling the ELF code through the API.
  • the ELF code can also call the API in the electronic device system. This application does not specifically limit this API.
  • the static characteristics of an application can be obtained by analyzing the code of the installation package corresponding to the application.
  • the server can obtain static characteristics of various applications through static analysis.
  • static analysis refers to a means of obtaining the functions of an application using various technical means such as word analysis and syntax analysis without running the application code.
  • the Android installation package (APK) file corresponding to an application includes files such as AndroidManifest.xml, Classes.dex and res.
  • APK Android installation package
  • the clear text AndroidManifest.xml file can be obtained.
  • Various information such as components, component permissions, component startup locations, and basic application information are defined in it.
  • the static characteristics of the application can be obtained.
  • the dynamic sandbox features of an application include, but are not limited to, service, static broadcast, inter-application mutual pull, registration push, scheduled wake-up, DEX API, ELF API, etc. Details about the characteristics of each dynamic sandbox The introduction can be referred to the above and will not be repeated here.
  • the sandbox is a security mechanism that provides an isolation environment for executing applications, that is, different applications are isolated and run in different environments.
  • the dynamic sandbox characteristics of an application can be obtained by building a sandbox and running the code of the installation package corresponding to the application. For example, by modifying the source code of the operating system, building a sandbox, using virtualized disks, memory, and network resources to run applications respectively, and then detecting the running behavior of the application, the dynamic sandbox of the application can be obtained feature. Since the construction of a sandbox is an existing technology, its specific implementation may refer to relevant introductions in the existing technology.
  • static features and dynamic sandbox features are introduced using the Android operating system as an example. They are only illustrative explanations to facilitate understanding of this application and do not constitute a limitation of this application. In practical applications, other more features can also be included. Moreover, for applications in different operating systems, such as iOS, Android, Harmony, Windows, etc., the static features and dynamic sandbox features they include may be the same or different.
  • the application may perform some operations such as obfuscation, encryption, etc. in the configuration file, it may not be possible to fully detect possible behaviors of the application only by detecting the static characteristics of the application. Therefore, the real runtime behavior of the application can also be obtained by obtaining the dynamic sandbox characteristics of the application. In addition, some behaviors of the application may need to be triggered under certain conditions, such as triggering when the power of the electronic device is 80%. Therefore, it may not be possible to fully detect possible behaviors of the application only by detecting the dynamic sandbox characteristics of the application. , Therefore, by obtaining the static characteristics of the application, you can also obtain some application behaviors that are not detected when running the application using the dynamic sandbox. In summary, by detecting the static features and dynamic sandbox features of the application, that is, by combining static detection and dynamic sandbox detection, some possible behaviors of the application can be more comprehensively obtained, and the accuracy of the generated application details can be improved.
  • the server generates application details according to the target characteristics of the application.
  • the server can generate details for one or more applications.
  • the server analyzes the target characteristics of the detected application through the scheduling analysis module 601 shown in Figure 6, and generates application details.
  • Table 1 shows an example of details of a server-generated application.
  • “Application ID” can be used to identify different applications.
  • “Application name” is the name of an application.
  • "Package name” is the name of the installation package corresponding to the application.
  • the “hash value” can be used to identify different versions of the application.
  • the “hash value” can be calculated and obtained through various hash algorithms. This application does not limit this. In view of the fact that the method of calculating the "hash value” is an existing technology, For its specific implementation, reference can be made to the existing technology and will not be described in detail in this article.
  • “Technical means ID” is used to identify the keep-alive policy adopted by an application.
  • “Technical means name” is an application Use the name of the keepalive policy being used.
  • Numberer of processes refers to the number of processes that an application may start in the background of the system based on the keep-alive policy (or the number of processes that may be started when the application resides in the background of an electronic device).
  • Minimum supported version refers to the minimum version of the operating system supported by technical means.
  • Highest supported version refers to the highest version of the operating system supported by technical means.
  • Impact refers to the impact that the "technical means” adopted by the application or the background resident behavior supported by the application may have on electronic devices.
  • impact can be information such as "too many applications running in the background will cause the device to freeze, and some applications may push advertisements in the background, affecting the user experience.”
  • “Description” is a relevant introduction (or explanation) of "technical means” or “background persistence”.
  • “description” can be such as “background persistence” means that when the application is started, the application cannot pass If other means are closed, it will always run in the background.”
  • Whether it supports background resident behavior refers to whether an application supports background resident behavior (or whether an application will always run in the background, or whether an application is a keep-alive application, or whether an application will take a keep-alive action). policy, or whether an application has a keep-alive behavior, etc.). It can be understood that if an application uses several "technical means”, it means that the application supports background resident behavior. If an application does not use any “technical means", it means that the application does not support background resident behavior.
  • the application details generated by the server may only include details of applications that support background resident behavior or only include details of applications that do not support background resident behavior.
  • the application details generated by the server may not only include details of applications that support background resident behavior, but may also include details of applications that do not support background resident behavior.
  • an application may use one or more keepalive policies. That is, an "application ID” (or “application name”) may correspond to multiple different “technical means IDs” (or “technical means names”), and different “technical means IDs” correspond to the “minimum supported version” and/or Or the “highest supported version” may or may not be the same.
  • Exemplary keep-alive strategies that an application may adopt include, but are not limited to, setting the service as a foreground service; listening for static broadcasts; setting timers to regularly wake up the application's process; interoperability between applications; a dual-process keep-alive strategy in the application When it is opened, two processes are started. When one process is killed, the other process that is still running will wake up the killed process and so on.
  • An application can also combine the aforementioned strategies to achieve process keepalive. More keep-alive strategies can also refer to existing technologies.
  • the details of the browser generated by the server can be shown in Table 2.
  • the keep-alive strategy adopted by the browser is "file lock".
  • the number of processes started in the background is 6.
  • the minimum version of the supported operating system is Android 2.
  • the highest version of the operating system is Android 12, and it supports background resident behavior.
  • file lock refers to the use of multiple processes to determine whether the other process has been closed by using one process to obtain the file lock of another process. If a process successfully obtains the file lock of another process, it means that the other process has been shut down, and the other process will be immediately pulled up (or awakened, started, etc.) to keep the process alive.
  • the file lock of the process means that the other process has not been closed, so there is no need to pull up the other process.
  • the file lock can be assigned by the electronic device to the started process. After a process creates a sub-file, it locks the sub-file according to the assigned file lock. After the lock is completed, it can instruct another process to monitor its own file lock. status.
  • the technical means corresponding to an application can be determined based on one or more of the target characteristics of the application, that is, the keep-alive strategy adopted by an application can be determined based on one or more of the target characteristics, that is, the details of an application It can be determined based on the target characteristics of the application.
  • the server can also store the generated application details. Subsequently, the application details can be sent to the mobile phone and displayed by the mobile phone.
  • the details of these applications can also be used for some other operations, such as determining the levels of these applications.
  • the use of the details of the applications in this application is not limited to this.
  • the above example uses the server to generate application details.
  • the process of generating application details can also be performed by an electronic device, which is not limited in this application.
  • Figure 8 shows a schematic flowchart of a display method provided by an embodiment of the present application. As shown in Figure 8, the method includes the following steps:
  • the mobile phone receives the user's target operation (ie, the first operation).
  • the target action can be used to instruct the phone to display the details of the application.
  • the application may be an application installed on the mobile phone or an application not installed on the mobile phone.
  • the target operation may be an operation used by the user to launch the application market.
  • the mobile phone displays a main interface 900.
  • the main interface 900 includes various applications, and different applications can be used to implement different functions. These multiple applications include application market 901.
  • the target operation may be a user's click operation on the application market 901 .
  • the target operation may also be the user's operation of viewing an application in the application market.
  • the mobile phone displays a main interface 1000, and the main interface 1000 includes an application market 1001.
  • the mobile phone detects, for example, the user's click operation on the icon of the application market 1001.
  • the mobile phone can display the main interface 1010 of the application market, where the main interface 1010 includes various types of applications, such as games, videos, music, etc. Users can download and install an application based on actual needs.
  • the main interface 1010 may also include a search bar 1012 As well as the navigation bar 1013, the search bar 1012 can be used to quickly find different applications, and the navigation bar 1013 can be used to quickly enter different sub-interfaces of the application market.
  • the target operation may be the user's operation of viewing an application in the home interface 1010.
  • the target operation may be the user's click operation on the display area 1011 of an application in the home interface 1010.
  • the user can also view applications in other ways.
  • the navigation bar 1013 included in the main interface 1010 includes one or more option buttons, and different option buttons can be used to enter different interfaces.
  • the mobile phone detects an operation such as the user's click on the "My" option 1014 on the main interface 1010, and in response to the operation, as shown in (2) in Figure 11, the mobile phone may display the interface 1100.
  • the interface 1100 includes some services, such as update management 1101, installation management 1102, and so on.
  • the update management 1101 can be used to view the applications that need to be updated among the currently installed applications on the mobile phone.
  • the user can use the update management 1101 to update the versions of the applications installed in the mobile phone according to actual needs.
  • Installation management 1102 can be used to view installed applications in the current mobile phone.
  • the target operation may be a user's click operation on the update management 1101 or the installation management 1102 .
  • the interface 1100 can also include other services, such as: installation package management, cleaning acceleration, quick application management, settings, etc. Since these services are existing technologies, their detailed introduction can refer to the existing technologies, which are not discussed here. Let’s introduce them one by one.
  • the target operation may be an operation of viewing the application through setting the application.
  • the mobile phone displays a main interface 1200, which includes one or more applications, including a setting application 1201.
  • the mobile phone detects a click operation such as the user's click on the icon of the settings application 1201.
  • the mobile phone displays a settings interface 1210, where the settings interface 1210 includes a notification option 1211, an application and service option 1212.
  • the notification option 1211 can be used to view the installed applications on the phone that have the function of automatically pushing messages.
  • the application and service option 1212 can be used to manage the installed applications on the phone, such as: uninstallation, permission management, startup management, etc.
  • the target operation is such as the user's click operation on the notification option 1211 or the application and service option 1212.
  • the setting interface 1210 may also include other setting options, such as: WLAN, Bluetooth, mobile network, desktop and wallpaper, sound and vibration, etc.
  • the target operation may be an operation used by the user to search for the application.
  • the mobile phone displays the main interface 1500.
  • the main interface 1500 includes the browser 1501.
  • the mobile phone detects the user's operation to start the browser 1501.
  • the mobile phone detects a user's click operation on the icon of the browser 1501, and in response to the operation, as shown in (2) in Figure 15, the mobile phone displays a search interface 1510, which includes a search box 1511 and a search button. 1512 etc.
  • the search box 1511 can be used for the user to input the content they want to search
  • the search button 1512 can be used to start the search function.
  • the target operation may be an operation in which the user enters the name of the application (such as Game 1) in the search box 1511 and clicks the search button 1512.
  • the search interface 1510 may also include some other options, such as recommendations, videos, selections, entertainment, etc. Since these options are all existing technologies, reference may be made to the existing technologies for their specific introduction.
  • the target operation may also be the user's operation on the icon of the application, for example, the user's key operation on the icon of the application on the mobile phone desktop (such as the main interface 900 shown in (1) in Figure 9), Voice operations, gesture operations, and the like.
  • target operations described above are only exemplary descriptions, and in actual applications, the target operations may include more situations.
  • the mobile phone obtains application details.
  • the mobile phone can obtain the application details generated by itself from its own memory or other devices. It can be understood that after the mobile phone generates the application details, it can either store the application details in its own memory or send them to other devices for storage.
  • the mobile phone can obtain the application details from the server.
  • the server may send the generated details of all applications to the mobile phone. Accordingly, the mobile phone receives the details of all applications from the server. In this way, the server can send all application details directly to the mobile phone without filtering and other operations, which can reduce the calculation amount of the server and improve the work efficiency of the server.
  • the server may send the generated details of some applications to the mobile phone. Accordingly, the mobile phone receives partial application details from the server.
  • the server can only include details of applications that support background resident behavior.
  • the details of the application are sent to the phone, or only the details of the application that do not support background persistent behavior are sent to the phone.
  • the mobile phone can also determine the details of other applications besides the partial application based on the received details of the partial application.
  • the mobile phone can first send to the server the version of the current operating system of the mobile phone and/or the application currently viewed by the user (or the application to be displayed by the mobile phone). ).
  • the server can then filter out the details of the corresponding application based on the current operating system version of the mobile phone and/or the application currently viewed by the user.
  • the server determines the applications that support a version higher than or equal to Android 11 based on the "highest supported version" in the example shown in Table 1.
  • the server determines the details of the browser based on the "application ID" (and/or "application name”) in the example shown in Table 1.
  • the server will use the "highest supported version” and "application ID" (and/or " Application name") determines whether the version supported by the browser includes Android 11. If it is included, the server can send the browser corresponding details to the mobile phone. If it is not included, the server can determine that the browser does not support background behavior, and the server can send The browser does not support background resident behavior, "description", impact and other information in the example shown in Table 1 to be sent to the mobile phone.
  • the application details received by the mobile phone can be adapted to the current mobile phone, and the server only returns part of the application details, which can prevent the application details from being stolen by others, improve the security of the information, and also reduce the gap between the server and the electronic device.
  • the amount of information transmitted improves the communication efficiency between servers and electronic devices.
  • the mobile phone can also store the application details for subsequent use.
  • the mobile phone displays application details.
  • the mobile phone can only display the details of applications that support background resident behavior or the details of applications that do not support background resident behavior. It can also display the details of applications that support background resident behavior and those that do not support background resident behavior at the same time.
  • the details of the application are not limited in this application.
  • the mobile phone can determine how to display the application details based on the received application details. For example, if the mobile phone only receives the details of the application that supports the background resident behavior, the mobile phone can only display the details of the application that supports the background resident behavior. Details will not be displayed for applications other than these applications. Alternatively, the mobile phone can first determine the details of other applications except this part of the application based on the received details of the application that supports background resident behavior, and then only display the details of other applications except this part of the application, or display both Details of apps that support background persistence behavior and details of apps that don't support background persistence behavior. Similarly, in the case where the mobile phone only receives details of applications that do not support background resident behavior, the display method is similar to the aforementioned method.
  • the mobile phone when the mobile phone only displays the details of a part of the application, the mobile phone can also display prompt information to remind the user about other applications except this part of the application.
  • the prompt message can be such as "If the application does not display relevant information about whether it supports background persistence behavior, it means that the application does not support background persistence behavior.”
  • the prompt message can be such as "If the application does not display relevant information about whether it supports background resident behavior, it means that the application supports background resident behavior.”
  • the mobile phone can display part of the application details first, and then display other parts of the application details.
  • the mobile phone can also directly display all the details of the application, and this application is not limited to this.
  • the mobile phone detects an operation such as a user's click on the icon of the application market 901.
  • the mobile phone displays the application market.
  • the main interface 910. the main interface 910 of the application market includes multiple applications.
  • these multiple applications can be applications that are not installed on the mobile phone.
  • the display area 911 of each application includes the application's icon, name, and application details 912.
  • the details 912 of the application may only include a part of the details of the application (ie, the first details) such as those shown in Table 1 above.
  • the mobile phone detects the user's operation for instructing the mobile phone to display other details of the application. For example, the mobile phone detects similar operations such as the user's tap (or click) on the application details 912, as shown in (( in Figure 9 3), the mobile phone can display other detailed information of the application (i.e., the second details), such as: "Description", “Impact”, “Number of Processes", etc. shown in Table 1 above. This application does not impose specific restrictions on this. .
  • the mobile phone can display other details of the application in a floating window, such as the floating window 920, or can display other details of the application by jumping to a new interface. This application is not limited to this.
  • the mobile phone detects an operation such as a user's click on the application market 1001 , and in response to the operation, as shown in (2) in FIG. 10 , the mobile phone displays the application market.
  • the main interface 1010 includes multiple applications.
  • the multiple applications can be applications that are not installed on the mobile phone.
  • the display area 1011 of each application includes the icon, name, etc. of the application.
  • the mobile phone may not display application details in the main interface 1010.
  • the phone detects a user action that instructs the phone to display the app's details, such as For example, the mobile phone detects a user's click operation on the display area 1011 of an application (such as music).
  • the mobile phone displays an interface 1020, in which the application is included in the interface 1020.
  • the details display area 1021 can be used to display application details such as those shown in Table 1, such as: "Whether background persistence is supported", “Description”, “Impact”, “Number of processes", etc. This application does not limit this .
  • the mobile phone detects the user's operation of instructing the mobile phone to display the details of the application. For example, the mobile phone detects the user's click operation on the display area 1011 of the application. In response to the operation, as shown in (4) in Figure 10, the mobile phone displays Application details interface 1030. Among them, the application details 1031 are included in the application details interface 1030 .
  • the application details 1031 may include only part of the application details such as those shown in Table 1 above, for example, only include information related to "whether background persistence is supported.”
  • the mobile phone detects the user's operation to instruct the mobile phone to display other details of the application, for example, the mobile phone detects similar operations such as the user's tap (or click) on the application details 1031, which is the same as (3) in Figure 9 Similar to the displayed other details of the application 920, the mobile phone then displays other detailed information of the application, such as: “Description”, “Impact”, “Number of Processes”, etc. shown in Table 1 above. This application does not impose specific restrictions on this.
  • the mobile phone detects a click operation such as the user's click on the update management 1101 , and in response to the operation, as shown in (3) in Figure 11 , the mobile phone can display the interface 1110 , the interface 1110 includes one or more applications to be updated, such as: Music 1, Music 2, Game 4, etc.
  • the details of each application can be displayed in a manner such as (3) in Figure 10, or can be displayed in a manner such as (4) in Figure 10.
  • the interface 1110 may also include a drop-down button 1111, which may be used to hide or display application details and/or other information about the application (such as the size of the installation package, the version of the installation package, etc.).
  • the mobile phone detects a click operation such as the user's click on the installation management 1102.
  • the mobile phone can display an interface 1120, which includes one or more installed software on the mobile phone. application.
  • the details of each application can be displayed in a manner such as (3) in Figure 10, or in a manner such as (4) in Figure 10.
  • the interface 1120 may also include a drop-down button 1121, which may be used to hide or display application details and/or other information (such as an uninstall button, a management button, etc.).
  • the mobile phone detects a click operation such as the user's click on the notification option 1211.
  • the mobile phone displays a notification interface 1220, where in the notification interface 1220 includes one or more applications already installed in the mobile phone.
  • the notification interface 1220 may also include other options, such as desktop icon badges, lock screen notifications, batch management, etc. Since these options are existing technologies, their specific introduction and implementation may refer to the existing technologies.
  • the display area 1221 of each application includes the icon, name and application details 1222 of each application.
  • the application details 1222 may only include part of the application details such as those shown in Table 1 above, for example, only include "whether the background is supported.”Permanent" related information.
  • the mobile phone detects the user's operation for instructing the mobile phone to display other details of the application. For example, the mobile phone detects a similar operation such as the user's tap (or click) on the application details 1222, which is the same as (in Figure 9 3) Other details of the application shown are similar to 920.
  • the mobile phone can display other detailed information of the application, such as: "Description”, “Impact”, “Number of Processes", etc. shown in Table 1 above. This application does not specify this. limit.
  • the mobile phone detects the user's operation for instructing the mobile phone to display the details of the application. For example, the mobile phone detects the user's click operation on the display area 1301 of the application.
  • the mobile phone displays Interface 1310, which includes an application details display area 1311, which can be used to display details in the application such as those shown in Table 1, such as: "Whether background persistence is supported", “Description”, “Impact”, “Number of processes", etc., this application does not limit this.
  • the mobile phone can also display application details in a manner such as shown in (4) in Figure 10.
  • the introduction of (1) and (2) in Figure 13 please refer to the relevant introduction of (1) and (2) in Figure 12 respectively.
  • the mobile phone can also display various applications in other ways, such as: "Batch Management” shown in (3) in Figure 12 or (3) in Figure 13. Further display such as (3) in Figure 12 or (3) in Figure 13 3) various applications shown, and the details of the applications are displayed on the batch management interface in a manner such as shown in Figure 12, Figure 13, etc., the present application is not limited to this.
  • the mobile phone detects an operation such as the user's click on the application and service option 1212.
  • the mobile phone displays the application management interface 1400, where , the application management interface 1400 includes one or more applications that have been installed on the mobile phone.
  • the application management interface 1400 may also include other options, such as application management, application startup management, service management, etc. Since these options are all existing technologies, this article will not introduce them one by one.
  • the details of each application may be displayed in a manner such as that shown in Figure 12 or in a manner such as that shown in Figure 13, and the present application is not limited thereto.
  • the mobile phone detects the operation of the user entering the name of the application (such as Game 1) in the search box 1511 and clicking the search button 1512, and responds to the operation, as shown in (3) in Figure 15
  • the mobile phone displays a search interface 1520, in which the searched game 1 is included in the search interface 1520.
  • the search interface 1520 includes a details display area 1521 of game 1, which can be used to display details of applications such as those shown in Table 1. , such as: "Whether background resident support is supported", “Description”, “Impact”, “Number of processes", etc. This application does not limit this.
  • the mobile phone can display the details of the application in a manner such as (3) in Figure 12, or can display the details of the application in a manner such as (4) in Figure 13.
  • the mobile phone does not display application details in the search interface 1600.
  • the mobile phone detects, for example, the user's click operation on the application display area 1601, in response to the operation, as shown in (4) in Figure 16, the mobile phone displays an interface 1610, wherein the interface 1610 includes the application details display area. 1611, which can be used to display application details such as those shown in Table 1, such as: "Whether background persistence is supported", “Description”, “Impact”, “Number of processes", etc.
  • the mobile phone can display the details of the application in a manner such as (3) in Figure 12, or can display the details of the application in a manner such as (4) in Figure 13.
  • (1) and (2) in Figure 16 please refer to the introduction of (1) and (2) in Figure 15 respectively.
  • the mobile phone detects the user's response to the application icon (for example: the application icon in the interface 900 shown in (1) in Figure 9, the interface 1000 shown in (1) in Figure 10, the Key operations, voice operations, gesture operations, etc. of the interface 1200 shown in (1), the interface 1500 shown in (1) in FIG. 15, etc.)
  • the mobile phone can directly display the details of the application on the current interface in a manner such as (3) in Figure 12, or can also display the application in a manner such as (4) in Figure 13 details.
  • the mobile phone can also jump to a new interface, where the details of the application are displayed in a manner such as (3) in Figure 12, or the details of the application are displayed in a manner such as (4) in Figure 13 .
  • the mobile phone can also jump to the relevant interfaces of other applications that have the function of displaying application details (the application market shown in Figure 10, the settings application shown in Figure 12, the browser shown in Figure 15, etc.) Show details for this app.
  • the mobile phone can also install or uninstall the corresponding application according to the user's operation.
  • each interface may include more or less content, or may include more or fewer interfaces. This application does not impose specific limitations on this.
  • Figure 17 shows a schematic flowchart of yet another display method provided by an embodiment of the present application.
  • the method includes the following steps:
  • the electronic device receives the user's first operation.
  • the electronic device sends a request message to the server.
  • the server receives the request message from the electronic device.
  • the request message may be used to instruct the server to send application details to the electronic device. Details of the application include whether the application will persist in the background of the electronic device.
  • the details of the application may also include one or more of the following: an explanation of background persistence, the impact of background persistence on the electronic device, and the number of processes started when the application resides in the background of the electronic device.
  • the application details may also include other contents such as the application details shown in Table 1, and the present application is not limited thereto. It can be understood that the application details may include details of one or more applications.
  • the request message includes a version of the operating system of the electronic device and/or identification information of the application.
  • the identification information of the application may be used to indicate the application to be displayed by the electronic device.
  • the request message may not include the version of the operating system of the electronic device and the identification information of the application.
  • the server determines application details according to the request message.
  • the server may determine details of the application corresponding to the current electronic device.
  • the server may determine that all generated application details need to be sent.
  • the server sends application details to the electronic device. Accordingly, the electronic device receives application details from the server.
  • the server may send details of the application corresponding to the current electronic device to the electronic device.
  • the server may send the generated details of all applications to the electronic device.
  • the server can send all the details of the application to the electronic device at once, or it can send the details to the electronic device in multiple times. This application does not limit this.
  • the electronic device displays application details.
  • the details of the application may be used to instruct the user to avoid the application remaining in the background of the electronic device by uninstalling the application or not installing the application.
  • the electronic device may display part of the application details first, and then display other parts of the application details.
  • the electronic device may first display an overview of the application details.
  • the summary of the application details may be generated by the server based on the application details shown in Table 1, or the electronic device may, after receiving the application details sent by the server, Generated based on received application details.
  • the summary of the details can be whether the application will persist in the background of the electronic device, etc.
  • the electronic device receives the user's operations, such as clicks, taps, and the like on the displayed overview of the application details.
  • the electronic device displays the detailed introduction of the application details, such as: background resident explanation, background resident explanation, etc.
  • the detailed introduction of the application details can also be as shown in Table 1 Other content, this application is not limited to this.
  • the electronic device can also display all the details of the application at the same time.
  • This application does not specifically limit the way in which the electronic device displays the details of the application.
  • the electronic device receives the user's second operation.
  • the second operation may be the user's uninstall operation of several applications.
  • the server Based on the above technical solution, the server generates the details of the application.
  • the details of the application include but are not limited to whether the application supports the process to persist in the background (or whether the application is a keep-alive application, or whether the application has background resident behavior, etc.), background Related explanations of persistence, the impact of application processes resident in the background on electronic devices, etc.
  • the server can then send some or all of the application details to the phone, and the phone can display the application details. In this way, by informing users of the existence of an application and its possible impact on electronic devices, users can make their own decisions about whether to install or uninstall an application, which brings convenience to users and improves the efficiency of human-computer interaction.
  • the user still chooses to install the application after learning about the behavior of the application and the impact it may have on electronic devices, it means that the behavior of the application and the impact it may have on electronic devices are acceptable to the user, and therefore it is not acceptable to the user. Will not affect user experience. If the user chooses to uninstall or not install the application after learning about the behavior of an application and the impact it may have on electronic devices, this can solve the problem that the keep-alive application cannot be completely checked and killed, thereby avoiding the problem of keep-alive Various problems caused by application processes to electronic devices.
  • This application is an embodiment that can divide electronic devices and servers into functional modules according to the above method examples.
  • each functional module can be divided corresponding to each function, or two or more function sets can be divided into into one processing unit.
  • the above-mentioned integrated units can be implemented in the form of hardware or software function modules. It should be noted that the division of units in the embodiment of the present application is schematic and is only a logical function division. In actual implementation, there may be other division methods.
  • FIG. 18 it is a schematic structural diagram of an electronic device 1800 provided by an embodiment of the present application.
  • the electronic device 1800 can be used to implement the methods described in each of the above method embodiments.
  • the electronic device 1800 may specifically include: a processing unit 1801, a communication unit 1802, and a display unit 1803.
  • the processing unit 1801 is configured to support the electronic device 1800 in performing step S802 in FIG. 8 . And/or, the processing unit 1801 is configured to support the electronic device 1800 in performing step S1707 in FIG. 17 . And/or, the processing unit 1801 is also used to support the electronic device 1800 to perform other steps performed by the electronic device in the embodiment of the present application.
  • the communication unit 1802 is configured to support the electronic device 1800 in performing step S801 in FIG. 8 . And/or, the communication unit 1802 is configured to support the electronic device 1800 to perform step S1701, step S1702, step S1704, step S1706, etc. in FIG. 17 . And/or, the communication unit 1802 is also used to support the electronic device 1800 to perform other steps performed by the electronic device in the embodiment of the present application.
  • the display unit 1803 is configured to support the electronic device 1800 in performing step S803 in FIG. 8 . And/or, the display unit 1803 is configured to support the electronic device 1800 in performing step S1705 in FIG. 17 . And/or, the display unit 1803 is also used to support the electronic device 1800 to perform other steps performed by the electronic device in the embodiment of the present application.
  • the electronic device 1800 shown in Figure 18 may also include a storage unit (not shown in Figure 18), which stores programs or instructions.
  • a storage unit not shown in Figure 18
  • the processing unit 1801 executes the program or instruction
  • the electronic device 1800 shown in FIG. 18 can perform the method shown in FIG. 8 and/or FIG. 17 .
  • the processing unit 1801 involved in the electronic device 1800 shown in FIG. 18 can be implemented by a processor or a processor-related circuit component, and can be a processor or a processing module.
  • the communication unit can be implemented by a transceiver or a transceiver-related circuit component, and can be a transceiver or a transceiver module.
  • the display unit 1803 may be implemented by display screen related components.
  • FIG 19 it is a schematic structural diagram of a server 1900 provided by an embodiment of the present application.
  • the server 1900 can be used to implement the methods described in each of the above method embodiments.
  • the server 1900 may specifically include: a processing unit 1901 and a communication unit 1902.
  • the processing unit 1901 is used to execute the support server 1900 to execute steps S701 and S702 in FIG. 7 . 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 also used to support the server 1900 to perform other steps performed by the server in the embodiment of this application.
  • the communication unit 1902 is used to execute the support server 1900 to execute step S1702, step S1704, etc. in FIG. 17 . And/or, the communication unit 1902 is also used to support the server 1900 in performing other steps performed by the server in the embodiment of this application.
  • the server 1900 shown in Figure 19 may also include a storage unit (not shown in Figure 19), which stores programs or instructions.
  • a storage unit not shown in Figure 19
  • the server 1900 shown in FIG. 19 can execute the method shown in FIG. 7 and/or FIG. 17 .
  • the processing unit 1901 involved in the server 1900 shown in Figure 19 can be implemented by a processor or a processor-related circuit component, and can be a processor or a processing module.
  • the communication unit can be implemented by a transceiver or a transceiver-related circuit component, and can be a transceiver or a transceiver module.
  • the chip system includes at least one processor 2001 and at least one interface circuit 2002.
  • the processor 2001 and the interface circuit 2002 may be interconnected via lines.
  • interface circuitry 2002 may be used to receive signals from other devices.
  • interface circuit 2002 may be used to send signals to other devices (eg, processor 2001).
  • the interface circuit 2002 can read instructions stored in the memory and send the instructions to the processor 2001.
  • the electronic device may be caused to perform various steps performed by the electronic device in the above embodiment, or the server may be caused to perform various steps performed by the server in the above embodiment.
  • the chip system may also include other discrete devices, which are not specifically limited in the embodiments of this application.
  • processors in the chip system there may be one or more processors in the chip system.
  • the processor can be implemented in hardware or software.
  • the processor may be a logic circuit, an integrated circuit, or the like.
  • the processor may be a general-purpose processor implemented by reading software code stored in memory.
  • the memory may be integrated with the processor or may be provided separately from the processor, which is not limited by this application.
  • the memory can be a non-transient processor, such as a read-only memory ROM, which can be integrated on the same chip as the processor, or can be separately provided on different chips.
  • This application describes the type of memory, and the relationship between the memory and the processor. There is no specific limitation on how the processor is configured.
  • the chip system can be a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), or a system on chip (SoC). It can also be a central processor (central processor unit, CPU), a network processor (network processor, NP), a digital signal processing circuit (digital signal processor, DSP), or a microcontroller (micro controller unit (MCU), or a programmable logic device (PLD) or other integrated chip.
  • FPGA field programmable gate array
  • ASIC application specific integrated circuit
  • SoC system on chip
  • CPU central processor unit
  • NP network processor
  • DSP digital signal processing circuit
  • MCU microcontroller
  • PLD programmable logic device
  • each step in the above method embodiment can be completed by an integrated logic circuit of hardware in the processor or instructions in the form of software.
  • the method steps disclosed in conjunction with the embodiments of this application can be directly implemented by a hardware processor, or executed by a combination of hardware and software modules in the processor.
  • Embodiments of the present application also provide a computer storage medium.
  • Computer instructions are stored in the computer storage medium. When the computer instructions are run on a computer, they cause the computer to execute the method described in the above method embodiment.
  • Embodiments of the present application provide a computer program product.
  • the computer program product includes: a computer program or instructions. When the computer program or instructions are run on a computer, the computer is caused to execute the method described in the above method embodiment.
  • the embodiment of the present application also provides a device.
  • This device may be a chip, a component or a module.
  • the device may include a connected processor and a memory.
  • the memory is used to store computer execution instructions. When the device is running, the processing The device can execute computer execution instructions stored in the memory, so that the device executes each of the above methods. Methods in Examples.
  • An embodiment of the present application also provides a communication system, including the electronic device and server introduced in the above embodiment.
  • the electronic equipment, servers, computer storage media, computer program products or chips, and communication systems provided in this embodiment are all used to execute the corresponding methods provided above. Therefore, the beneficial effects they can achieve can be referred to the above. The beneficial effects of the corresponding methods provided will not be described again here.
  • a unit described as a separate component may or may not be physically separate.
  • a component shown as a unit may be one physical unit or multiple physical units, that is, it may be located in one place, or it may be distributed to multiple different places. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.
  • each functional unit in each embodiment of the present application can be integrated into one processing unit, each unit can exist physically alone, or two or more units can be integrated into one unit.
  • the above integrated units can be implemented in the form of hardware or software functional units.
  • Integrated units may be stored in a readable storage medium if they are implemented in the form of software functional units and sold or used as independent products.
  • the technical solutions of the embodiments of the present application are essentially or contribute to the existing technology, or all or part of the technical solution can be embodied in the form of a software product, and the software product is stored in a storage medium , including several instructions to cause a device (which can be a microcontroller, a chip, etc.) or a processor to execute all or part of the steps of the methods of various embodiments of the present application.
  • the aforementioned storage media include: U disk, mobile hard disk, read only memory (ROM), random access memory (RAM), magnetic disk or optical disk and other media that can store program code.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Human Computer Interaction (AREA)
  • Stored Programmes (AREA)

Abstract

La présente demande a trait au domaine technique des dispositifs électroniques. L'invention concerne un procédé d'affichage et un dispositif électronique, lequel procédé peut permettre de nettoyer efficacement un processus d'application d'entretien, ce qui permet de résoudre divers problèmes d'un dispositif électronique, qui sont provoqués par l'entretien du processus d'application. Le procédé est appliqué à un dispositif électronique pourvu d'un écran d'affichage. Le procédé consiste à : recevoir une première opération d'un utilisateur ; en réponse à la première opération, acquérir des détails d'une application, les détails de l'application comprenant si l'application réside dans l'arrière-plan du dispositif électronique ; afficher les détails de l'application, les détails de l'application étant utilisés pour ordonner à l'utilisateur de décharger l'application ou de ne pas installer l'application, de façon à empêcher l'application de résider dans l'arrière-plan du dispositif électronique ; recevoir une seconde opération de l'utilisateur ; et en réponse à la seconde opération, décharger l'application.
PCT/CN2023/087335 2022-04-22 2023-04-10 Procédé d'affichage et dispositif électronique WO2023202406A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202210426387.1 2022-04-22
CN202210426387.1A CN116974434A (zh) 2022-04-22 2022-04-22 显示方法及电子设备

Publications (1)

Publication Number Publication Date
WO2023202406A1 true WO2023202406A1 (fr) 2023-10-26

Family

ID=88419088

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/087335 WO2023202406A1 (fr) 2022-04-22 2023-04-10 Procédé d'affichage et dispositif électronique

Country Status (2)

Country Link
CN (1) CN116974434A (fr)
WO (1) WO2023202406A1 (fr)

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140331119A1 (en) * 2013-05-06 2014-11-06 Mcafee, Inc. Indicating website reputations during user interactions
CN105094869A (zh) * 2014-05-14 2015-11-25 腾讯科技（深圳）有限公司 目标程序确定方法及装置
CN105335134A (zh) * 2014-06-30 2016-02-17 北京金山安全软件有限公司 处理app的cpu占用率异常的方法、装置及移动终端
CN111639333A (zh) * 2020-05-28 2020-09-08 维沃移动通信有限公司 信息管理方法、装置及电子设备
CN112051947A (zh) * 2020-09-02 2020-12-08 北京达佳互联信息技术有限公司 控件显示方法、装置及电子设备
CN113589990A (zh) * 2021-08-12 2021-11-02 Vidaa美国公司 一种显示设备的应用管理方法、显示设备及移动终端

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140331119A1 (en) * 2013-05-06 2014-11-06 Mcafee, Inc. Indicating website reputations during user interactions
CN105094869A (zh) * 2014-05-14 2015-11-25 腾讯科技（深圳）有限公司 目标程序确定方法及装置
CN105335134A (zh) * 2014-06-30 2016-02-17 北京金山安全软件有限公司 处理app的cpu占用率异常的方法、装置及移动终端
CN111639333A (zh) * 2020-05-28 2020-09-08 维沃移动通信有限公司 信息管理方法、装置及电子设备
CN112051947A (zh) * 2020-09-02 2020-12-08 北京达佳互联信息技术有限公司 控件显示方法、装置及电子设备
CN113589990A (zh) * 2021-08-12 2021-11-02 Vidaa美国公司 一种显示设备的应用管理方法、显示设备及移动终端

Also Published As

Publication number Publication date
CN116974434A (zh) 2023-10-31

Similar Documents

Publication Publication Date Title
US11803451B2 (en) Application exception recovery
CN113110941B (zh) 使用应用容器管理代码和依赖性数据的传递
US8813175B2 (en) Multimodal computing device
US10515056B2 (en) API for resource discovery and utilization
US11853820B2 (en) Cross-process communication method, apparatus, and device
WO2022199111A1 (fr) Procédé et appareil pour mettre en oeuvre des fonctions dans un programme d'application, dispositif électronique et support de stockage
US20200174823A1 (en) State management method and apparatus for virtual machine, and smart terminal thereof
CN109271211B (zh) 应用程序的分身方法、装置、设备和介质
US20180196584A1 (en) Execution of multiple applications on a device
CN110780930A (zh) 启动Android系统的方法、装置、电子设备及存储介质
CN116048628B (zh) 设备启动方法及电子设备
EP3134817A1 (fr) Support de dispositif mobile pour des capteurs dans des périphériques
US20230139886A1 (en) Device control method and device
WO2023202406A1 (fr) Procédé d'affichage et dispositif électronique
EP3853725A1 (fr) Expérience d'application connectée
KR20190098516A (ko) 어플리케이션과 관련된 데이터를 관리하기 위한 방법 및 그 전자 장치
CN113742716A (zh) 代码运行方法、装置、电子设备、存储介质和程序产品
CN116719556B (zh) 系统升级的方法和电子设备
WO2024032022A1 (fr) Procédé et dispositif de visualisation d'icône d'application
WO2023169212A1 (fr) Procédé d'identification de sdk dans une application, terminal et serveur
US20230216732A1 (en) Network Configuration Method and Device
WO2024083114A1 (fr) Procédé de distribution de logiciel, dispositif électronique et système
CN116643778B (zh) 一种应用程序优化方法及电子设备
WO2022143126A1 (fr) Procédé, appareil et dispositif d'analyse de sécurité d'application, et support de stockage
CN116719556A (zh) 系统升级的方法和电子设备

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23791061

Country of ref document: EP

Kind code of ref document: A1