CN118069263A

CN118069263A - Window control method and electronic device

Info

Publication number: CN118069263A
Application number: CN202211486270.9A
Authority: CN
Inventors: 袁中举; 闫永杰; 郭昌盛; 洪太亮
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2022-11-24
Filing date: 2022-11-24
Publication date: 2024-05-24
Also published as: WO2024109481A1

Abstract

The embodiment of the disclosure provides a window control method and electronic equipment. The method comprises the following steps: the device displays an interface of the first application, the device detects that the second application initiates a request for displaying a popup window, and the device displays a floating window related to the second application on the first application interface, wherein the floating window comprises a title bar, and the title bar comprises an identification of the second application. By implementing the embodiment of the disclosure, the system performance can be improved, the interference of malicious popup behaviors of the application to the user can be reduced, the identification of popup applications and the management and control of the application behaviors can be enhanced, the man-machine interaction performance can be enhanced, and the use experience of the user can be improved.

Description

Window control method and electronic device

Technical Field

The present disclosure relates to the field of computers, and more particularly, to a window control method and an electronic device.

Background

Malicious popups of non-user triggered systems or applications often occur on the terminal device. In some cases, the popup may be a non-foreground application behavior, but the application name is not displayed in the popup, hiding its identity, which may interfere with the user, possibly causing misleading the user to gain inadvisable rights. In other cases, the popup may be full screen or the return key is shielded in the popup, which can cause a significant disturbance to the user's use. Similar to the popup behavior that these users cannot recognize and manage, the user experience is poor.

Disclosure of Invention

The embodiment of the application provides a window control method and related electronic equipment, which are used for identifying and controlling malicious popup behaviors of an application.

In a first aspect of the application, there is provided a method comprising: the device displays an interface of the first application, the device detects that the second application initiates a request for displaying a popup window, and the device displays a floating window related to the second application on the interface of the first application, wherein the floating window comprises a title bar, and the title bar comprises an identification of the second application.

By implementing the method, the system performance can be improved, the interference of malicious popup behaviors of the application to the user can be reduced, the identification of popup applications and the management and control of the application behaviors can be enhanced, the man-machine interaction performance can be enhanced, and the use experience of the user can be improved.

With reference to the first aspect, in some embodiments, the identification of the second application includes application information related to the second application that includes one or more of: application name, application icon, application title, application description, or developer information. The information of the second applications facilitates the user to identify the applications corresponding to the floating window.

With reference to the first aspect, in some embodiments, the device detects an operation indicating to close the floating window, and the device removes the floating window. The floating window closing mode can avoid that some malicious windows close the channel in a hidden way, so that users are forced to respond to other requirements of the popup window, for example, the popup window cannot be closed, and advertisements are forced to be watched.

In combination with the first aspect, in some embodiments, the floating window includes a close control that is displayed on the right side of the title bar, indicating that the operation of closing the floating window is a click operation on the close control. The close control may also be located to the left of the title bar or in any area below the hover window, in the lower left corner, etc., as the embodiments are not limited in this regard.

With reference to the first aspect, in some embodiments, the first application is a lock screen application, and the operation of closing the floating window is indicated as a pressing operation acting on the power key. In some embodiments, closing the floating window may be triggered by hardware.

In combination with the first aspect, in some embodiments, the method further comprises requesting to display a second window that completely covers the interface for the request: in response to the request, the device converts the second window into a floating window, the size of the floating window being smaller than the size of the second window, the second window not including the title bar, the content in the floating window including the content in the second window. The size of the floating window displayed is smaller than the size of the requested popup window, less obscuring the interface of the first application, and the dragging movement is possible.

With reference to the first aspect, in some embodiments, the floating window includes a magnification control, the method further includes: the device detects an operation on the magnification control, and the device displays the magnified floating window, which is a full screen window. The reduced window or full screen window may be switched as desired.

With reference to the first aspect, in some embodiments, the enlarged floating window includes a zoom-out control, the method further comprising: the device detects an operation on the zoom-out control and the device zooms out the zoomed-in hover window. The reduced window or full screen window may be switched as desired.

In combination with the first aspect, in some embodiments, the floating window is a notification window that is displayed at a top or bottom of the interface, and is moved out of the interface if no operation instruction is received for more than a predetermined time. Converting the popup window into a lighter notification window can further reduce interference to the user.

In combination with the first aspect, in some embodiments, the first application is a lock screen application, the second application is a music application, song information and a play control are included in the floating window, and a title bar includes a name of the music application, an icon of the music application and a closing control.

With reference to the first aspect, in some embodiments, the first application is a foreground application, the second application is the same application as the first application, and the method further includes: after the device detects that the first application initiates a request to display a popup window, the device allows a floating window associated with the first application to be displayed on the interface. The popup of the foreground application may be preferentially responded to.

With reference to the first aspect, in some embodiments, the first application is a foreground application, and the second application is a background application, the method further includes: after the device detects that the second application initiates a request for displaying the popup window, the device judges whether the second application has a permission interface to display the floating window. If the second application has permission to display the floating window, the device allows the floating window associated with the second application to be displayed on the interface. If the second application does not have permission to display the floating window, the device denies the request to display the popup window. Whether to release the popup window of the background application needs to inquire whether the release condition is satisfied. The popup permission is set for the application, so that a user can conveniently control popup behaviors.

With reference to the first aspect, in some embodiments, the method further comprises: if the second application has the right to display the floating window, the device creates a carrier carrying the popup window. The device obtains application information of the second application. The device displays a floating window related to the second application based on the carrier, and the identification of the second application displayed in the floating window is from the acquired application information of the second application. Application information can be added to package the popup window, so that the popup window is convenient for a user to identify.

In combination with the first aspect, in some embodiments, the device hides the display popup if the second application has permission to display the floating window. The device creates a notification window, the device acquires application information of the second application, the device displays the notification window related to the second application, and the identifier of the second application displayed in the notification window comes from the acquired application information of the second application. The notification window is also a carrier for bearing the floating window, and the conversion of the popup window into the notification window can further reduce the interference to the user.

With reference to the first aspect, in some embodiments, the hidden display popup includes any one of: the popup window is set as a transparent window, the display color of the popup window is consistent with the background color of the interface, and the popup window is set to a predetermined size so as not to be recognized by a user.

With reference to the first aspect, in some embodiments, the rights are set by one or more of: permission of notification, permission of silent notification, permission of foreground notification, permission of background notification, permission of displaying full-screen window, permission of displaying notification window, and permission of displaying window on lock screen interface. By setting the popup right for the application, the popup behavior can be better controlled.

In combination with the first aspect, in some embodiments, the device may not display the title bar upon detecting that the requested popup may display an identification of the second application. In other embodiments, the device may display a title bar including the second application identification on the basis of the requested popup window displaying the identification of the second application, which may display repeated application information, such as displaying two-bar application identifications.

With reference to the first aspect, in some embodiments, the apparatus is any one of the following: cell phone, tablet computer, notebook computer, personal computer, smart watch, smart bracelet, smart television.

In a second aspect of the present application, there is provided a window control apparatus comprising: the display module is configured to display an interface of the first application, the detection module is configured to detect that the second application initiates a request for displaying a popup window, and the display module is further configured to display a floating window related to the second application on the interface of the first application, wherein the floating window comprises a title bar, and the title bar comprises an identification of the second application.

By means of the device, system performance can be improved, interference of malicious popup behaviors of an application to a user is reduced, recognition of popup applications and management and control of the application behaviors are enhanced, man-machine interaction performance is enhanced, and use experience of the user is improved.

With reference to the second aspect, in some embodiments, the identification of the second application includes application information related to the second application that includes one or more of: application name, application icon, application title, application description, or developer information. The information of the second applications facilitates the user to identify the applications corresponding to the floating window.

With reference to the second aspect, in some embodiments, the detection module is further configured to detect an operation indicating to close the floating window, and the window management module is configured to remove the floating window. The floating window closing mode can avoid that some malicious windows close the channel in a hidden way, so that users are forced to respond to other requirements of the popup window, for example, the popup window cannot be closed, and advertisements are forced to be watched.

In combination with the second aspect, in some embodiments, the floating window includes a close control that is displayed on the right side of the title bar, indicating that the operation of closing the floating window is a click operation on the close control. The close control may also be located to the left of the title bar or in any area below the hover window, in the lower left corner, etc., as the embodiments are not limited in this regard.

With reference to the second aspect, in some embodiments, the first application is a lock screen application, and the operation of closing the floating window is indicated as a pressing operation acting on the power key. In some embodiments, closing the floating window may be triggered by hardware.

In combination with the second aspect, in some embodiments, the apparatus further comprises a conversion module for converting the second window into a floating window in response to the request, the size of the floating window being smaller than the size of the second window, the second window not including the title bar, and the content in the floating window including the content in the second window. The size of the floating window displayed is smaller than the size of the requested popup window, less obscuring the interface of the first application, and the dragging movement is possible.

With reference to the second aspect, in some embodiments, the floating window includes an enlargement control, the detection module is further configured to detect an operation acting on the enlargement control, and the window management module is further configured to enlarge the floating window, where the enlarged floating window is a full-screen window. The reduced window or full screen window may be switched as desired.

With reference to the second aspect, in some embodiments, the enlarged floating window includes a zoom-out control, the detection module is further configured to detect an operation on the zoom-out control, and the window management module is further configured to zoom out the enlarged floating window. The reduced window or full screen window may be switched as desired.

In combination with the second aspect, in some embodiments, the floating window is a notification window that is displayed at a top or bottom of the interface, and that moves out of the interface if no operation instruction is received for more than a predetermined time. Converting the popup window into a lighter notification window can further reduce interference to the user.

In combination with the second aspect, in some embodiments, the first application is a lock screen application, the second application is a music application, song information and a play control are included in the floating window, and a title bar includes a name of the music application, an icon of the music application, and a close control.

With reference to the second aspect, in some embodiments, the first application is a foreground application, the second application is the same application as the first application, and after detecting that the first application initiates a request for displaying a popup window, the judging module is configured to allow a floating window related to the first application to be displayed on the interface. The popup of the foreground application may be preferentially responded to.

With reference to the second aspect, in some embodiments, the first application is a foreground application, the second application is a background application, and the determining module is further configured to determine whether the second application has a permission interface to display a floating window after the device detects that the second application initiates a request for displaying a popup window. The determination module is further configured to allow the floating window associated with the second application to be displayed on the interface if the second application has permission to display the floating window. If the second application does not have the authority to display the floating window, the judging module is further used for rejecting the request for displaying the popup window. Whether to release the popup window of the background application needs to inquire whether the release condition is satisfied. The popup permission is set for the application, so that a user can conveniently control popup behaviors.

With reference to the second aspect, in some embodiments, if the second application has permission to display the floating window, the creating module is configured to create a carrier carrying the popup window. The acquisition module is used for acquiring application information of the second application. The display module is further used for displaying a floating window related to the second application based on the carrier, and the identification of the second application displayed in the floating window is from the acquired application information of the second application. Application information can be added to package the popup window, so that the popup window is convenient for a user to identify.

With reference to the second aspect, in some embodiments, if the second application has permission to display the floating window, the window management module is further configured to hide the display popup. The creating module is used for creating a notification window, the acquiring module is used for acquiring application information of the second application, the display module is also used for displaying the notification window related to the second application, and the identification of the second application displayed in the notification window is from the acquired application information of the second application. The notification window is also a carrier for bearing the floating window, and the conversion of the popup window into the notification window can further reduce the interference to the user.

With reference to the second aspect, in some embodiments, the hidden display popup includes any one of: the popup window is set as a transparent window, the display color of the popup window is consistent with the background color of the interface, and the popup window is set to a predetermined size so as not to be recognized by a user.

With reference to the second aspect, in some embodiments, the rights are set by one or more of: permission of notification, permission of silent notification, permission of foreground notification, permission of background notification, permission of displaying full-screen window, permission of displaying notification window, and permission of displaying window on lock screen interface. By setting the popup right for the application, the popup behavior can be better controlled.

With reference to the second aspect, in some embodiments, the display module may not display the title bar when detecting that the requested popup may display the identity of the second application. In other embodiments, the display module may display a title bar including the second application identifier, possibly displaying repeated application information, such as displaying a two-bar application identifier, in addition to the requested popup window displaying the identifier of the second application.

With reference to the second aspect, in some embodiments, the apparatus comprises any one of the following: cell phone, tablet computer, notebook computer, personal computer, smart watch, smart bracelet, smart television.

In a third aspect of the present application, there is provided an electronic device comprising a memory having stored therein executable instructions for invoking the executable instructions to cause the electronic device to perform the following operations in accordance with the method of the first aspect or any embodiment thereof described above.

In a fourth aspect of the application, there is provided a computer readable storage medium storing computer executable instructions which when executed by a processor perform operations according to the method of the first aspect or any embodiment thereof.

In a fifth aspect of the application, there is provided a computer program product comprising computer executable instructions thereon which when executed implement operations according to the method of the first aspect or any embodiment thereof described above.

In a sixth aspect of the application, there is provided a chip or chip system comprising processing circuitry configured to implement operations according to the method of the first aspect or any embodiment thereof described above.

By implementing one or more aspects of the application, the system performance can be improved, the interference of malicious popup behaviors of the application on the user can be reduced, the identification of popup applications and the management and control of the application behaviors can be enhanced, the man-machine interaction performance can be enhanced, and the use experience of the user can be improved.

Drawings

The above and other features, advantages and aspects of embodiments of the present disclosure will become more apparent by reference to the following detailed description when taken in conjunction with the accompanying drawings. In the drawings, wherein like or similar reference numerals designate like or similar elements, and wherein:

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

fig. 1B is a schematic software architecture diagram of an electronic device according to an embodiment of the present application;

FIG. 2 illustrates a user interface schematic diagram according to some embodiments of the present disclosure;

FIG. 3A illustrates a user interface schematic diagram according to some embodiments of the present disclosure;

FIG. 3B illustrates a user interface schematic diagram according to some embodiments of the present disclosure;

FIG. 3C illustrates a user interface schematic diagram according to some embodiments of the present disclosure;

FIG. 4A illustrates a user interface schematic diagram according to some embodiments of the present disclosure;

FIG. 4B illustrates a user interface schematic diagram according to some embodiments of the present disclosure;

FIG. 5 illustrates a user interface schematic diagram according to some embodiments of the present disclosure;

FIG. 6A illustrates a user interface schematic diagram according to some embodiments of the present disclosure;

FIG. 6B illustrates a user interface schematic diagram according to some embodiments of the present disclosure;

FIG. 7 illustrates a user interface schematic diagram according to some embodiments of the present disclosure;

FIG. 8 illustrates a user interface schematic diagram according to some embodiments of the present disclosure;

FIG. 9 illustrates a window control logic flow diagram in accordance with some embodiments of the present disclosure;

FIG. 10 illustrates another window control logic flow diagram in accordance with some embodiments of the present disclosure;

FIG. 11 illustrates a flow chart of a window control method according to some embodiments of the present disclosure;

Fig. 12 illustrates a functional block diagram of an apparatus according to some embodiments of the present disclosure.

Detailed Description

Embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While certain embodiments of the present disclosure have been shown in the accompanying drawings, it is to be understood that the present disclosure may be embodied in various forms and should not be construed as limited to the embodiments set forth herein, but are provided to provide a more thorough and complete understanding of the present disclosure. It should be understood that the drawings and embodiments of the present disclosure are for illustration purposes only and are not intended to limit the scope of the present disclosure. Wherein, in the description of the embodiments of the present application, unless otherwise indicated, "/" means or, for example, a/B may represent a or B; the text "and/or" is merely an association relation describing the associated object, and indicates that three relations may exist, for example, a and/or B may indicate: a exists alone, A and B exist together, and B exists alone.

The terminology used in the following embodiments of the application is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. As used in the specification of the present application and the appended claims, the singular forms "a," "an," "the," and "the" are intended to include the plural forms as well, unless the context clearly indicates to the contrary. It should also be understood that the term "and/or" as used in this disclosure refers to and encompasses any or all possible combinations of one or more of the listed items. In describing embodiments of the present application, the term "comprising" and its like should be taken to be open-ended, i.e., including, but not limited to. The term "based on" should be understood as "based at least in part on". The term "one embodiment" or "the embodiment" should be understood as "at least one embodiment". It should be understood that the expressions "first", "second", "third", etc. are merely intended to indicate that the plurality of objects may be different, but do not exclude that the two objects are identical. The expressions "first", "second", "third", etc. should not be construed as limiting the embodiments in any way. The terms "first," "second," and the like, are used for descriptive purposes only and are not to be construed as implying or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defining "a first" or "a second" may explicitly or implicitly include one or more such feature, and in the description of embodiments of the application, unless otherwise indicated, the meaning of "a plurality" is two or more. Other explicit and implicit definitions are also possible below.

Reference in the specification to "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment may be included in at least one embodiment of the application. The appearances of such phrases in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. Those of skill in the art will explicitly and implicitly appreciate that the described embodiments of the application may be combined with other embodiments.

The term "User Interface (UI)" in the following embodiments of the present application is a media interface for interaction and information exchange between an Application (APP) or an Operating System (OS) and a user, which implements conversion between an internal form of information and a form acceptable to the user. The user interface is a source code written in a specific computer language such as java, extensible markup language (extensible markup language, XML) and the like, and the interface source code is analyzed and rendered on the electronic equipment to finally be presented as content which can be identified by a user. A commonly used presentation form of a user interface is a graphical user interface (graphic user interface, GUI), which refers to a graphically displayed user interface that is related to computer operations. It may be a visual interface element of text, icons, buttons, menus, tabs, text boxes, dialog boxes, status bars, navigation bars, widgets, etc., displayed in a display of the electronic device.

One or more embodiments of the present disclosure propose a window control method and an electronic device for identifying and controlling malicious popup behavior of an application. The method can present the basic information of the popup application to the user by processing and packaging the popup interface of the application, thereby facilitating the user to quickly identify the basic information of the popup application. The method can also hide the popup interface of the application and convert the popup interface into a notification form, thereby reducing the interference to the user.

By implementing the window control method and the electronic device in one or more embodiments of the present disclosure, system performance can be improved, interference of malicious popup behaviors of an application to a user can be reduced, recognition of popup applications and management and control of application behaviors can be enhanced, man-machine interaction performance can be enhanced, and use experience of the user can be improved.

An exemplary electronic device 100 provided by embodiments of the present application is described below. Fig. 1A is a schematic hardware structure of an electronic device 100 according to an embodiment of the present application. The exemplary electronic device 100 provided in the embodiments of the present application may be configured with a display device, and may be, but not limited to, a mobile phone, a notebook computer, a tablet computer (portable android device, PAD), a desktop computer, a laptop computer, a handheld computer, an augmented reality (augmented reality, AR) device, a Virtual Reality (VR) device, a personal computer (personal computer, PC), a mobile terminal device, etc., or may be a smart bracelet, a smart watch, an electronic photo frame, a smart television, a smart speaker, an artificial intelligence (ARTIFICIAL INTELLIGENCE, AI) device, a car machine (vehicle-mounted device), a game machine, a cloud host/cloud server, other smart wearable devices, etc., or may be an internet of things (internet of things, IOT) device or other types of electronic devices such as a smart water heater, a smart light, a smart air conditioner, a smart weight scale, etc., without any limitation to the device type.

It is to be understood that the structure illustrated in the present embodiment does not constitute a specific limitation on the electronic apparatus 100. In other embodiments of the application, electronic device 100 may include more or less components than illustrated, may add or subtract some hardware structures, or may combine some components, or may split some components, or may have a different arrangement of components. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

Referring to fig. 1A, the electronic device 100 may include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (universal serial bus, USB) interface 130, a charge management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, an earphone interface 170D, a sensor module 180, keys 190, a motor 191, an indicator 192, a camera 193, a display 194, a subscriber identity module (subscriber identification module, SIM) card interface 195, and the like. The sensor module 180 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 sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, an ambient light sensor 180L, a bone conduction sensor 180M, and the like.

The processor 110, which is typically used to control the overall operation of the electronic device 100, may include one or more processing units. For example: the processor 110 may include a central processor (central processing unit, CPU), an application processor (application processor, AP), a modem processor, a graphics processor (graphics processing unit, GPU), an image signal processor (IMAGE SIGNAL processor, ISP), a video processing unit (video processing unit, VPU), a controller, a memory, a video codec, a digital signal processor (DIGITAL SIGNAL processor, DSP), a baseband processor, and/or a neural-network processor (neural-network processing unit, NPU), etc. Wherein the different processing units may be separate devices or may be integrated in one or more processors. The controller can generate operation control signals according to the instruction operation codes and the time sequence signals to finish the control of instruction fetching and instruction execution. The digital signal processor is used for processing digital signals, and can process other digital signals besides digital image signals. For example, when the electronic device 100 selects a frequency bin, the digital signal processor is used to fourier transform the frequency bin energy, or the like. Video codecs are used to compress or decompress digital video. The electronic device 100 may support one or more video codecs. In this way, the electronic device 100 may play or record video in a variety of encoding formats, such as: dynamic picture experts group (moving picture experts group, MPEG) 1, MPEG2, MPEG3, MPEG4, etc. The NPU is a neural-network (NN) computing processor, and can rapidly process input information by referencing a biological neural network structure, for example, referencing a transmission mode between human brain neurons, and can also continuously perform self-learning. Applications such as intelligent cognition of electronic devices can be realized through the NPU, for example: image recognition, face recognition, speech recognition, text understanding, etc. A memory may also be provided in the processor 110 for storing instructions and data. In some embodiments, the memory in the processor 110 is a cache memory. The memory may hold instructions or data that the processor 110 has just used or recycled. If the processor 110 needs to reuse the instruction or data, it can be called directly from the memory. Repeated accesses are avoided and the latency of the processor 110 is reduced, thereby improving the efficiency of the system. In some embodiments of the application, a processor may be used to perform the methods and functions provided in any of the embodiments of the application.

In some embodiments, the processor 110 may include one or more interfaces. The interfaces may include an integrated circuit (inter-INTEGRATED CIRCUIT, I2C) interface, an integrated circuit built-in audio (inter-INTEGRATED CIRCUIT SOUND, I2S) interface, a pulse code modulation (pulse code modulation, PCM) interface, a universal asynchronous receiver transmitter (universal asynchronous receiver/transmitter, UART) interface, a mobile industry processor interface (mobile industry processor interface, MIPI), a general-purpose input/output (GPIO) interface, a subscriber identity module (subscriber identity module, SIM) interface, and/or a universal serial bus (universal serial bus, USB) interface, a serial peripheral interface (SERIAL PERIPHERAL INTERFACE, SPI) interface, and the like. It should be understood that the embodiments of the present application are not limited to the interfacing relationship between the modules, and are not limited to the structure of the electronic device 100. In some embodiments of the present application, electronic device 100 may employ different interfacing schemes, or a combination of interfacing schemes.

The charge management module 140 is configured to receive a charge input from a charger. The charger can be a wireless charger or a wired charger. In some wired charging embodiments, the charge management module 140 may receive a charging input of a wired charger through the USB interface 130. In some wireless charging embodiments, the charge management module 140 may receive wireless charging input through a wireless charging coil of the electronic device. The charging management module 140 may also supply power to the electronic device through the power management module 141 while charging the battery 142. The power management module 141 is used for connecting the battery 142, and the charge management module 140 and the processor 110. The power management module 141 receives input from the battery 142 and/or the charge management module 140 to power the processor 110, the internal memory 121, the display 194, the camera 193, the wireless communication module 160, and the like. The power management module 141 may also be configured to monitor battery capacity, battery cycle number, battery health (leakage, impedance) and other parameters. In other embodiments, the power management module 141 may also be provided in the processor 110. In other embodiments, the power management module 141 and the charge management module 140 may be disposed in the same device.

The wireless communication function of the electronic device 100 may be implemented by the antenna 1, the antenna 2, the mobile communication module 150, the wireless communication module 160, a modem processor, a baseband processor, and the like. The antennas 1 and 2 are used for transmitting and receiving electromagnetic wave signals. Each antenna in the electronic device 100 may be used to cover a single or multiple communication bands. Different antennas may also be multiplexed to improve the utilization of the antennas. For example: the antenna 1 may be multiplexed into a diversity antenna of a wireless local area network. In other embodiments, the antenna may be used in conjunction with a tuning switch. The mobile communication module 150 may provide a solution for wireless communication including second generation (2th generation,2G) network/third generation (3th generation,3G) network/fourth generation (4th generation,4G) network/fifth generation (5th generation,5G) network, etc., as applied on the electronic device 100. The mobile communication module 150 may include at least one filter, switch, power amplifier, low noise amplifier (low noise amplifier, LNA), etc. The mobile communication module 150 may receive electromagnetic waves from the antenna 1, perform processes such as filtering, amplifying, and the like on the received electromagnetic waves, and transmit the processed electromagnetic waves to the modem processor for demodulation. The mobile communication module 150 can amplify the signal modulated by the modem processor, and convert the signal into electromagnetic waves through the antenna 1 to radiate. In some embodiments, at least some of the functional modules of the mobile communication module 150 may be disposed in the processor 110. In some embodiments, at least some of the functional modules of the mobile communication module 150 may be provided in the same device as at least some of the modules of the processor 110. The modem processor may include a modulator and a demodulator. The modulator is used for modulating the low-frequency baseband signal to be transmitted into a medium-high frequency signal. The demodulator is used for demodulating the received electromagnetic wave signal into a low-frequency baseband signal. The demodulator then transmits the demodulated low frequency baseband signal to the baseband processor for processing. The low frequency baseband signal is processed by the baseband processor and then transferred to the application processor. The application processor outputs sound signals through an audio device (not limited to the speaker 170A, the receiver 170B, etc.), or displays images or video through the display screen 194. In some embodiments, the modem processor may be a stand-alone device. In other embodiments, the modem processor may be provided in the same device as the mobile communication module 150 or other functional module, independent of the processor 110.

The wireless communication module 160 may provide information that may be used on the electronic device 100 including wireless local area networks (wireless local area networks, WLAN) (e.g., wireless fidelity (WIRELESS FIDELITY, wi-Fi) networks), bluetooth (BT), global navigation satellite systems (global navigation SATELLITE SYSTEM, GNSS), frequency modulation (frequency modulation, FM), short range wireless communication technology (NEAR FIELD communication, NFC), infrared (IR), and the like. The wireless communication module 160 may be one or more devices that integrate at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via the antenna 2, modulates the electromagnetic wave signals, filters the electromagnetic wave signals, and transmits the processed signals to the processor 110. The wireless communication module 160 may also receive a signal to be transmitted from the processor 110, frequency modulate it, amplify it, and convert it to electromagnetic waves for radiation via the antenna 2. In some embodiments, antenna 1 and mobile communication module 150 of electronic device 100 are coupled, and antenna 2 and wireless communication module 160 are coupled, such that electronic device 100 may communicate with a network and other devices through wireless communication techniques. The wireless communication techniques may include the Global System for Mobile communications (global system for mobile communications, GSM), general packet radio service (GENERAL PACKET radio service, GPRS), code division multiple access (code division multiple access, CDMA), wideband code division multiple access (wideband code division multiple access, WCDMA), time division code division multiple access (time-division code division multiple access, TD-SCDMA), long term evolution (long term evolution, LTE), BT, GNSS, WLAN, NFC, FM, and/or IR techniques, among others. GNSS may include global satellite positioning systems (global positioning system, GPS), global navigation satellite systems (global navigation SATELLITE SYSTEM, GLONASS), beidou satellite navigation systems (beidou navigation SATELLITE SYSTEM, BDS), quasi zenith satellite systems (quasi-zenith SATELLITE SYSTEM, QZSS) and/or satellite based augmentation systems (SATELLITE BASED AUGMENTATION SYSTEMS, SBAS).

The electronic device 100 may implement display functions through a GPU, a display screen 194, an application processor, and the like. The GPU is a microprocessor for image processing, and is connected to the display 194 and the application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. Processor 110 may include one or more GPUs that execute program instructions to generate or change display information. The display screen 194 is used to display images, videos, and the like. The display 194 includes a display panel. The display panel may employ a Liquid Crystal Display (LCD) CRYSTAL DISPLAY, an organic light-emitting diode (OLED), an active-matrix organic LIGHT EMITTING diode (AMOLED), a flexible light-emitting diode (FLED), miniled, microLed, micro-oLed, a quantum dot LIGHT EMITTING diode (QLED), or the like. In some embodiments, the electronic device 100 may include 1 or N display screens 194, N being a positive integer greater than 1.

The camera 193 is used to capture still images or video. The object generates an optical image through the lens and projects the optical image onto the photosensitive element. The photosensitive element may be a charge coupled device (charge coupled device, CCD) or a Complementary Metal Oxide Semiconductor (CMOS) phototransistor. The photosensitive element converts the optical signal into an electrical signal, which is then transferred to the ISP to be converted into a digital image signal. The ISP outputs the digital image signal to the DSP for processing. The DSP converts the digital image signal into an image signal in a standard RGB, YUV, or the like format. In some embodiments, electronic device 100 may include 1 or N cameras 193, N being a positive integer greater than 1. The cameras 193 may include, but are not limited to, conventional color cameras (RGB cameras), depth cameras (RGB DEPTH CAMERA), dynamic vision sensor (dynamic vision sensor, DVS) cameras, and the like. In some embodiments, camera 193 may be a depth camera. The depth camera can collect the space information of the real environment. In some embodiments, the camera 193 may acquire images of the user's hand or body, and the processor 110 may be configured to analyze the images acquired by the camera 193 to identify the user's input hand or body movements. For example, the hand motion of the user can be recognized by the camera 193 to realize the gesture control of the user.

The internal memory 121 may be used to store computer executable program code that includes instructions. The processor 110 executes various functional applications of the electronic device and data processing by executing instructions stored in the internal memory 121. In some embodiments of the present application, the memory 121 may be used to store an implementation program of the method provided by one or more embodiments of the present application on the electronic device 100 side. The internal memory 121 may include a storage program area and a storage data area. The storage program area may store an application program (such as a sound playing function, an image playing function, etc.) required for at least one function of the operating system, etc. The storage data area may store data created during use of the electronic device (e.g., audio data, phonebook, etc.), and so forth. In some embodiments of the present application, internal memory 121 may be used to store an application program for one or more applications, the application program comprising instructions. The application, when executed by the processor 110, causes the electronic device 100 to generate content for presentation to a user. By way of example, the application may include an application for managing the electronic device 100, such as a gaming application, a conferencing application, a video application, a desktop application, or other application, and so forth. The internal memory 121 may include one or more random access memories (random access memory, RAM) and one or more non-volatile memories (NVM). The random access memory has the characteristics of high reading/writing speed and volatility. Volatile refers to the fact that, once powered down, the data stored in RAM will disappear. In general, the static power consumption of the random access memory is extremely low, and the operation power consumption is relatively large. The data in the RAM is memory data, and can be read at any time, and the power failure disappears. The nonvolatile memory has characteristics of nonvolatile and stable storage data. The random access memory may be read directly from and written to by the processor 110, may be used to store executable programs (e.g., machine instructions) for an operating system or other on-the-fly programs, may also be used to store data for users and applications, and the like. The nonvolatile memory may store executable programs, store data of users and applications, and the like, and may be loaded into the random access memory in advance for the processor 110 to directly read and write. The external memory interface 120 may be used to connect external non-volatile memory to enable expansion of the memory capabilities of the electronic device. The external nonvolatile memory communicates with the processor 110 through the external memory interface 120 to implement a data storage function. For example, files such as music and video are stored in an external nonvolatile memory.

The electronic device 100 may implement audio functions through an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, an earphone interface 170D, an application processor, and the like. Such as music playing, recording, etc. The audio module 170 is used to convert digital audio information into an analog audio signal output and also to convert an analog audio input into a digital audio signal. The audio module 170 may also be used to encode and decode audio signals. In some embodiments, the audio module 170 may be disposed in the processor 110, or a portion of the functional modules of the audio module 170 may be disposed in the processor 110. The speaker 170A, also referred to as a "horn," is used to convert audio electrical signals into sound signals. The electronic device may listen to music, or to hands-free conversations, through speaker 170A. A receiver 170B, also referred to as a "earpiece", is used to convert the audio electrical signal into a sound signal. When the electronic device picks up a phone call or voice message, the voice can be picked up by placing the receiver 170B close to the human ear. Microphone 170C, also referred to as a "microphone" or "microphone", is used to convert sound signals into electrical signals. When making a call or transmitting voice information, the user can sound near the microphone 170C through the mouth, inputting a sound signal to the microphone 170C. The electronic device may be provided with at least one microphone 170C. In other embodiments, the electronic device may be provided with two microphones 170C, and may implement a noise reduction function in addition to collecting sound signals. In other embodiments, the electronic device may also be provided with three, four, or more microphones 170C to enable collection of sound signals, noise reduction, identification of sound sources, directional recording functions, etc. The earphone interface 170D is used to connect a wired earphone. The headset interface 170D may be a USB interface 130 or a 3.5mm open mobile electronic device platform (open mobile terminal platform, OMTP) standard interface, a american cellular telecommunications industry association (cellular telecommunications industry association of the USA, CTIA) standard interface.

The electronic device 100 may include one or more keys 190, and the keys 190 may control the electronic device 100 to provide a user with access to functions on the electronic device 100. The key 190 may be in the form of a mechanical case such as a button, switch, dial, etc., or may be a touch or near-touch sensing device (e.g., a touch sensor). The electronic device 100 may receive key inputs, generating key signal inputs related to user settings and function controls of the electronic device 100. The keys 190 may include a power on key, a volume key, etc. The motor 191 may generate a vibration cue. The motor 191 may be used for incoming call vibration alerting as well as for touch vibration feedback. For example, touch operations acting on different applications (e.g., photographing, audio playing, etc.) may correspond to different vibration feedback effects. The motor 191 may also correspond to different vibration feedback effects by touching operations on different areas of the electronic device 100. Different application scenarios (such as time reminding, receiving information, alarm clock, game, etc.) can also correspond to different vibration feedback effects. The touch vibration feedback effect may also support customization. The indicator 192 may be an indicator light, which may be used to indicate a state of charge, a change in charge, a message, a notification, etc. The electronic device 100 may also include other input-output interfaces through which other means may be connected to the electronic device 100. The components may include, for example, audio/video jacks, data connectors, and the like.

The electronic device 100 is equipped with one or more sensors including, but not limited to, a pressure sensor 180A, a gyroscope sensor 180B, an air pressure sensor 180C, a magnetic sensor 180D, an acceleration sensor 180E, a distance sensor 180F, a proximity sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, an ambient light sensor 180L, a bone conduction sensor 180M, and the like. The pressure sensor 180A is used to sense a pressure signal, and may convert the pressure signal into an electrical signal. In some embodiments, the pressure sensor 180A may be disposed on the display screen 194. The pressure sensor 180A is of various types, such as a resistive pressure sensor, an inductive pressure sensor, a capacitive pressure sensor, and the like. The capacitive pressure sensor may be a capacitive pressure sensor comprising at least two parallel plates with conductive material. The capacitance between the electrodes changes when a force is applied to the pressure sensor 180A. The electronic device 100 determines the strength of the pressure from the change in capacitance. When a touch operation is applied to the display screen 194, the electronic apparatus 100 detects the touch operation intensity according to the pressure sensor 180A. The electronic device 100 may also calculate the location of the touch based on the detection signal of the pressure sensor 180A. In some embodiments, touch operations that act on the same touch location, but at different touch operation strengths, may correspond to different operation instructions. For example: and executing an instruction for checking the short message when the touch operation with the touch operation intensity smaller than the first pressure threshold acts on the short message application icon. And executing an instruction for newly creating the short message when the touch operation with the touch operation intensity being greater than or equal to the first pressure threshold acts on the short message application icon. In some embodiments, touch operations that act on the same touch location, but for different lengths of time, may correspond to different operation instructions. For example: when a touch operation with a touch operation time length smaller than the first time threshold acts on the pressure sensor 180A, an instruction of confirmation is executed. When a touch operation with a touch operation time length greater than or equal to the first time threshold acts on the pressure sensor 180A, an instruction of power on/off is executed. The gyro sensor 180B may be used to determine a motion gesture of the electronic device 100. In some embodiments, the angular velocity of the electronic device about three axes (i.e., x, y, and z axes) may be determined by the gyro sensor 180B. The gyro sensor 180B may be used for photographing anti-shake. For example, when the shutter is pressed, the gyro sensor 180B detects the shake angle of the electronic device, calculates the distance to be compensated by the lens module according to the angle, and makes the lens counteract the shake of the electronic device through the reverse motion, thereby realizing anti-shake. The gyro sensor 180B may also be used for navigating, somatosensory game scenes. In some embodiments, electronic device 100 may confirm the instruction to switch the previous/next display option through gyroscopic sensor 180B. The air pressure sensor 180C is used to measure air pressure. In some embodiments, electronic device 100 calculates altitude from barometric pressure values measured by barometric pressure sensor 180C, aiding in positioning and navigation. The magnetic sensor 180D includes a hall sensor. The electronic device 100 may detect the opening and closing of the flip cover using the magnetic sensor 180D. In some embodiments, when the electronic device 100 is a flip machine, the opening and closing of the flip can be detected from the magnetic sensor 180D. And then according to the detected opening and closing state of the leather sheath or the opening and closing state of the flip, the characteristics of automatic unlocking of the flip and the like are set. The acceleration sensor 180E may detect the magnitude of acceleration of the electronic device 100 in various directions (typically three axes). The magnitude and direction of gravity may be detected when the electronic device 100 is stationary. The electronic equipment gesture recognition method can also be used for recognizing the gesture of the electronic equipment, and is applied to horizontal and vertical screen switching, pedometers and other applications. In some embodiments, the electronic device 100 may confirm the instruction to switch the previous/next display option through the acceleration sensor 180E. A distance sensor 180F for measuring a distance. The electronic device 100 may measure the distance by infrared or laser. In some embodiments, the electronic device 100 may range using the distance sensor 180F to achieve quick focus. The proximity light sensor 180G may include, for example, a Light Emitting Diode (LED) and a light detector, such as a photodiode. The light emitting diode may be an infrared light emitting diode. The electronic device 100 emits infrared light outward through the light emitting diode. The electronic device 100 detects infrared reflected light from nearby objects using a photodiode. When sufficient reflected light is detected, it may be determined that there is an object in the vicinity of the electronic device 100. When insufficient reflected light is detected, the electronic device 100 may determine that there is no object nearby. The electronic device 100 can detect that the user holds the electronic device 100 close to the ear by using the proximity light sensor 180G, so as to automatically extinguish the screen for the purpose of saving power. The proximity light sensor 180G may also be used in holster mode, pocket mode to automatically unlock and lock the screen. The ambient light sensor 180L is used to sense ambient light level. The electronic device 100 may adaptively adjust the brightness of the display 194 based on the perceived ambient light level. The ambient light sensor 180L may also be used to automatically adjust white balance when taking a photograph. Ambient light sensor 180L may also cooperate with proximity light sensor 180G to detect whether electronic device 100 is in a pocket to prevent false touches. The fingerprint sensor 180H is used to collect a fingerprint. The electronic device 100 may utilize the collected fingerprint feature to unlock the fingerprint, access the application lock, photograph the fingerprint, answer the incoming call, etc. The temperature sensor 180J is for detecting temperature. In some embodiments, the electronic device 100 performs a temperature processing strategy using the temperature detected by the temperature sensor 180J. For example, when the temperature reported by temperature sensor 180J exceeds a threshold, the electronics perform a reduction in performance of a processor located near temperature sensor 180J in order to reduce power consumption to implement thermal protection. In other embodiments, when the temperature is below another threshold, the electronic device 100 heats the battery 142 to avoid the low temperature causing the electronic device 100 to be abnormally shut down. In other embodiments, when the temperature is below a further threshold, the electronic device 100 performs boosting of the output voltage of the battery 142 to avoid abnormal shutdown caused by low temperatures. The touch sensor 180K, also referred to as a "touch device". The touch sensor 180K may be disposed on the display screen 194, and the touch sensor 180K and the display screen 194 form a touch screen, which is also called a "touch screen". The touch sensor 180K is for detecting a touch operation acting thereon or thereabout. The touch sensor may communicate the detected touch operation to the application processor to determine the touch event type. Visual output related to touch operations may be provided through the display 194. In other embodiments, the touch sensor 180K may also be disposed on the surface of the electronic device 100 at a different location than the display 194. The bone conduction sensor 180M may acquire a vibration signal. In some embodiments, bone conduction sensor 180M may acquire a vibration signal of a human vocal tract vibrating bone pieces. The bone conduction sensor 180M may also contact the pulse of the human body to receive the blood pressure pulsation signal. In some embodiments, bone conduction sensor 180M may also be provided in a headset, in combination with an osteoinductive headset. The audio module 170 may analyze the voice signal based on the vibration signal of the sound portion vibration bone block obtained by the bone conduction sensor 180M, so as to implement a voice function. The application processor may analyze the heart rate information based on the blood pressure beat signal acquired by the bone conduction sensor 180M, so as to implement a heart rate detection function.

The SIM card interface 195 is used to connect a SIM card. The SIM card may be inserted into the SIM card interface 195, or removed from the SIM card interface 195 to enable contact and separation with the electronic device 100. The electronic device 100 may support 1 or N SIM card interfaces, N being a positive integer greater than 1. The SIM card interface 195 may support Nano SIM cards, micro SIM cards, and the like. The same SIM card interface 195 may be used to insert multiple cards simultaneously. The types of the plurality of cards may be the same or different. The SIM card interface 195 may also be compatible with different types of SIM cards. The SIM card interface 195 may also be compatible with external memory cards. The electronic device 100 interacts with the network through the SIM card to realize functions such as communication and data communication. In some embodiments, the electronic device 100 employs esims, i.e.: an embedded SIM card. The eSIM card can be embedded in the electronic device 100 and cannot be separated from the electronic device 100.

The software system of the electronic device 100 may employ a layered architecture, an event driven architecture, a microkernel architecture, a microservice architecture, or a cloud architecture. The embodiment of the present application exemplifies a system of a hierarchical architecture, and exemplifies a software structure of the electronic device 100.

Fig. 1B is a software block diagram of an electronic device 100 according to an embodiment of the application. The layered architecture divides the software into several layers, each with distinct roles and branches. The layers communicate with each other through a software interface. In some embodiments, the system may be divided into four layers, from top to bottom, an application layer, an application framework layer, runtime (runtime) and system libraries, and a kernel layer, respectively.

The application layer may include a series of application packages. As shown in fig. 1B, the application package may include applications for cameras, gallery, calendar, talk, map, navigation, WLAN, bluetooth, music, video, settings, etc. Wherein, the authority of the application can be set in the setting application. The application framework layer provides an application programming interface (application programming interface, API) and programming framework for the application of the application layer. The application framework layer includes a number of predefined functions.

As shown in FIG. 1B, the application framework layer may include a window manager, a content provider, a view system, a telephony manager, a resource manager, a notification manager, and the like. The window manager is used for managing window programs. The window manager can acquire the size of the display screen, judge whether a status bar exists, lock the screen, intercept the screen and the like. The content provider is used to store and retrieve data and make such data accessible to applications. Such data may include video, images, audio, calls made and received, browsing history and bookmarks, phonebooks, etc. The view system includes visual controls, such as controls to display text, controls to display pictures, and the like. The view system may be used to build applications. The display interface may be composed of one or more views. For example, a display interface including a text message notification icon may include a view displaying text and a view displaying a picture. The telephony manager is used to provide communication functions. Such as the management of call status (including on, hung-up, etc.). The resource manager provides various resources for the application program, such as localization strings, icons, pictures, layout files, video files, and the like. The notification manager allows the application to display notification information in a status bar, can be used to communicate notification type messages, can automatically disappear after a short dwell, and does not require user interaction. Such as notification manager is used to inform that the download is complete, message alerts, etc. The notification manager may also be a notification in the form of a chart or scroll bar text that appears on the system top status bar, such as a notification of a background running application, or a notification that appears on the screen in the form of a dialog window. For example, a text message is prompted in a status bar, a prompt tone is emitted, the electronic device vibrates, and an indicator light blinks, etc.

The runtime includes a core library and a virtual machine. The runtime is responsible for scheduling and management of the system. The core library consists of two parts: one part is a function which needs to be called by java language, and the other part is a core library of the system. The application layer and the application framework layer run in a virtual machine. The virtual machine executes java files of the application program layer and the application program framework layer as binary files. The virtual machine is used for executing the functions of object life cycle management, stack management, thread management, security and exception management, garbage collection and the like.

The system library may include a plurality of functional modules. For example: surface manager (surface manager), media Libraries (Media Libraries), three-dimensional graphics processing Libraries (e.g., openGL ES), 2D graphics engines (e.g., SGL), etc. The surface manager is used to manage the display subsystem and provides a fusion of 2D and 3D layers for multiple applications. Media libraries support a variety of commonly used audio, video format playback and recording, still image files, and the like. The media library may support a variety of audio video encoding formats, such as: MPEG4, h.264, MP3, AAC, AMR, JPG, PNG, etc. The three-dimensional graphic processing library is used for realizing three-dimensional graphic drawing, image rendering, synthesis, layer processing and the like. The 2D graphics engine is a drawing engine for 2D drawing.

The kernel layer is a layer between hardware and software. The inner core layer at least comprises a display driver, a camera driver, an audio driver and a sensor driver. The workflow of the electronic device 100 in combination with the software and hardware is illustrated in connection with initiating a photo scene. When touch sensor 180K receives a touch operation, a corresponding hardware interrupt is issued to the kernel layer. The kernel layer processes the touch operation into the original input event (including information such as touch coordinates, time stamp of touch operation, etc.). The original input event is stored at the kernel layer. The application framework layer acquires an original input event from the kernel layer, and identifies a control corresponding to the input event. Taking the touch operation as a touch click operation, taking a control corresponding to the click operation as an example of a control of a camera application icon, the camera application calls an interface of an application framework layer, starts the camera application, further starts a camera driver by calling a kernel layer, and captures a still image or video by the camera 193.

The above description of the software architecture of the electronic device 100 is merely an example, and it should be understood that the software architecture illustrated in the embodiments of the present application is not limited to the specific embodiments of the present application. In other embodiments of the application, the software architecture of the electronic device 100 may include more or fewer modules than shown, or may combine certain modules, or split certain modules, or may be arranged in a different architecture. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

The following describes aspects of the application in connection with a related exemplary user interface provided in connection with some embodiments.

The user interface in the following embodiments provided in the present application may be described using the electronic device 100 as a mobile phone as an example. It is to be understood that the embodiments described by taking the mobile phone as an example in the present application do not limit other embodiments, and the device type of the electronic device 100 may be other devices, and all the schemes for implementing the inventive concept are within the scope of the present application. It will be appreciated that the various user interfaces described in the following embodiments of the application are merely exemplary interfaces and are not limiting of other embodiments of the application. In other embodiments, different interface layouts may be adopted in the user interface, more or fewer controls may be included, other functional options may be added or reduced, and the following example interfaces may also be migrated to be used on other types of devices, so long as the technical solutions based on the same inventive concept provided by the present application are all within the scope of protection of the present application.

Fig. 2 shows a pop-up scenario occurring on the electronic device 100. Referring to the illustrative interface 200 shown in FIG. 2, interface 210 is a display interface for a foreground application "sports health". In some cases, a popup may appear at the runtime of the foreground application, such as the popup shown in interface 220, including the request content "request for position rights" and the "reject" and "allow" controls. The popup would overlay the display over interface 210, which in some cases may be a full screen interface, and the return key is shielded in the popup, forcing the user to have to deal with the popup immediately, which can interfere with the user's use of the foreground application. In some cases, as shown in interface 220, application information for the popup is not displayed in the popup, and it is difficult for the user to identify what application the current popup request is for. For example, for malicious popup behavior of a background application, the identity of the user may be deliberately hidden when popup, which may mislead the user to misuse that the popup request was initiated by the foreground application, thereby allowing rights that the background application should not obtain. For example, when running the foreground application "sports health", the pop-up interface 220 that appears is actually launched by the background application "browser", but because the background application "browser" hides its identity and does not display its name on the pop-up interface, the user may misunderstand that it is the foreground application "sports health" that is requesting to obtain location permissions, and typically the user will allow the "sports health" to obtain location permissions in order to count running distance, and thus the user may have selected "allow" to let the background application "browser" obtain location permissions by misguiding the user.

Embodiments in the present application propose solutions for window control for identifying and controlling the pop-up behavior of an application. In some embodiments, the basic information of the popup application can be presented to the user by processing and packaging the popup interface of the application, so that the user can conveniently and quickly identify the basic information of the popup application. In some embodiments, it may be scaled to a small window for a full screen popup window, see fig. 3A, 3C. In other embodiments, the application's popup interface may also be hidden and converted to notification form, reducing interference to the user, see fig. 4A or 4B.

When running the foreground application "sports health", the background application "browser" initiates a popup request. The system can inquire the basic information of the background application and judge whether the background application has the popup window authority, if so, the system allows the background application to popup window, but performs interface conversion on a popup window display interface according to the basic information of the application. In some embodiments, a full screen popup may be scaled to a widget, referring to the schematic interface 300 shown in FIG. 3A, a popup interface 320 is displayed on a foreground application "sports health" interface 310, the popup interface 320 being a popup launched by a background application "browser", the popup interface 320 being a scaled-down window with respect to the popup interface 220 with a title bar 330. The popup interface 320 includes a title bar 330 in addition to the request content "request to obtain location rights," and "reject" and "allow" controls. The title bar 330 may include a zoom-in control 332, a close control 334, and application information 336. Magnification control 332 may be used to zoom in on reduced popup interface 320 to a full screen popup interface 350, as shown in FIG. 3B. The close control 334 is used to close the pop-up window, providing the user with the option of quickly exiting the pop-up window. The application information 336 may display application information such as application names (e.g., "browser"), application icons, etc., which is obtained by analyzing application information identifiers (e.g., package names, requested class names), and the display application information 336 may enable a user to quickly understand the source of the popup behavior, so as to avoid misleading the user to cheat rights by a malicious popup. In some embodiments, the pop-up interface 320 may be moved to other locations in response to a user's drag operation.

The title bar shown in the drawings in the embodiments of the present application is merely an example, and in other embodiments, the title bar may be in other forms, which is not limited in this embodiment. For example, the title bar may be a transparent fusion over the original popup, not occluding the original popup content, not increasing the window space much, or not in the form of a title bar, but rather a base transparent application information control and a closing control suspended over the original popup. The embodiment of the application does not limit the expression form of the window, and can express the application identifier.

Further, in some embodiments, the electronic device 100 may not add an application identifier, such as a title bar, when detecting that a popup requested by a background application may display an identifier of the application for user identification, avoiding repeated display. In other embodiments, the electronic device 100 may further display a title bar including the application identifier based on the application identifier displayed by the popup requested by the background application, which may display partially repeated application information, for example, two columns of title bars with the application identifier are displayed in the displayed window, one is the popup requested by itself, the other is the electronic device added on the popup basis, and typically, the title bar on the outermost layer is the title bar added by the system to the popup again.

When the electronic device 100 detects that the zoom-in control 332 is clicked, the interface 340 shown in fig. 3B may be displayed, with the pop-up interface 320 zoomed in to a full screen pop-up interface 350, completely overlaying the foreground application interface 310. Included in the popup interface 350 are request content "request to get position rights", "reject" control and "allow" control, and a title bar 330. A shrink control 338, a close control 334, and application information 336 may be included in the title bar 330. The zoom-out control 338 may be used to trigger zooming out of the full screen popup interface 350 to the popup interface 320. In some embodiments, the electronic device 100 also supports thumbnail windows displaying multiple popup windows on the interface, and these windows may be dragged.

In some embodiments, the scheme of converting the popup window can be applied not only when a third party application runs in the foreground, but also when a desktop application and a screen locking application run, and the embodiment of the application does not limit the application type applicable to the technical scheme. For the case of processing popup under the desktop application, referring to the schematic interface 360 shown in fig. 3C, the mobile phone displays the desktop application interface 370, after receiving the popup request of the browser application, the mobile phone determines whether there is authority to display the popup on the desktop, if there is authority, a window carrier carrying the original popup content can be created, and then after the application information is acquired, a floating window 380 with the browser application identifier can be displayed. In addition to the request content "request to get position rights" and the "reject" and "allow" controls, title bar 390 and close control 394 are added to the floating window 380, including the original popup. A magnification control 392 and application information 396 may be included in the title bar 390. Magnification control 392 may be used to magnify the scaled-down popup window 380 into a full-screen popup window. The close control 394 is used to close the popup window, and provides the user with an option of quickly exiting the popup window, and the close control 394 is located in the lower area of the floating window 380, and may be located at any position in other embodiments, and the embodiments of the present application do not limit the presentation forms, positions, etc. of the individual controls, title bars, etc. The application information 396 can display application names (such as a browser), application icons, developers, application descriptions and other application information, which is obtained by analyzing application information identifiers (such as package names and requested class names), and the display application information 396 can enable a user to quickly know the source of popup behaviors and avoid misleading of a malicious popup to cheat the authority of the user. In some embodiments, the floating window 380 may be moved to other positions in response to a drag operation by a user. In some embodiments, a plurality of such floating windows may be displayed on desktop application interface 370.

In other embodiments, the application's popup interface may also be hidden and converted to notification form to reduce interference to the user, referring to the illustrative interface 400 shown in FIG. 4A. When the electronic device 100 detects a pop-up request of a background application "browser", a pop-up interface that should be displayed is hidden, and then an application information identifier, such as a package name, a class name of the request, etc., is obtained, and application information that needs to be displayed, including an application name, an icon, a title, application description information, developer information, etc., is resolved. The manner of hiding the popup window interface may be various, and the embodiment is not limited thereto, for example, the window may be set to be transparent, and further, for example, the window may be set to be 1 pixel size unrecognizable by naked eyes, and the like. The electronic device 100 may convert the pop-up interface into a form of a notification message to alert the user, for example, by displaying a hovering notification banner 420 over the foreground interface 410, where the notification banner 420 may include a title bar 422 and a content bar 424, and the content bar 424 may display a summary of the requesting content "request to get location rights", "reject" control, and "allow" control. Application information resulting from parsing the "browser" application, such as "browser" application name and application icon, and closing controls, may be included in the title bar 422. The notification banner 420 occupies a small area and typically remains displayed for a few seconds and then automatically exits the foreground display interface, such as being placed in a notification bar. If the user needs to view the pop-up content, the notification banner 420 may be clicked on, a similar pop-up interface as pop-up interface 320 or pop-up interface 350 may be displayed, and if the user does not want to process the pop-up request, the notification may be ignored. The method for processing the popup window can not interrupt the use of the foreground application, does not need users to immediately process the popup window request, and reduces the interference to the users.

Likewise, the scheme for converting the popup window into the notification can be applied to not only the operation of a third party application in the foreground, but also the operation of a desktop application and a screen locking application, and the embodiment of the application does not limit the application type applicable to the technical scheme. For the case of processing popup under the desktop application, referring to the schematic interface 430 shown in fig. 4B, the mobile phone displays the desktop application interface 440, after receiving the popup request of the browser application, the mobile phone determines whether there is authority to display the popup on the desktop, if there is authority, a window carrier carrying the content of the original popup, that is, a notification window can be created, and after acquiring the application information, the notification window 450 with the browser application identifier can be displayed. The notification window 450 may include a title bar 452 and a content bar 454, where the content bar 454 may generally display the request content "request for acquisition location rights", "reject" control, and "allow" control. Application information resulting from parsing the "browser" application, such as "browser" application name and application icon, and closing controls, may be included in the title bar 452. The notification window 450 occupies a small area, typically remains displayed for a few seconds, and then automatically exits the currently displayed interface, e.g., is placed in a notification bar. If the user needs to view the pop-up content, he can click on the notification window 450 and display an enlarged pop-up interface in which more detailed content is displayed. The notification may be ignored if the user does not want to process the pop-up request. The method for processing the popup window can not interrupt the use of the current application, does not need users to immediately process the popup window request, and reduces the interference to the users.

Not limited to the above-described narrowing of the pop-up window and notification banner, in other embodiments, the pop-up window may also be converted into other types of messaging, such as desktop icons, status bar icon presentations, etc., which are intended to reduce the user's interference from the pop-up window.

Fig. 5 illustrates another floating window scenario for a lock screen interface that occurs on electronic device 100. Referring to the schematic interface 500 shown in fig. 5, interface 510 is a lock screen interface. In some cases, the popup may be triggered by a specific operation, for example, the user runs a music application in the background, and the operation of the screen-extinguishing operation may cause the popup interface 520 to appear on the screen-locking interface 510, and in the example of fig. 5, the popup interface 520 is a small window of a music application, where the popup includes music application information such as a song, a singer, a play control, a previous control, a next control, and the like, so that the user can conveniently and quickly control the music application on the screen-locking interface. The popup interface 520 may be displayed in a floating manner over the interface 510, which may be a full screen interface or a small window interface in some cases, and the popup may be shielded from closing the popup by the user, which may cause interference to the user. In some cases, as shown in interface 520, application information for the popup is not displayed in the popup, and it is difficult for the user to identify what application the current popup interface is. For example, a user may have multiple music applications, and not displaying application information may make it difficult for the user to distinguish which music application is currently being launched, and may cause unnecessary cost consumption if an application is selected in error. For another example, some malicious applications may disguise that the lock screen interface is overlaid on the lock screen interface and deliberately hide their identity on the pop-up interface, such that a user may be misled into the malicious application upon clicking, adding trouble or potential safety hazard to the user.

In other examples, the act of triggering a pop may also be detecting that an input interface is connected, such as when a data line is plugged into a charging interface, while a bright screen is triggered, some applications may also be triggered to initiate a pop.

Embodiments in the present application propose solutions for window control for identifying and controlling the pop-up behavior of an application. In some embodiments, the basic information of the popup application can be presented to the user by processing and packaging the popup interface of the application on the lock screen interface, so that the user can conveniently and quickly identify the basic information of the popup application. In some embodiments, a title bar may be added to the popup window, referring to interface 600 shown in FIG. 6A. When the screen is locked, the background application A music initiates a popup request. The system can inquire the basic information of the background application and judge whether the background application has the screen locking popup window authority, if so, the system allows the background application to popup window on the screen locking interface, but performs interface conversion on the popup window display interface according to the basic information of the application. In some embodiments, a title bar may be added to the pop-up window, and referring to the schematic interface 600 shown in fig. 6A, a pop-up window interface 620 is displayed on the lock screen interface 610, where the pop-up window interface 620 is a pop-up window initiated by the background application "a music", and the pop-up window interface 620 has the title bar 630 added to the pop-up window interface 520. The popup interface 620 includes a title bar 630 in addition to music application information such as songs, singers, play controls, previous controls, next controls, etc. The title bar 630 may include a zoom-in control 632, a close control 634, and application information 636. Magnification control 632 may be used to zoom in the zoomed out popup interface to a full screen popup interface 650, as shown in FIG. 6B. Closing control 634 is used to close the pop-up window, providing the user with the option of quickly exiting the pop-up window. The application information 636 can display application information such as application names (e.g. "a music"), application icons and the like, which are obtained by analyzing application information identifiers (e.g. package names and requested class names), and the display of the application information 636 can enable a user to quickly know the source of popup behaviors, so that loss or hidden danger caused by misleading the user by a malicious popup is avoided. In some embodiments, the pop-up interface 620 may be moved to other locations in response to a drag operation by a user. In other embodiments, rather than closing the pop-up window by clicking on the close control 634, the pop-up window may be controlled by an operation on hardware, e.g., the electronic device 100 may close the pop-up window 620 in response to a user pressing a power key.

When electronic device 100 detects that magnification control 632 is clicked, interface 640 shown in FIG. 6B may be displayed, with pop-up interface 620 being magnified to a full screen pop-up interface 650, completely overlaying Yu Suobing interface 610. The pop-up window interface 650 includes details of the music application, such as songs, singers, play controls, previous controls, next controls, volume adjustment controls, etc., and the title bar 630. A shrink control 638, a close control 634, and application information 636 may be included in the title bar 630. The zoom-out control 638 may be used to trigger zooming out of the full screen pop-up interface 650 to the pop-up interface 620.

The electronic device 100 may further include a notification management setting interface, so that a user can manage popup window rights and popup window modes of different applications conveniently. Referring to interface 700 shown in fig. 7, a notification management column 720 may be included in setup interface 710. In response to the user clicking on notification management field 720, electronic device 100 may display notification management interface 730, where notification management interface 730 may display options corresponding to a number of different applications, such as browser, camera, music, map, sports, mail, web pad, etc. application options are displayed in box 740. Clicking on the browser option may display an interface 800 as shown in fig. 8, wherein in the notification management interface 810 of the browser, options including but not limited to the following may be displayed: permission notification 811, silence notification 812, foreground notification 813, background notification 814, full screen notification 815, banner notification 816, lock screen notification 817, notification sound 818, vibration 819, and the like. The allow notification 811 option indicates whether the application notification is allowed, and when the allow notification 811 option is off, any notification for the application will be intercepted and not sent out. The on indication of the silent notification 812 option allows notifications but there are no reminders, e.g., no reminders such as banners, alert tones, or vibrations, and the notification can be displayed only in the drop down notification bar. The opening of the foreground notification 813 option indicates that notification is allowed when the application is a foreground application. The opening of the background notification 814 option indicates that notification is allowed when the application is a background application. The open indication of the full screen notification 815 option allows the notification box to be displayed full screen. The open indication of the banner notification 816 option allows the notification box to be displayed in the form of a notification banner. The unlock indication of the lock screen notification 817 option allows the application notification when the screen is locked. The notification sound 818 option indicates the selected alert sound. The vibration 819 option indicates whether the electronic device vibrates when notified.

It will be appreciated that the various user interfaces described in the above embodiments of the application are merely exemplary interfaces and are not limiting of other embodiments of the application. In other embodiments, different interface layouts may be adopted in the user interface, more or fewer controls may be included, other functional options may be added or reduced, and different expression forms may be provided, so long as the technical solutions based on the same inventive concept provided by the present application are all within the scope of protection of the present application.

Fig. 9 illustrates a flow chart 900 of window control logic provided by some embodiments of the application. In combination with the embodiments of fig. 3A and 3C, in some embodiments, the size of the popup may be reduced, interference caused by a full screen popup may be avoided, and application identification information may be added to the popup.

At block 901, the electronic device detects that application a requests to launch a popup. In some embodiments, application a requests a system to initiate an activity management service, initiating a pop request. At block 902, the electronic device determines whether application A is a foreground application or a background application, and if so goes to block 903, and if so goes to block 904. At block 903, the electronic device allows the popup of application a. At block 904, the electronic device determines whether a pass condition, such as the notification authority set by the user in fig. 8, is satisfied by the background application, and whether the application is allowed to pop the window in the current situation, such as that the application has been set in the system to push the pop content in a notification form, but is not allowed to pop the window in a screen-locked state, then if the request of the application to initiate the pop under the screen-locked application does not satisfy the pass condition, the request of the application to initiate the pop will be intercepted, and other application foreground runtime requests will convert the content of the pop into a notification banner. If the pass condition is met then block 903 is passed, i.e. the pop-up window is allowed, and if the pass condition is not met then block 908 is passed. At block 908, the electronic device intercepts the popup and does not display the popup for application a. After the electronic device allows the popup of application a, the flow of blocks 905 to 907 continues. At block 905, the electronic device creates a carrier carrying the popup, and referring to the embodiments shown in fig. 3A, 3C, the electronic device may package and process the original popup to generate a new popup carrier. At block 906, the electronic device obtains an application information identification, such as a package name, a requested class name, an icon, and the like. In block 907, a popup window is displayed, which may or may not be a full screen window, and referring to the embodiments shown in fig. 3A, 3B, the popup window may add a title bar 330 on the basis of the original popup interface, and the title bar 330 may include an zoom-in control 332 (for a zoom-out window) or a zoom-out control 338 (for a full screen window), a close control 334, and application information 336. Zoom-in control 332 may be used to zoom in on a zoomed out popup interface to a full screen popup interface 350 and zoom-out control 338 may be used to trigger zooming out on a full screen popup interface 350 to a popup interface 320. The close control 334 is used to close the pop-up window, providing the user with the option of quickly exiting the pop-up window. The application information 336 may display application information such as application names (e.g., "browser"), application icons, etc., which is obtained by analyzing application information identifiers (e.g., package names, requested class names), and the display application information 336 may enable a user to quickly understand the source of the popup behavior, so as to avoid misleading the user to cheat rights by a malicious popup.

Fig. 10 illustrates a flow chart 1000 of window control logic provided by some embodiments of the application. In conjunction with the embodiments of fig. 4A or fig. 4B, in some embodiments, the application's popup interface may be hidden and converted into notification form to reduce the user's interference by the popup and to add application identification information to the notification.

At block 1001, the electronic device detects that application B requests to launch a popup. In some embodiments, application B requests the system to initiate an activity management service, initiating a pop request. At block 1002, the electronic device determines whether the application B is a foreground application or a background application, and proceeds to block 1003 if it is a foreground application, and proceeds to block 1004 if it is a background application. At block 1003, the electronic device allows the pop-up window of application B. At block 1004, the electronic device determines whether a release condition, such as the notification authority set by the user in fig. 8, is satisfied, and if the release condition is satisfied, goes to block 1003, i.e., a pop-up window is allowed, and if the release condition is not satisfied, goes to block 1008. At block 1008, the electronic device intercepts the popup and does not display the popup for application B. After the electronic device allows the popup of application B, the flow of blocks 1005 to 1007 continues. In block 1005, the electronic device may hide the popup window, and the manner of hiding the popup window interface may be various, for example, the window may be set to be transparent, then, for example, the window may be set to be 1 pixel size unrecognizable by naked eyes, and then, for example, the background color of the window may be set to be integrated into the background interface. In addition, when the window is hidden, the audio corresponding to the popup window can be normally played, and the playing can also be paused, which is not limited by the embodiment of the application. At block 1006, the electronic device creates a notification, which is also a carrier carrying the pop-up window, and then the electronic device obtains an application information identifier, i.e., the electronic device may convert the pop-up window interface into a notification message to alert the user, where the application information identifier may be, for example, a package name, a requested class name, an application icon, etc. At block 1007, a notification is displayed, such as in the example of FIG. 4A, over the foreground interface 410, a hover notification banner 420 is displayed, the notification banner 420 may include a title bar 422 and a content bar 424, the title bar 422 may include application information 336, such as a "browser" application name and application icon, etc., from which the "browser" application was parsed, and a close control. The notification banner 420 occupies a small area and typically remains displayed for a few seconds and then automatically exits the foreground display interface, such as being placed in a notification bar. If the user needs to view the pop-up content, the notification banner 420 may be clicked on, a similar pop-up interface as pop-up interface 320 or pop-up interface 350 may be displayed, and if the user does not want to process the pop-up request, the notification may be ignored. The method for processing the popup window can not interrupt the use of the foreground application, does not need users to immediately process the popup window request, and reduces the interference to the users.

By implementing the process 900 or the process 1000 in the above embodiment, the system performance can be improved, the interference of the malicious popup behavior of the application on the user can be reduced, the identification of the popup application and the management and control of the application behavior can be enhanced, the man-machine interaction performance can be enhanced, and the use experience of the user can be improved.

Referring to fig. 11, fig. 11 is a schematic diagram illustrating a window control method 1100 according to an embodiment of the application. By way of example, the device implementing the window control method may be the aforementioned electronic device 100, such as a smart phone, tablet computer, personal computer, desktop computer, laptop computer, handheld computer, game console, smart screen (smart television), AR device, VR device, AI device, wearable device, car machine (in-car device), IOT device, or other type of electronic device, etc. The embodiment of the application does not limit the specific type of the electronic equipment.

At block 1101, the device displays an interface of a first application. The embodiment of the application does not limit the type of the first application, and for example, the first application may be a screen locking application, a desktop application, or a third party application running in the foreground. At block 1102, the device detects that a second application initiates a request to display a popup. At block 1103, the device displays a floating window associated with the second application over the interface of the first application. The floating window includes a title bar including an identification of the second application. By implementing the method, the system performance can be improved, the interference of the malicious popup behavior of the application on the user can be reduced, the identification of the popup application and the management and control of the application behavior can be enhanced, the man-machine interaction performance can be enhanced, and the use experience of the user can be improved. For example, the floating window is a popup window 320, a notification window 420, a popup window 620, and the like.

In some embodiments, the identification of the second application may include application information related to the second application that includes one or more of: application name, application icon, application title, application description or developer information, etc. The information of the second applications facilitates the user to identify the applications corresponding to the floating window. For example, title bar 330 shown in FIG. 3A.

In some embodiments, the device detects an operation indicating closing of the floating window, and the device removes the floating window. The floating window closing mode can avoid that some malicious windows close the channel in a hidden way, so that users are forced to respond to other requirements of the popup window, for example, the popup window cannot be closed, and advertisements are forced to be watched. In some embodiments, the hover window includes a close control that is displayed on the right side of the title bar, indicating that the operation to close the hover window is a click operation on the close control, such as close control 334. The close control may also be located to the left of the title bar or in any area below the hover window, in the lower left corner, etc., as the embodiments are not limited in this regard.

In some embodiments, the first application is a lock screen application, indicating that the operation to close the floating window is a pressing operation on a power key. In some embodiments, closing the floating window may be triggered by hardware. In some embodiments, the first application is a lock screen application, the second application is a music application, song information and play controls are included in the floating window, and names of the music application, icons of the music application and closing controls are included in the title bar. Referring to the embodiment shown in fig. 6A, a popup interface 620 is displayed on the lock screen interface 610, the popup interface 620 being a popup initiated by a background application, the popup interface 620 having a title bar 630 added to the popup interface 520. The popup interface 620 includes a title bar 630 in addition to music application information such as songs, singers, play controls, previous controls, next controls, etc. The title bar 630 may include a zoom-in control 632, a close control 634, and application information 636. Magnification control 632 may be used to zoom in the zoomed out popup interface to a full screen popup interface 650, as shown in FIG. 6B. Closing control 634 is used to close the pop-up window, providing the user with the option of quickly exiting the pop-up window. The application information 636 can display application information such as application names and application icons, which is obtained by analyzing application information identifiers (such as package names and request class names), and the display of the application information 636 can enable a user to quickly know the source of popup behaviors, so that loss or hidden danger caused by misleading the user by a malicious popup is avoided.

In some embodiments, the requesting is requesting to display a second window that completely covers the interface, the method further comprising: in response to the request, the device converts the second window into a floating window, the size of the floating window being smaller than the size of the second window, the second window not including the title bar, the content in the floating window including the content in the second window. The size of the floating window displayed is smaller than the size of the requested popup window, less obscuring the interface of the first application, and the dragging movement is possible. Referring to the embodiment shown in fig. 3A, the second window may be, for example, a pop-up window as shown in interface 220, and the floating window may be, for example, pop-up window interface 320.

In some embodiments, the floating window includes a magnification control, the method further comprising: the device detects an operation on the zoom-in control, the device displays the zoomed-in hover window as a full-screen window, e.g., zoom-in control 332 may be used to zoom-in the zoomed-out pop-in interface 320 to a full-screen pop-in interface 350. In some embodiments, the magnified floating window includes a zoom-out control, the method further comprising: the device detects an operation to zoom out the magnified floating window out, e.g., zoom out control 338 may be used to trigger zooming out full screen popup interface 350 to popup interface 320. This allows switching between a reduced window or a full screen window as desired. Reference is made to the embodiment shown in fig. 3A, 3B.

In some embodiments, the floating window is a notification window that is displayed at the top or bottom of the interface, and that moves out of the interface if no operation instruction is received for more than a predetermined time. Converting the popup window into a lighter notification window can further reduce interference to the user. Refer to the embodiment shown in fig. 4A. For example, a hover notification banner 420 is displayed over the foreground interface 410, a title bar 422 and a content bar 424 may be included in the notification banner 420, and application information 336 and a close control may be included in the title bar 422. The notification banner 420 occupies a small area and typically remains displayed for a few seconds and then automatically exits the foreground display interface, such as being placed in a notification bar. If the user needs to view the pop-up content, the notification banner 420 may be clicked on, a similar pop-up interface as pop-up interface 320 or pop-up interface 350 may be displayed, and if the user does not want to process the pop-up request, the notification may be ignored.

In some embodiments, the first application is a foreground application, the second application is the same application as the first application, and the method further comprises: after the device detects that the first application initiates a request to display a popup window, the device allows a floating window associated with the first application to be displayed on the interface. The popup of the foreground application may be preferentially responded to.

In some embodiments, the first application is a foreground application and the second application is a background application, the method further comprising: after the device detects that the second application initiates a request for displaying the popup window, the device judges whether the second application has a permission interface to display the floating window. If the second application has permission to display the floating window, the device allows the floating window associated with the second application to be displayed on the interface. If the second application does not have permission to display the floating window, the device denies the request to display the popup window. Whether to release the popup window of the background application needs to inquire whether the release condition is satisfied. The popup permission is set for the application, so that a user can conveniently control popup behaviors.

In some embodiments, the method further comprises: if the second application has the right to display the floating window, the device creates a carrier carrying the popup window. The device obtains application information of the second application. The device displays a floating window related to the second application based on the carrier, and the identification of the second application displayed in the floating window is from the acquired application information of the second application. Application information can be added to package the popup window, so that the popup window is convenient for a user to identify. Reference is made to the embodiment shown in fig. 9.

In some embodiments, if the second application has permission to display the floating window, the device hides the display popup. The device creates a notification window, the device acquires application information of the second application, the device displays the notification window related to the second application, and the identifier of the second application displayed in the notification window comes from the acquired application information of the second application. The notification window is also a carrier for bearing the floating window, and the conversion of the popup window into the notification window can further reduce the interference to the user. In some embodiments, the hidden display popup includes any one of the following: the popup window is set as a transparent window, the display color of the popup window is consistent with the background color of the interface, and the popup window is set to a predetermined size so as not to be recognized by a user. Reference is made to the embodiment shown in fig. 10.

In some embodiments, the permissions are set by one or more of: permission of notification, permission of silent notification, permission of foreground notification, permission of background notification, permission of displaying full-screen window, permission of displaying notification window, and permission of displaying window on lock screen interface. By setting the popup right for the application, the popup behavior can be better controlled. Reference is made to the embodiments shown in figures 7 and 8.

In some embodiments, the device may not display the title bar upon detecting that the requested popup may display an identification of the second application. In other embodiments, the device may display a title bar including the second application identification on the basis of the requested popup window displaying the identification of the second application, which may display repeated application information, such as displaying two-bar application identifications.

The above embodiments are merely for the purpose of more clearly illustrating the technical aspects of the present application, and do not limit the present application. Other embodiments may include more or fewer processes or steps, or various embodiments may be combined or split to obtain more implementations, and embodiments of the application are not limited in this respect.

The related embodiments shown in fig. 11 are some implementations provided by the present application, and are merely examples shown for more clearly illustrating the technical solution of the present application, and are not limited to other embodiments of the present application. Other embodiments may include more or fewer modules, structures, flows, or steps, or various embodiments may be combined or split to achieve more implementations, and embodiments of the application are not limited in this respect.

A window control apparatus 1200 according to an embodiment of the present application is described below. The apparatus 1200 may be the aforementioned electronic device 100. The apparatus 1200 may include: the display module 1201 is configured to display an interface of a first application, the detection module 1202 is configured to detect that a second application initiates a request to display a popup window, and the display module 1201 is further configured to display a floating window associated with the second application over the interface of the first application, the floating window including a title bar including an identification of the second application. The embodiment of the application does not limit the type of the first application, and for example, the first application may be a screen locking application, a desktop application, or a third party application running in the foreground. By means of the device, system performance can be improved, interference of malicious popup behaviors of an application to a user is reduced, recognition of popup applications and management and control of the application behaviors are enhanced, man-machine interaction performance is enhanced, and use experience of the user is improved.

In some embodiments, the identification of the second application includes application information related to the second application that includes one or more of: application name, application icon, application title, application description, or developer information. The information of the second applications facilitates the user to identify the applications corresponding to the floating window.

In some embodiments, the detection module 1202 is further configured to detect an operation indicating closing of the floating window, and the window management module 1203 is configured to remove the floating window. The floating window closing mode can avoid that some malicious windows close the channel in a hidden way, so that users are forced to respond to other requirements of the popup window, for example, the popup window cannot be closed, and advertisements are forced to be watched. In some embodiments, the hover window includes a close control that is displayed on the right side of the title bar, indicating that the operation to close the hover window is a click operation on the close control. The close control may also be located to the left of the title bar or in any area below the hover window, in the lower left corner, etc., as the embodiments are not limited in this regard.

In some embodiments, the first application is a lock screen application, indicating that the operation to close the floating window is a pressing operation on a power key. In some embodiments, closing the floating window may be triggered by hardware. In some embodiments, the first application is a lock screen application, the second application is a music application, song information and play controls are included in the floating window, and names of the music application, icons of the music application and closing controls are included in the title bar. Refer to the embodiment shown in fig. 6A.

In some embodiments, the apparatus further comprises a conversion module 1204 for converting the second window into a floating window in response to the request, the size of the floating window being smaller than the size of the second window, the second window not including the title bar, the content in the floating window including the content in the second window. The size of the floating window displayed is smaller than the size of the requested popup window, less obscuring the interface of the first application, and the dragging movement is possible. Reference is made to the embodiment shown in fig. 3A, 3C.

In some embodiments, the floating window includes an enlargement control, the detection module 1202 is further configured to detect an operation acting on the enlargement control, and the window management module 1203 is further configured to enlarge the floating window, the enlarged floating window being a full screen window. The reduced window or full screen window may be switched as desired. In some embodiments, the enlarged floating window includes a zoom-out control, the detection module 1202 is further configured to detect an operation on the zoom-out control, and the window management module 1203 is further configured to zoom out the enlarged floating window. The reduced window or full screen window may be switched as desired. Reference is made to the embodiment shown in fig. 3A, 3B.

In some embodiments, the floating window is a notification window that is displayed at the top or bottom of the interface, and that moves out of the interface if no operation instruction is received for more than a predetermined time. Converting the popup window into a lighter notification window can further reduce interference to the user. Reference is made to the embodiment shown in fig. 4A or fig. 4B.

In some embodiments, the first application is a foreground application, the second application is the same application as the first application, and after detecting that the first application initiates a request for displaying a popup window, the determining module 1205 is configured to allow displaying a floating window related to the first application on the interface. The popup of the foreground application may be preferentially responded to.

In some embodiments, the first application is a foreground application, the second application is a background application, and the determining module 1205 is further configured to determine whether the second application has a permission interface to display a floating window after the device detects that the second application initiates a request for displaying a popup window. The determination module 1205 is also configured to allow the floating window associated with the second application to be displayed on the interface if the second application has permission to display the floating window. The determination module 1205 is further configured to reject the request to display the popup window if the second application does not have permission to display the floating window. Whether to release the popup window of the background application needs to inquire whether the release condition is satisfied. The popup permission is set for the application, so that a user can conveniently control popup behaviors.

In some embodiments, if the second application has the right to display a floating window, the creation module 1206 is to create a carrier carrying the popup. The acquisition module 1207 is configured to acquire application information of the second application. The display module 1201 is further configured to display a floating window related to the second application based on the carrier, where the identifier of the second application displayed in the floating window is derived from the acquired application information of the second application. Application information can be added to package the popup window, so that the popup window is convenient for a user to identify. Reference is made to the embodiment shown in fig. 9.

In some embodiments, the window management module 1203 is further configured to hide the display popup if the second application has permission to display the floating window. The creating module 1206 is configured to create a notification window, the acquiring module 1207 is configured to acquire application information of the second application, and the display module 1201 is further configured to display the notification window related to the second application, where the identifier of the second application displayed in the notification window is derived from the acquired application information of the second application. The notification window is also a carrier for bearing the floating window, and the conversion of the popup window into the notification window can further reduce the interference to the user. In some embodiments, the hidden display popup includes any one of the following: the popup window is set as a transparent window, the display color of the popup window is consistent with the background color of the interface, and the popup window is set to a predetermined size so as not to be recognized by a user. Reference is made to the embodiment shown in fig. 10.

In some embodiments, the permissions may be set by one or more of: permission of notification, permission of silent notification, permission of foreground notification, permission of background notification, permission of displaying full-screen window, permission of displaying notification window, and permission of displaying window on lock screen interface. By setting the popup right for the application, the popup behavior can be better controlled. Reference is made to the embodiment shown in fig. 8.

In some embodiments, the display module 1201 may not display the title bar upon detecting that the requested pop-up window may display the identity of the second application. In other embodiments, the display module 1201 may display a title bar including the second application identifier, possibly displaying repeated application information, such as displaying two-bar application identifiers, in addition to the requested popup window displaying the identifier of the second application.

It should be noted that, the device described in the foregoing embodiments is only for describing one implementation manner of the technical solution of the present application more clearly, and does not constitute a limitation to other embodiments of the present application, and in practical application, the type, number and association relationship of each functional module of the device are not limited. In some embodiments, more or fewer functional modules, etc. may be included in the apparatus. The various functional modules in the apparatus may be implemented in software, hardware, or a combination of both. It will be understood that, for specific implementation of each functional unit included in the apparatus, reference may be made to the detailed description in other embodiments of the present application, which is not repeated here.

It should be noted that, in the embodiment of the present application, the division of the modules or units is schematic, only one logic function is divided, and another division manner may be adopted in actual implementation. In addition, each functional unit in the embodiment may be integrated in one unit, may exist alone physically, or may be integrated into one unit. The integrated units may be implemented in hardware, in software functional units, or in a combination of hardware and software.

Embodiments of the present application also provide a chip that may include an input interface, an output interface, and a processing circuit. In the embodiment of the disclosure, the interaction of the signaling or data can be completed by the input interface and the output interface, and the generation and the processing of the signaling or data information can be completed by the processing circuit.

Embodiments of the present application also provide a chip system including a processor for supporting a computing device to implement the functions referred to in any of the above embodiments. In one possible design, the chip system may further include a memory for storing necessary program instructions and data that, when executed by the processor, cause the apparatus on which the chip system is installed to implement the method referred to in any of the embodiments above. The chip system may be formed from one or more chips, and may include chips and other discrete devices, for example.

Embodiments of the present application also provide a processor for coupling with a memory, the memory storing instructions that, when executed by the processor, cause the processor to perform the methods and functions referred to in any of the embodiments above.

Embodiments of the present application also provide a computer readable storage medium having stored thereon computer instructions or program code which, when executed by a processor, cause the processor to perform the methods and functions referred to in any of the embodiments above. A computer readable medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. The computer readable medium may be a computer readable signal medium or a computer readable storage medium. The computer readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination thereof. The computer readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that contains an integration of one or more available media. More detailed examples of computer readable storage media include an electrical connection with one or more wires, magnetic media (e.g., diskette, floppy disk, hard disk, magnetic tape, magnetic storage device), optical media (e.g., optical storage device, DVD), semiconductor media (e.g., solid state disk), random Access Memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), any suitable combination thereof, and the like.

In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. Embodiments of the present application also provide at least one computer program product tangibly stored on a non-transitory computer-readable storage medium. The computer program product comprises one or more computer-executable instructions, such as instructions included in program modules, which are executed in a device on a real or virtual processor of a target to perform the processes, methods, and functions involved in any of the embodiments described above. When loaded and executed on a computer, produces a flow or function in accordance with embodiments of the application, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatus. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by a wired (e.g., coaxial cable, fiber optic, digital subscriber line), or wireless (e.g., infrared, wireless, microwave, etc.).

According to a method provided by an embodiment of the present application, the present application also provides a computer program product, including: computer program code which, when run on a computer, causes the computer to perform the processes, methods and functions of the embodiments described above. Generally, program modules include routines, programs, libraries, objects, classes, components, data structures, etc. that perform particular tasks or implement particular abstract data types. In various embodiments, the functionality of the program modules may be combined or split between program modules as desired. Machine-executable instructions for program modules may be executed within local or distributed devices. In distributed devices, program modules may be located in both local and remote memory storage media.

Computer program code for carrying out methods of the present disclosure may be written in one or more programming languages. These computer program code may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus such that the program code, when executed by the computer or other programmable data processing apparatus, causes the functions/operations specified in the flowchart and/or block diagram to be implemented. The program code may execute entirely on the computer, partly on the computer, as a stand-alone software package, partly on the computer and partly on a remote computer or entirely on the remote computer or server. In the context of this disclosure, computer program code or related data may be carried by any suitable carrier to enable an apparatus, device, or processor to perform the various processes and operations described above. Examples of carriers include signals, computer readable media, and the like. Examples of signals may include electrical, optical, radio, acoustical or other form of propagated signals, such as carrier waves, infrared signals, etc.

In general, the various embodiments of the application may be implemented in hardware or special purpose circuits, software, logic or any combination thereof. Some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software, which may be executed by a controller, microprocessor or other computing device. While various aspects of the embodiments of the disclosure are illustrated and described as block diagrams, flow charts, or using some other pictorial representation, it is well understood that these blocks, apparatus, systems, techniques or methods described herein may be implemented in, as non-limiting examples, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof.

As used in the above embodiments, the term "when …" may be interpreted to mean "if …" or "after …" or "in response to determination …" or "in response to detection …" depending on the context. Similarly, the phrase "at the time of determination …" or "if detected (a stated condition or event)" may be interpreted to mean "if determined …" or "in response to determination …" or "at the time of detection (a stated condition or event)" or "in response to detection (a stated condition or event)" depending on the context.

The foregoing has described implementations of the present disclosure, and the foregoing description is exemplary, not exhaustive, and not limited to the implementations disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the various implementations described. The terminology used herein was chosen in order to best explain the principles of each implementation, the practical application, or the improvement of technology in the marketplace, or to enable others of ordinary skill in the art to understand each implementation disclosed herein. The specific internal implementation may be different according to different types of electronic devices, different operating systems carried on the electronic devices, different programs used and different interfaces called, and the embodiment of the present application is not limited in any way, and may implement the feature functions described in the embodiment of the present application. The embodiments of the present application may be arbitrarily combined to achieve different technical effects.

The foregoing detailed description of the embodiments of the present application further illustrates the purposes, technical solutions and advantageous effects of the embodiments of the present application, and it should be understood that the foregoing is merely a specific implementation of the embodiments of the present application, and is not intended to limit the scope of the embodiments of the present application, and any modifications, equivalent substitutions, improvements, etc. made on the basis of the technical solutions of the embodiments of the present application should be included in the scope of the embodiments of the present application.

It should be noted that although the embodiments of the present application have been described above with reference to the accompanying drawings, respectively, the above embodiments are not independent of each other, and they may be combined to obtain other embodiments. The manner, the case, the category, and the division of the embodiments in the embodiments of the present application are merely for convenience of description, and should not be construed as a particular limitation, and the features in the various manners, the categories, the cases, and the embodiments may be combined with each other in a case where they conform to logic. The embodiments of the present application may be arbitrarily combined to achieve different technical effects. The embodiments of the present application are not listed in any way for various combinations.

Furthermore, although the operations of the methods of the present disclosure are depicted in the drawings in a particular order, this is not required to or suggested that these operations must be performed in this particular order or that all of the illustrated operations must be performed in order to achieve desirable results. Rather, the steps depicted in the flowcharts may change the order of execution. Additionally or alternatively, certain steps may be omitted, multiple steps combined into one step to perform, and/or one step decomposed into multiple steps to perform. It should also be noted that features and functions of two or more devices according to the present disclosure may be embodied in one device. Conversely, the features and functions of one device described above may be further divided into multiple devices to be embodied.

Claims

1. A window control method, the method comprising:

The device displays an interface of the first application;

the equipment detects that a second application initiates a request for displaying a popup window; and

The device displays a floating window associated with the second application over the interface, the floating window including a title bar including an identification of the second application.

2. The method of claim 1, wherein the identification of the second application includes application information related to the second application that includes one or more of: application name, application icon, application title, application description, or developer information.

3. The method according to claim 1, wherein the method further comprises:

The device detecting an operation indicating closing of the floating window; and

The device removes the floating window.

4. The method of claim 3, wherein the hover window includes a close control that is displayed on the right side of the title bar, the operation indicating closing of the hover window being a click operation on the close control.

5. A method according to claim 3, wherein the first application is a lock screen application and the operation indicating closing of the floating window is a pressing operation acting on a power key.

6. The method of claim 1, wherein the request is to display a second window that completely covers the interface, the method further comprising:

In response to the request, the device converts the second window into the floating window, the size of the floating window being smaller than the size of the second window, the second window not including the title bar, the content in the floating window including the content in the second window.

7. The method of claim 6, wherein the floating window includes a zoom-in control, the method further comprising:

the device detecting an operation acting on the magnification control;

The device displays the magnified floating window, which is a full screen window.

8. The method of claim 7, wherein the zoomed-in floating window includes a zoom-out control, the method further comprising:

the device detecting an operation acting on the zoom-out control;

the apparatus narrows the enlarged floating window.

9. The method of any one of claims 1-8, wherein the floating window is a notification window that is displayed at a top or bottom of the interface, the notification window being moved out of the interface if no operation instruction is received for more than a predetermined time.

10. The method of any of claims 1-5, wherein the first application is a lock screen application, the second application is a music application, song information and a play control are included in the floating window, and a name of the music application, an icon of the music application, and a close control are included in the title bar.

11. The method of claim 1, wherein the first application is a foreground application and the second application is the same application as the first application, the method further comprising:

after the device detects that a first application initiates a request to display a popup window, the device allows the floating window associated with the first application to be displayed on the interface.

12. The method of claim 1, wherein the first application is a foreground application and the second application is a background application, the method further comprising:

after the equipment detects that a second application initiates a request for displaying a popup window, the equipment judges whether the second application has permission for displaying the suspended window on the interface;

If the second application has permission to display the floating window, the device allows the floating window related to the second application to be displayed on the interface;

if the second application does not have permission to display the floating window, the device denies the request to display a popup window.

13. The method according to claim 12, wherein the method further comprises:

If the second application has permission to display the floating window, the device creates a carrier bearing the popup window;

the equipment acquires application information of the second application;

The device displays the floating window related to the second application based on the carrier, and the identification of the second application displayed in the floating window is from the acquired application information of the second application.

14. The method according to claim 12, wherein the method further comprises:

if the second application has permission to display the floating window, the equipment displays the popup window in a hidden mode;

the device creates a notification window;

the equipment acquires application information of the second application;

The device displays the notification window related to the second application, and the identifier of the second application displayed in the notification window is from the acquired application information of the second application.

15. The method of claim 14, wherein the concealing the popup window comprises any one of: and setting the popup window as a transparent window, enabling the display color of the popup window to be consistent with the background color of the interface, and setting the popup window to be in a preset size so as not to be recognized by a user.

16. The method of claim 12, wherein the rights are set by one or more of: permission of notification, permission of silent notification, permission of foreground notification, permission of background notification, permission of displaying full-screen window, permission of displaying notification window, and permission of displaying window on lock screen interface.

17. The method according to any one of claims 1-16, wherein the device is any one of the following: cell phone, tablet computer, notebook computer, personal computer, smart watch, smart bracelet, smart television.

18. A window control device, comprising:

A display module configured to display an interface of a first application;

The detection module is configured to detect that a second application initiates a request for displaying a popup window; and

The display module is further configured to display a floating window associated with the second application over the interface, the floating window including a title bar including an identification of the second application.

19. An electronic device comprising a memory having stored therein executable instructions and a processor coupled to the memory for invoking the executable instructions to cause the electronic device to perform the method according to any of claims 1-17.

20. A computer readable storage medium storing computer executable instructions which when executed by a processor implement the method of any one of claims 1 to 17.