Processing method, intelligent terminal and storage medium
By displaying control options for target interface elements on smart terminals and employing source tracing technology, the problem of users finding it difficult to close intrusive interface elements from unknown sources has been solved, enabling a fast and convenient control path and improving user experience and system security.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- SHENZHEN TRANSSION HLDG CO LTD
- Filing Date
- 2026-03-09
- Publication Date
- 2026-07-21
Smart Images
Figure CN122431765A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of terminal technology, specifically to a processing method, a smart terminal, and a storage medium. Background Technology
[0002] With the rapid development of mobile internet applications, the number and variety of third-party applications on smart terminals (such as smartphones and tablets) are increasing daily. Some applications, for commercial gain, employ various technical means to push advertisements or other intrusive information to users.
[0003] In conceiving and implementing this application, the inventors discovered at least the following problems: when users encounter intrusive interface elements (such as malicious advertisements) that are difficult to close or have unknown sources, existing smart terminals cannot provide an effective operation path to control the intrusive interface element and / or the source application of the intrusive interface element, thus affecting the user experience.
[0004] The preceding description is intended to provide general background information and does not necessarily constitute prior art. Summary of the Invention
[0005] To address the aforementioned technical issues, this application provides a processing method, a smart terminal, and a storage medium, which can simplify the operation path for controlling interfering interface elements and / or the source applications of interfering interface elements, thereby improving user experience and system security.
[0006] This application provides a processing method applicable to smart terminals, comprising the following steps: S1. In response to the fulfillment of a preset trigger condition, display control options for the target interface element and / or the source application of the target interface element; the target interface element is the interface element currently displayed on the foreground application.
[0007] Optionally, before step S1, the following steps are included: In response to the triggering operation of the management and control integration settings control, a management and control integration settings interface is displayed. The management and control integration settings interface includes settings entry points for at least one of the following functions: prohibiting applications from obtaining device action permissions, prohibiting applications from background pop-up permissions, and enabling the system to automatically generate a close button for target interface elements. In response to any setting operation performed on any setting entry in the integrated management and control settings interface, the activation status of the corresponding function is updated.
[0008] Optionally, before displaying the control options for the source application of the target interface element, the following steps are included: Obtain the window attributes, process identifier, or package name of the target interface element to determine the source application of the target interface element.
[0009] Optionally, the target interface element includes at least one of the following: a pop-up window, a full-screen overlay interface, and a floating window.
[0010] Optionally, the target interface element is an interface that is not actively triggered by the current foreground application.
[0011] Optionally, the control options include an executable entry point for triggering at least one of the following operations: Close the operation entry point of the target interface element; The entry point for setting permissions related to interface display for the source application; The system will redirect you to the access point for the permission management page of the source application mentioned in the system settings.
[0012] Optionally, the permission settings related to interface display include setting at least one of the following permissions: background pop-up interface permission, floating window display permission, and permission to obtain device actions and orientation.
[0013] Optionally, the method further includes: The interface displaying the control options provides an entry point for deleting the source application.
[0014] Optionally, before step S1, the following steps are included: Based on predefined blacklists and whitelists, default restrictions are imposed on the background pop-up permissions of at least some applications.
[0015] This application also provides a smart terminal, including: a memory and a processor, wherein the memory stores a processing program, and when the processing program is executed by the processor, it implements the above-described processing method.
[0016] This application also provides a storage medium storing a computer program that, when executed by a processor, implements the above-described processing method.
[0017] As described above, the processing method of this application can be applied to smart terminals, including: in response to meeting a preset trigger condition, displaying control options for a target interface element and / or the application from which the target interface element originates; the target interface element is the interface element currently displayed on top of the foreground application. Through the above technical solution, the smart terminal can quickly and directly provide an operation path for controlling the interfering interface element and / or the application from which the interfering interface element originates when the user encounters an interfering interface. This achieves an immediate and convenient interactive channel from the user's perceived problem to the system providing a solution, placing complex backend management functions at the user's interaction point, greatly simplifying the operation path for controlling the interfering interface element and / or the application from which the interfering interface element originates, and improving user experience and system security. Attached Figure Description
[0018] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application. To more clearly illustrate the technical solutions of the embodiments of this application, the drawings used in the description of the embodiments will be briefly introduced below. Obviously, those skilled in the art can obtain other drawings based on these drawings without any creative effort.
[0019] Figure 1 A schematic diagram of the hardware structure of a mobile terminal to implement the various embodiments of this application.
[0020] Figure 2 This is a schematic diagram of a communication network system architecture provided in an embodiment of this application.
[0021] Figure 3 This is a flowchart illustrating a processing method according to one embodiment.
[0022] Figure 4 This is a schematic diagram of a smart terminal interface according to one embodiment. Figure 1 .
[0023] Figure 5 This is a schematic diagram of a smart terminal interface according to one embodiment. Figure 2 .
[0024] Figure 6 This is a schematic diagram of a smart terminal interface according to one embodiment. Figure 3 .
[0025] The realization of the objectives, functional features, and advantages of this application will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. The accompanying drawings have illustrated specific embodiments of this application, which will be described in more detail below. These drawings and textual descriptions are not intended to limit the scope of the concept in any way, but rather to illustrate the concepts of this application to those skilled in the art through reference to specific embodiments. Detailed Implementation
[0026] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application.
[0027] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element. Furthermore, components, features, and elements with the same names in different embodiments of this application may have the same meaning or different meanings, the specific meaning of which must be determined by its interpretation in that specific embodiment or further in conjunction with the context of that specific embodiment.
[0028] It should be understood that although the terms first, second, third, etc., may be used herein to describe various information, such information should not be limited to these terms. These terms are used only to distinguish information of the same type from one another. For example, without departing from the scope of this document, first information may also be referred to as second information, and similarly, second information may also be referred to as first information. Depending on the context, the word "if," as used herein, may be interpreted as "when," "when," or "in response to determination." Furthermore, as used herein, the singular forms "a," "an," and "the" are intended to also include the plural forms unless the context indicates otherwise. It should be further understood that the terms "comprising," "including," indicate the presence of the stated feature, step, operation, element, component, item, type, and / or group, but do not exclude the presence, occurrence, or addition of one or more other features, steps, operations, elements, components, items, types, and / or groups. The terms "or," "and / or," "including at least one of the following," etc., as used in this application may be interpreted as inclusive, or mean any one or any combination thereof. For example, "including at least one of the following: A, B, C" means "any one of the following: A; B; C; A and B; A and C; B and C; A and B and C." Similarly, "A, B, or C" or "A, B, and / or C" means "any one of the following: A; B; C; A and B; A and C; B and C; A and B and C." Exceptions to this definition only occur when the combination of elements, functions, steps, or operations is inherently mutually exclusive in some way.
[0029] It should be understood that although the steps in the flowcharts of this application's embodiments are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some of the steps in the figures may include multiple sub-steps or multiple stages. These sub-steps or stages are not necessarily completed at the same time, but can be executed at different times, and their execution order is not necessarily sequential, but can be performed alternately or in turn with other steps or at least a portion of the sub-steps or stages of other steps.
[0030] Depending on the context, the words “if” or “suppose” as used here can be interpreted as “when” or “in response to determination” or “in response to detection.” Similarly, depending on the context, the phrases “if determination” or “if detection (of the stated condition or event)” can be interpreted as “when determination” or “in response to determination” or “when detection (of the stated condition or event)” or “in response to detection (of the stated condition or event).”
[0031] It should be noted that step designations such as S1 and S2 are used in this document for the purpose of more clearly and concisely describing the corresponding content, and do not constitute a substantial limitation on the order. In specific implementation, those skilled in the art may execute S2 first and then S1, etc., but these should all be within the protection scope of this application.
[0032] It should be understood that the specific embodiments described herein are merely illustrative of this application and are not intended to limit this application.
[0033] In the following description, the use of suffixes such as "module," "part," or "unit" to denote elements is solely for the purpose of illustrative purposes and has no specific meaning in itself. Therefore, "module," "part," or "unit" may be used interchangeably.
[0034] Smart terminals can be implemented in various forms. For example, the smart terminals described in this application may include mobile terminals such as mobile phones, tablets, laptops, handheld computers, personal digital assistants (PDAs), portable media players (PMPs), navigation devices, wearable devices, smart bracelets, pedometers, etc., as well as fixed terminals such as digital TVs and desktop computers.
[0035] The following description will use a mobile terminal as an example. Those skilled in the art will understand that, apart from elements specifically designed for mobile purposes, the construction according to the embodiments of this application can also be applied to fixed-type terminals.
[0036] Please see Figure 1 This is a schematic diagram of the hardware structure of a mobile terminal implementing various embodiments of this application. The mobile terminal 100 may include: an RF (Radio Frequency) unit 101, a WiFi module 102, an audio output unit 103, an A / V (Audio / Video) input unit 104, a sensor 105, a display unit 106, a user input unit 107, an interface unit 108, a memory 109, a processor 110, and a power supply 111, etc. Those skilled in the art will understand that... Figure 1 The mobile terminal structure shown does not constitute a limitation on the mobile terminal. The mobile terminal may include more or fewer components than shown, or combine certain components, or have different component arrangements.
[0037] The following is combined Figure 1 A detailed introduction to each component of the mobile terminal: The radio frequency unit 101 can be used for receiving and transmitting signals during information transmission or calls. Specifically, it receives downlink information from the base station and processes it with the processor 110; additionally, it transmits uplink data to the base station. Typically, the radio frequency unit 101 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low-noise amplifier, and a duplexer. Furthermore, the radio frequency unit 101 can also communicate wirelessly with networks and other devices. The aforementioned wireless communications may use any communication standard or protocol, including but not limited to GSM (Global System of Mobile communication), GPRS (General Packet Radio Service), CDMA2000 (Code Division Multiple Access 2000), WCDMA (Wideband Code Division Multiple Access), TD-SCDMA (Time Division-Synchronous Code Division Multiple Access), FDD-LTE (Frequency Division Duplexing-Long Term Evolution), TDD-LTE (Time Division Duplexing-Long Term Evolution), 5G, and 6G.
[0038] WiFi is a short-range wireless transmission technology. Mobile terminals, through the WiFi module 102, can help users send and receive emails, browse web pages, and access streaming media, providing users with wireless broadband internet access. Although Figure 1 WiFi module 102 is shown, but it is understood that it is not a necessary component of a mobile terminal and can be omitted as needed without changing the nature of the invention.
[0039] The audio output unit 103 can convert audio data received by the radio frequency unit 101 or the WiFi module 102 or stored in the memory 109 into audio signals and output them as sound when the mobile terminal 100 is in call signal receiving mode, call mode, recording mode, voice recognition mode, broadcast receiving mode, etc. Furthermore, the audio output unit 103 can also provide audio output related to specific functions performed by the mobile terminal 100 (e.g., call signal receiving sound, message receiving sound, etc.). The audio output unit 103 may include a speaker, a buzzer, etc.
[0040] The A / V input unit 104 is used to receive audio or video signals. The A / V input unit 104 may include a graphics processing unit (GPU) 1041 and a microphone 1042. The GPU 1041 processes image data of still images or videos acquired by an image capture device (such as a camera) in video capture mode or image capture mode. The processed image frames can be displayed on the display unit 106. The image frames processed by the GPU 1041 can be stored in the memory 109 (or other storage medium) or transmitted via the radio frequency unit 101 or the WiFi module 102. The microphone 1042 can receive sound (audio data) in operating modes such as telephone call mode, recording mode, and voice recognition mode, and can process such sound into audio data. The processed audio (voice) data can be converted into a format that can be transmitted to a mobile communication base station via the radio frequency unit 101 in telephone call mode. The microphone 1042 can implement various types of noise cancellation (or suppression) algorithms to eliminate (or suppress) noise or interference generated during the reception and transmission of audio signals.
[0041] The mobile terminal 100 also includes at least one sensor 105, such as a light sensor, a motion sensor, and other sensors. Optionally, the light sensor includes an ambient light sensor and a proximity sensor. Optionally, the ambient light sensor can adjust the brightness of the display panel 1061 according to the ambient light level, and the proximity sensor can turn off the display panel 1061 and / or backlight when the mobile terminal 100 is moved to the ear. As a type of motion sensor, the accelerometer sensor can detect the magnitude of acceleration in various directions (generally three axes), and can detect the magnitude and direction of gravity when stationary. It can be used for applications that recognize the phone's posture (such as landscape / portrait switching, related games, magnetometer posture calibration), vibration recognition related functions (such as pedometer, tapping), etc. Other sensors that may be configured in the phone, such as fingerprint sensors, pressure sensors, iris sensors, molecular sensors, gyroscopes, barometers, hygrometers, thermometers, and infrared sensors, will not be described in detail here.
[0042] The display unit 106 is used to display information input by the user or information provided to the user. The display unit 106 may include a display panel 1061, which may be configured in the form of a liquid crystal display (LCD), an organic light-emitting diode (OLED), or the like.
[0043] User input unit 107 can be used to receive input numerical or character information, and generate key signal inputs related to user settings and function control of the mobile terminal. Optionally, user input unit 107 may include touch panel 1071 and other input devices 1072. Touch panel 1071, also known as touch screen, can collect touch operations on or near the user (such as operations performed by the user using a finger, stylus, or any suitable object or accessory on or near touch panel 1071), and drive corresponding connection devices according to a pre-set program. Touch panel 1071 may include two parts: touch detection device and touch controller. Optionally, touch detection device detects the user's touch position and the signal generated by the touch operation, and transmits the signal to touch controller; touch controller receives touch information from touch detection device, converts it into touch point coordinates, and sends it to processor 110, and can receive and execute commands from processor 110. In addition, touch panel 1071 can be implemented using various types such as resistive, capacitive, infrared, and surface acoustic wave. In addition to the touch panel 1071, the user input unit 107 may also include other input devices 1072. Optionally, other input devices 1072 may include, but are not limited to, one or more of the following: physical keyboard, function keys (such as volume control buttons, power buttons, etc.), trackball, mouse, joystick, etc., without being specifically limited here.
[0044] Optionally, the touch panel 1071 may cover the display panel 1061. When the touch panel 1071 detects a touch operation on or near it, it transmits the information to the processor 110 to determine the type of touch event. Subsequently, the processor 110 provides corresponding visual output on the display panel 1061 based on the type of touch event. Although in Figure 1 In this embodiment, the touch panel 1071 and the display panel 1061 are two independent components to realize the input and output functions of the mobile terminal. However, in some embodiments, the touch panel 1071 and the display panel 1061 can be integrated to realize the input and output functions of the mobile terminal. The specific implementation is not limited here.
[0045] Interface unit 108 serves as an interface through which at least one external device can connect to mobile terminal 100. For example, the external device may include a wired or wireless headset port, an external power supply (or battery charger) port, a wired or wireless data port, a memory card port, a port for connecting a device with an identification module, an audio input / output (I / O) port, a video I / O port, a headphone port, and so on. Interface unit 108 may be used to receive input (e.g., data, power, etc.) from the external device and transmit the received input to one or more elements within mobile terminal 100, or it may be used to transmit data between mobile terminal 100 and the external device.
[0046] The memory 109 can be used to store software programs and various data. The memory 109 may primarily include a program storage area and a data storage area. Optionally, the program storage area may store the operating system, applications required for at least one function (such as sound playback, image playback, etc.), etc.; the data storage area may store data created based on the use of the mobile phone (such as audio data, phonebook, etc.). Furthermore, the memory 109 may include high-speed random access memory, and may also include non-volatile memory, such as at least one disk storage device, flash memory device, or other volatile solid-state storage device.
[0047] The processor 110 is the control center of the mobile terminal. It connects various parts of the mobile terminal via various interfaces and lines. By running or executing software programs and / or modules stored in the memory 109, and by calling data stored in the memory 109, it performs various functions and processes data of the mobile terminal, thereby providing overall monitoring of the mobile terminal. The processor 110 may include one or more processing units; preferably, the processor 110 may integrate an application processor and a modem processor. Optionally, the application processor mainly handles the operating system, user interface, and applications, while the modem processor mainly handles wireless communication. It is understood that the modem processor may not be integrated into the processor 110.
[0048] The mobile terminal 100 may also include a power supply 111 (such as a battery) that supplies power to various components. Preferably, the power supply 111 can be logically connected to the processor 110 through a power management system, thereby enabling functions such as charging, discharging, and power consumption management through the power management system.
[0049] although Figure 1 As not shown, the mobile terminal 100 may also include a Bluetooth module, etc., which will not be described in detail here.
[0050] To facilitate understanding of the embodiments of this application, the communication network system on which the mobile terminal of this application is based is described below.
[0051] Please see Figure 2 , Figure 2 This application provides a communication network system architecture diagram. The communication network system is an LTE system based on the universal mobile communication technology. The LTE system includes a UE (User Equipment) 201, an E-UTRAN (Evolved UMTS Terrestrial Radio Access Network) 202, an EPC (Evolved Packet Core) 203, and the operator's IP services 204, which are connected in sequence.
[0052] Optionally, UE201 can be the aforementioned terminal 100, which will not be described in detail here.
[0053] E-UTRAN202 includes eNodeB2021 and other eNodeB2022s. Optionally, eNodeB2021 can connect to other eNodeB2022s via backhaul (e.g., X2 interface). eNodeB2021 connects to EPC203 and can provide UE201 with access to EPC203.
[0054] EPC203 may include an MME (Mobility Management Entity) 2031, an HSS (Home Subscriber Server) 2032, other MMEs 2033, an SGW (Serving Gateway) 2034, a PGW (Packet Data Network Gateway) 2035, and a PCRF (Policy and Charging Rules Function) 2036, etc. Optionally, MME2031 is the control node that handles signaling between UE201 and EPC203, providing bearer and connection management. HSS2032 is used to provide registers to manage functions such as the Home Location Register (not shown in the figure) and stores user-specific information such as service characteristics and data rates. All user data can be sent through SGW2034. PGW2035 can provide UE 201 IP address allocation and other functions. PCRF2036 is the policy and charging control decision point for service data flow and IP bearer resources. It selects and provides available policy and charging control decisions for the policy and charging enforcement function unit (not shown in the figure).
[0055] IP services 204 may include the Internet, intranet, IMS (IP Multimedia Subsystem), or other IP services.
[0056] Although the above description uses the LTE system as an example, those skilled in the art should know that this application is not only applicable to the LTE system, but also to other wireless communication systems, such as GSM, CDMA2000, WCDMA, TD-SCDMA, 5G and future new network systems (such as 6G), etc., without limitation.
[0057] Based on the above-described mobile terminal hardware structure and communication network system, various embodiments of this application are proposed.
[0058] Reference Figure 3 , Figure 3 This is a flowchart illustrating a processing method according to an embodiment of this application. The processing method of this embodiment can be applied to smart terminals (such as mobile phones), and includes the following steps: S1. In response to the fulfillment of preset trigger conditions, display control options for the target UI element and / or the source application of the target UI element; the target UI element is the UI element currently displayed on the foreground application.
[0059] Optionally, a target interface element refers to a view element displayed on the smart terminal screen and located above the currently interacting foreground application interface. Typical characteristics of a target interface element include, but are not limited to, at least one of the following: created by a non-foreground application, not triggered by an active request, and potentially interfering with the current task. Specific forms of a target interface element may include at least one of the following: pop-up windows, full-screen overlay interfaces (such as splash screen ads), floating windows, etc. Preset triggering conditions can be set according to actual needs, such as detecting that the currently displayed target interface element does not have an effective closing function (e.g., no close button is displayed for the target interface element), detecting a preset operation, etc. A preset operation refers to a specific interactive action that can trigger the processing method flow provided in this embodiment, such as pulling down from the top of the screen or using voice to call up the control center and clicking on a function control with a "pop-up catcher" or similar identifier. The source application refers to the application software that creates and controls the display of the target interface element. Control options refer to a set of access points or operation options for a series of management operations on the target interface element and / or the source application of the target interface element.
[0060] Optionally, if the user has enabled the system's automatic generation of close buttons for target interface elements on the smart terminal, and the smart terminal displays an advertisement without a close button for that advertisement, a system-level real close control will be automatically generated and displayed at a preset location on the advertisement. This close control can be used to close the target interface element. In other words, control options for the target interface element will be displayed.
[0061] Optionally, when a user performs a predefined operation on a smart terminal (such as clicking a specific icon in the control center), the smart terminal will directly trigger an interactive response, which displays a set of control options for the source application of the current interfering interface (i.e., the target interface element).
[0062] For example, when a user is browsing an article using a news reading app, an advertisement window suddenly pops up in the center of the screen, obscuring the content and lacking a valid close button. If the user wants to quickly close the advertisement and prevent it from reappearing, they can pull down from the top of the screen to bring up the control center. In the quick settings panel of the control center, they can click an icon called "Pop-up Catcher" (this icon is the trigger control for the preset action). The smart device immediately responds to this action, displaying a dialog box at the top of the current screen. This dialog box may display a message: "Pop-up source identified," along with an application icon and name (e.g., "Shopping Assistant"), and may provide three buttons: "Close Pop-up," "Deny Permissions," and "Application Details." These three buttons represent the control options for the source application (Shopping Assistant) of the advertisement window.
[0063] In this way, smart terminals can quickly and directly provide an operational path for controlling interfering interface elements and / or the applications from which they originate when users encounter interfering interfaces. This realizes an instant and convenient interactive channel from user-perceived problem to system-provided solution, bringing complex backend management functions to the user interaction site. This greatly simplifies the operational path for controlling interfering interface elements and / or the applications from which they originate, thereby improving user experience and system security.
[0064] Optionally, before step S1, the following steps are included: In response to the trigger operation of the management and control integration settings control, a management and control integration settings interface is displayed. The management and control integration settings interface includes settings entry for at least one of the following functions: prohibiting the application from obtaining device action permissions, prohibiting the application from background pop-up permissions, and enabling the system to automatically generate a close button for target interface elements. In response to any setting operation performed on any setting entry in the management and control integration settings interface, update the enabling status of the corresponding function.
[0065] Optionally, in the system settings application, the user can click on the management and control integration settings control to input a trigger operation for the control and control integration settings control into the smart terminal, and the smart terminal will display a management and control integration settings interface accordingly. This management and control integration settings interface can present the settings entry points for at least one of the following functions in a list format: prohibiting applications from obtaining device action permissions, prohibiting applications from obtaining background pop-up permissions, and enabling the system to automatically generate a close button for the target interface element. For example, taking an advertisement as the target interface element, prohibiting applications from obtaining device action permissions prevents applications from obtaining device motion data through sensors such as gyroscopes and accelerometers, thus preventing the triggering of "shake" type advertisements and avoiding users being redirected to the advertisement page due to slight device shaking; prohibiting applications from obtaining background pop-up permissions prevents applications from popping up any interface while running in the background, including pop-ups, floating windows, full-screen overlay interfaces, etc., to prevent applications from actively popping up advertisements and interfering with the current operation when the user is not using the application; enabling the system to automatically generate a close button for the target interface element automatically generates a real close button in the upper right corner of the advertisement interface when it is detected that the current advertisement does not have a valid close function, thus solving the problem of advertisements without a close button or with a fake close button, ensuring that users can close the advertisement normally. When a user interacts with any setting entry in the integrated management settings interface, the smart terminal updates the activation status of the corresponding function. Taking the integrated management settings interface as the smart advertising management interface, and using the "Enable system automatically generated ad close button function (referred to as the generate close button)" as an example, please refer to [link / reference]. Figure 4 When a user clicks the switch control corresponding to the function, the switch state changes from "off" to "on". If the smart terminal detects that the currently displayed advertisement page does not have a close button, it will automatically generate a real close button in the upper right corner of the advertisement interface.
[0066] In this way, by centralizing the control functions for multiple interface elements into a single interface, users no longer need to repeatedly search for different permission locations in the system settings; they can complete all interface element-related settings with a single access. Simultaneously, by enabling the system to automatically generate a close button, users are provided with the ability to instantly close interface elements.
[0067] Optionally, before displaying control options for the source application of the target UI element, the following options are included: Obtain the window attributes, process ID, or package name of the target UI element to determine the application from which the target UI element originates.
[0068] Optionally, before displaying the control options, the smart terminal will proactively call the underlying interface of the system window management service to perform source tracing analysis by obtaining key metadata such as the window attributes, process identifier, or package name of the target interface element, thereby accurately determining the source application of the target interface element.
[0069] For example, continuing with the example above, when the user clicks the "Pop-up Catcher" icon, the smart terminal does not directly display the control options. Instead, it queries the system object information of the currently top-level window (i.e., the advertisement window) to obtain the process ID and user ID of the application that created this window. Then, it queries the corresponding application package name based on the process ID and user ID. Finally, it matches the application name "Shopping Assistant" in the list of installed applications based on the application package name.
[0070] In this way, authoritative and real-time traceability of any top-level window is achieved, providing a unique and reliable basis for subsequent precise control. This solves the fundamental difficulty for users who do not know the origin of pop-up windows and other intrusive interfaces, as well as the problem that existing technologies lack the ability to automatically and accurately trace the source of intrusive interfaces.
[0071] Optionally, the target interface element includes at least one of the following: a pop-up window, a full-screen overlay interface, or a floating window.
[0072] Optionally, the target interface element can be a modal dialog-style pop-up. Optionally, the target interface element can be a full-screen overlay interface. For example, a full-screen splash ad that appears when a user opens an application, and this ad cannot be skipped until the countdown ends. Optionally, the target interface element can be a floating window. For example, a draggable floating window displayed in the corner of the screen when a video player application is playing in the background.
[0073] Optionally, the target interface element is an interface that is not actively triggered by an action in the current foreground application.
[0074] Optionally, the specific presentation of the target interface elements can be varied, such as a lottery advertisement that pops up automatically when the user does not click any related buttons, a merchant promotion that pops up automatically based on the geographical location, a check-in reminder pop-up triggered by a timer, or a full-screen advertisement that is actively pushed by the application while it is running in the background.
[0075] For example, while browsing an article using a news reading app, an advertisement window suddenly pops up in the center of the screen, obscuring the content. This pop-up is automatically generated by the shopping assistant app without any user interaction (such as clicking a button). This pop-up behavior does not respond to any active interaction within the news reading app. Therefore, it falls under the category of an interface triggered by a non-active action within the current foreground application. Conversely, if the user clicks the "share" button in the news reading app, and a share menu dialog box pops up on the smart terminal, this dialog box is triggered in response to an explicit user action. This falls under the category of an interface triggered by an active action within the current foreground application, i.e., a non-target interface element.
[0076] In this way, the application of the technical solution can be strictly limited to non-requested interfaces that are not forcibly interrupted or interfered with by the user, so as to exclude legitimate dialog boxes, menus, etc. actively invoked by the user clicking buttons in the application, avoid undue interference with normal application interaction, and ensure that the solution only targets malicious advertising behavior that truly needs to be addressed.
[0077] Optionally, the control options include an executable entry point for triggering at least one of the following operations: Close the operation entry point of the target interface element; The entry point for setting permissions related to the interface display of source applications; This redirects to the permission management page for the source application in system settings.
[0078] Optionally, the entry point for closing the target interface element can be a close button for the target interface element. After the user clicks the close button, the smart terminal will immediately close the target interface element or directly remove the target interface element.
[0079] Optionally, the entry point for setting permissions related to the interface display of the source application could be a "Disable Permissions" button. After the user clicks the "Disable Permissions" button, the smart terminal will directly modify the permission settings of the source application, such as disabling its permission to display a background pop-up interface. This operation may be completed silently in the background of the smart terminal, or the smart terminal may display a secondary confirmation dialog box for the user to confirm.
[0080] Optionally, the entry point for navigating to the permission management page of the source application in system settings could be an application details button. After the user clicks the application details button, the smart terminal will initiate the settings for the source application and automatically navigate to the application information page of the source application. On this page, the user can view or modify more permissions, or uninstall the application, etc.
[0081] In this way, a hierarchical, end-to-end control option is provided to meet users’ different needs from emergency handling to fundamental problem-solving, and to achieve closed-loop management of advertising governance.
[0082] Optionally, permission settings related to interface display include settings for at least one of the following permissions: background pop-up interface permission, floating window display permission, and permission to obtain device actions and orientation.
[0083] Optionally, when a user selects an entry point for setting permissions related to the interface display of the source application, such as clicking the "Disable Permissions" button, the smart terminal can provide more granular permission selection or directly disable a set of related permissions. In this embodiment, the smart terminal can provide the setting to disable at least one of the following permissions: 1) Background pop-up interface permission: After being disabled, the source application will not be able to pop up any windows while running in the background; 2) Floating window display permission: After being disabled, the source application will not be able to create any floating windows; 3) Permission to obtain device actions and directions: After being disabled, the source application will not be able to use sensors such as gyroscopes, thereby preventing the triggering of "shake" ads, etc.
[0084] For example, if a smart terminal detects that a video application is simultaneously using a full-screen splash screen ad, a pop-up ad during playback, and a shake-to-jump ad, the user can click the "Disable Permissions" button, and the smart terminal can simultaneously disable background pop-up interface permissions, floating window display permissions, and permissions to obtain device actions and directions, thereby achieving a complete blockade of the application's advertising behavior.
[0085] In this way, the mechanism of target interface elements can be precisely targeted, with different permissions corresponding to different technical principles of target interface elements, ensuring the effectiveness and pertinence of control measures.
[0086] Optionally, the method further includes: The interface displaying control options provides an entry point for deleting source applications.
[0087] For example, continuing with the example above, the smart terminal can also provide a red "Uninstall this application" link in the interface displaying control options. When the user confirms that the application is malicious or no longer needed, they can directly click this link. The smart terminal will then display a standard uninstallation confirmation dialog box. After the user confirms, the smart terminal will immediately uninstall the "Shopping Assistant" application.
[0088] This provides the most thorough control method, which is particularly suitable for dealing with stubborn malicious adware applications. Users can complete the entire process from identification to uninstallation without leaving the current context, further improving the user experience. Optionally, before step S1, the following steps are included: Based on predefined blacklists and whitelists, default restrictions are imposed on the background pop-up permissions of at least some applications.
[0089] Optionally, administrators can predefine an application blacklist and whitelist. For example, known commonly used utility applications (such as calculators and calendars) can be added to the whitelist, allowing them to use background pop-up permissions normally, while known ad-push applications (such as certain cleaning apps and battery optimization apps) can be added to the blacklist. When a user installs a new application, the smart device checks if the application is on the blacklist. If so, its background pop-up permission can be automatically disabled without requiring manual setting by the user. In this way, even if a user accidentally installs a malicious application, it cannot harass the user through background pop-ups.
[0090] In this way, smart terminals can proactively protect themselves through blacklist and whitelist mechanisms, reducing the probability of users encountering interference and further improving the user experience.
[0091] Based on the same inventive concept as the foregoing embodiments, taking a mobile phone as the smart terminal and an advertising pop-up as the target interface element as an example, the specific implementation process of the processing method provided in this embodiment is illustrated below through a specific example.
[0092] In actual use of smart terminals, users may encounter various situations that lead to malicious pop-up ads. For example, application A may contain redirect or pop-up ads. During normal use, users may accidentally tap or click fraudulently, causing the ads to appear. In this case, the close button may be hidden, requiring the user to watch for a certain amount of time before closing. Application B may be on the blacklist for background pop-up permissions and normally controlled. However, while using application B, the application may pop up a pop-up requesting permission. If the user grants this permission without knowing that it will lead to a pop-up, it becomes difficult for the user to find the original function settings and restore normal settings. Application C may be a malicious application that is not on the blacklist or whitelist for background pop-up permissions. When application C is in the background, it can directly launch malicious pop-ups. Since the user is currently using other applications, it is difficult to find the source application of the malicious pop-up.
[0093] To address the above issues, this embodiment provides a method to display control options for the source application of the ad pop-up when a preset operation is received (in this embodiment, the pop-up catcher icon is triggered). After seeing the ad pop-up, the user can pull down the control center, click the pop-up catcher icon, scan the current foreground pop-up and its source application, and after the scan is complete, a pop-up window will appear to inform the user of the source information. At this time, the user can choose to quickly control the permissions of the application, or choose to go to the application details to learn more and delete the application.
[0094] The specific operation flow of the processing method provided in this embodiment includes: First, the smart terminal sets default device action and orientation permissions, as well as background pop-up interface permissions, for each application based on blacklists and whitelists. Optionally, the smart terminal can integrate various advertising permissions into a single menu bar, including permissions for obtaining device action and orientation, background pop-up interface permissions, and pop-up capture, such as... Figure 5 As shown, this is to help users manage quickly.
[0095] Next, when the user clicks to enter an application, a "shake" ad appears on the splash screen of the smart terminal. However, because the application is set to block access to the device's motion permissions, the smart terminal prompts the user that "shake ad is being blocked".
[0096] Next, if the user still accidentally clicks on the ad, since the app has been set to disable background pop-up windows, the smart terminal can display a pop-up window asking the user if they want to switch to the app.
[0097] Next, if the user clicks to cancel the redirect, but the application requests permission to use the background pop-up interface while the user is using the application, the user then closes the application.
[0098] Next, when a user opens another application, but that application displays an interstitial ad (i.e., a malicious ad page) without a close button, forcing the user to view it, the user can pull down the control center and click the pop-up catcher icon. This allows the smart device to scan the foreground page (foreground pop-up) and the source application, finding the source application so the user can perform secondary permission control through the displayed management options. For example, when the user clicks the displayed management permissions option, the smart device jumps to a permission management interface displaying permissions for setting background pop-up interface permissions, and when the user clicks the displayed uninstall option, the smart device jumps to the application details uninstall interface, such as... Figure 6 As shown.
[0099] The above methods can solve the problem of malicious ads in third-party mobile applications, preventing disruptive user experiences caused by such ads. Simultaneously, the device's ad control functions are integrated and adapted, providing solutions for hiding ads or forging close buttons, and offering users a quick way to manage secondary permissions. The examples listed above are for reference only. To avoid redundancy, they will not be listed one by one here. In actual development or application, they can be flexibly combined according to actual needs. However, any combination belongs to the technical solution of this application and is covered by the protection scope of this application.
[0100] This application also provides a smart terminal, including a memory and a processor. The memory stores a processing program, and when the processing program is executed by the processor, it implements the processing method in any of the above embodiments.
[0101] This application also provides a storage medium storing a processing program, which, when executed by a processor, implements the processing method in any of the above embodiments.
[0102] In the embodiments of the smart terminal and storage medium provided in this application, all the technical features of any of the above-described processing method embodiments may be included. The extended and explained contents of the specification are basically the same as the embodiments of the above methods, and will not be repeated here.
[0103] This application also provides a computer program product, which includes computer program code. When the computer program code is run on a computer, it causes the computer to perform the methods described in the various possible implementations above.
[0104] This application also provides a chip, including a memory and a processor. The memory is used to store a computer program, and the processor is used to call and run the computer program from the memory, so that a device with the chip installed performs the methods described in the various possible implementations above.
[0105] It is understood that the above scenarios are merely examples and do not constitute a limitation on the application scenarios of the technical solutions provided in the embodiments of this application. The technical solutions of this application can also be applied to other scenarios. For example, as those skilled in the art will know, with the evolution of system architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.
[0106] The sequence numbers of the embodiments in this application are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.
[0107] The steps in the method of this application embodiment can be adjusted, combined, or deleted according to actual needs.
[0108] The units in the device of this application embodiment can be merged, divided, and deleted according to actual needs.
[0109] In this application, the same or similar terms, concepts, technical solutions and / or application scenario descriptions are generally described in detail only when they appear for the first time. When they appear again, they are generally not repeated for the sake of brevity. When understanding the technical solutions and other contents of this application, the same or similar terms, concepts, technical solutions and / or application scenario descriptions that are not described in detail later can be referred to their previous relevant detailed descriptions.
[0110] In this application, the descriptions of the various embodiments have different focuses. For parts that are not described in detail or recorded in a certain embodiment, please refer to the relevant descriptions of other embodiments.
[0111] The technical features of the present application can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of the present application.
[0112] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) as described above, and includes several instructions to cause a terminal device (which may be a mobile phone, computer, server, controlled terminal, or network device, etc.) to execute the methods of each embodiment of this application.
[0113] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, as a computer program product. A computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the flow or function according to the embodiments of this application is generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a storage medium or transmitted from one storage medium to another. For example, computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line) or wireless (e.g., infrared, wireless, microwave, etc.) means. The storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium (e.g., floppy disk, storage disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid state disk (SSD)).
[0114] The above are merely preferred embodiments of this application and do not limit the patent scope of this application. Any equivalent structural or procedural transformations made using the content of this application's specification and drawings, or direct or indirect applications in other related technical fields, are similarly included within the patent protection scope of this application.
Claims
1. A processing method applied to a smart terminal, characterized in that, Including the following steps: S1. In response to the fulfillment of a preset trigger condition, display control options for the target interface element and / or the source application of the target interface element; the target interface element is the interface element currently displayed on the foreground application.
2. The method as described in claim 1, characterized in that, Before step S1, the following are included: In response to the triggering operation of the management and control integration settings control, a management and control integration settings interface is displayed. The management and control integration settings interface includes settings entry points for at least one of the following functions: prohibiting applications from obtaining device action permissions, prohibiting applications from background pop-up permissions, and enabling the system to automatically generate a close button for target interface elements. In response to any setting operation performed on any setting entry in the integrated management and control settings interface, the activation status of the corresponding function is updated.
3. The method as described in claim 1, characterized in that, The target interface elements include at least one of the following: pop-up window, full-screen overlay interface, and floating window.
4. The method according to any one of claims 1 to 3, characterized in that, The target interface element is an interface that is not actively triggered by the current foreground application.
5. The method according to any one of claims 1 to 3, characterized in that, The control options include an executable entry point for triggering at least one of the following operations: Close the operation entry point of the target interface element; The entry point for setting permissions related to interface display for the source application; The system will redirect you to the access point for the permission management page of the source application mentioned in the system settings.
6. The method as described in claim 5, characterized in that, The permission settings related to interface display include the setting of at least one of the following permissions: background pop-up interface permission, floating window display permission, and permission to obtain device actions and orientation.
7. The method as described in claim 1, characterized in that, The method further includes: The interface displaying the control options provides an entry point for deleting the source application.
8. The method as described in claim 1, characterized in that, Before step S1, the following are included: Based on predefined blacklists and whitelists, default restrictions are imposed on the background pop-up permissions of at least some applications.
9. A smart terminal, characterized in that, include: A memory and a processor, wherein the memory stores a processing program, and the processing program, when executed by the processor, implements the processing method as described in any one of claims 1 to 8.
10. A storage medium, characterized in that, The storage medium stores a processing program, which, when executed by a processor, implements the processing method as described in any one of claims 1 to 8.