Application message notification control method and system, storage medium and equipment

Abstract

The invention provides an application message notification management and control method and system, a storage medium and equipment, and the method comprises the steps: setting and storing an application message control list which comprises preset applications and corresponding message notification permissions; the application state of the system foreground is monitored in real time and / or periodically; judging whether a current foreground application is in the application message control list or not; and dynamically adjusting the message notification permission according to a judgment result. By presetting the application message control list and monitoring the foreground application state in real time, the message notification permission of the system can be automatically adjusted during the running period of the specific application, so that the tedious operation of repeatedly and manually setting the message notification permission by a user is avoided, and intelligent and accurate control on message notification is realized.

Description

Technical Field

[0001] This invention relates to the field of communication technology, and in particular to an application message notification management method, system, storage medium, and device. Background Technology

[0002] With the widespread use of smartphones, users often need to avoid being disturbed by notifications from other applications while using certain apps (such as watching videos or using navigation), but at the same time, they want to retain important notifications from specific apps (such as work communication software). Currently, mainstream mobile operating systems (such as iOS and Android) offer the solution of manually controlling notification permissions for each app through system settings. However, this solution has significant drawbacks: users need to manually disable notification permissions for numerous other apps before each use of a specific app, and then restore these settings one by one after use, making the process cumbersome and repetitive.

[0003] Traditional message notification management methods fail to meet users' needs for contextualized and intelligent message control. Especially in driving scenarios, users often need to retain navigation app prompts and important messages from work communication software (such as Lark and DingTalk) while blocking distracting notifications from other applications. However, frequently and manually switching notification permissions for numerous applications not only degrades the user experience but may also hinder timely access to important information due to operational inconvenience. Therefore, a solution that can automatically manage application message notifications based on usage scenarios is urgently needed. Summary of the Invention

[0004] The purpose of this invention is to solve the problem in the prior art where users need to repeatedly manually adjust message notification permissions during application operation.

[0005] A first aspect of the present invention provides an application message notification control method, comprising:

[0006] Set and store an application message control list, which includes preset applications and their corresponding message notification permissions;

[0007] Real-time and / or periodic monitoring of the application status in the system front end;

[0008] Determine if the currently foreground application is in the application message control list;

[0009] Message notification permissions are dynamically adjusted based on the assessment results.

[0010] Furthermore, the periodic monitoring of the application status in the system foreground also includes monitoring when the system is woken up during foreground / background switching.

[0011] Furthermore, the message notification permissions in the application message control list include:

[0012] Identification information that allows receiving message notifications;

[0013] Identifier information for disabling message notifications.

[0014] Furthermore, the dynamic adjustment of message notification permissions based on the judgment result includes:

[0015] When it is determined that the current foreground application is in the application message control list, read and execute the application's preset message control permissions;

[0016] When it is determined that the current foreground application is not in the application message control list, restore the system's default message notification settings;

[0017] When executing the application's preset message control permissions, only applications set in the application's message control list are allowed to receive message notifications.

[0018] Furthermore, if a new application is added to the application message control list, the message control permissions of the new application are initialized and then manually enabled; the initialization operation includes disabling all message notification permissions of the new application.

[0019] Furthermore, it also includes:

[0020] Monitor the application's foreground / background switching status;

[0021] The judgment and permission adjustment steps are re-executed when an application switch is detected.

[0022] A second aspect of the present invention provides an application message notification management system, comprising:

[0023] The settings module is used to configure and store the application message control list;

[0024] The monitoring module is used to periodically monitor the status of the system's front-end applications.

[0025] The judgment module is used to determine whether the current foreground application is in the application message control list;

[0026] The control module is used to dynamically adjust message notification permissions based on the judgment results.

[0027] Furthermore, it also includes:

[0028] The data storage module is used to store the application message control list;

[0029] The state switching module is used to handle application foreground / background switching events.

[0030] A third aspect of the present invention provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the steps of the application message notification control method as described in any of the preceding claims.

[0031] A fourth aspect of the present invention provides an electronic device comprising:

[0032] processor;

[0033] Memory;

[0034] A computer program stored in the memory and executable on the processor, which, when executed by the processor, implements the steps of the application message management notification method as described in any of the preceding claims.

[0035] Compared with existing technologies, the present invention has at least the following beneficial effects: by pre-setting an application message control list and monitoring the status of foreground applications in real time, the system message notification permissions can be automatically adjusted during the operation of specific applications. This avoids the tedious operation of users repeatedly setting message notification permissions manually, and realizes intelligent and precise control of message notifications. This allows users to receive only preset important message notifications when using specific applications, effectively improving the user experience. It is particularly suitable for use scenarios such as driving navigation and video viewing that require focus and do not want to be disturbed by unnecessary messages. Attached Figure Description

[0036] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on the provided drawings without creative effort.

[0037] Figure 1 This is a flowchart of a message notification control method in one embodiment of the present invention;

[0038] Figure 2 This is a flowchart illustrating the message notification control method in one embodiment of the present invention. Detailed Implementation

[0039] The present invention will now be described in more detail with reference to the accompanying drawings, which illustrate preferred embodiments of the invention. It should be understood that those skilled in the art can modify the invention described herein while still achieving its advantageous effects. Therefore, the following description should be understood as being broadly known to those skilled in the art and is not intended to limit the invention.

[0040] It should be noted that, in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, 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 process, method, article, or apparatus.

[0041] The invention is described more specifically by way of example in the following paragraphs with reference to the accompanying drawings. The advantages and features of the invention will become clearer from the following description. It should be noted that the drawings are in a very simplified form and use non-precise proportions, and are only used to facilitate and clarify the illustration of the embodiments of the invention.

[0042] Example 1

[0043] This embodiment provides a method for managing application message notifications. Please refer to [link / reference]. Figures 1-2 ,include:

[0044] Set up and store an application message control list, which includes preset applications and their corresponding message notification permissions.

[0045] Real-time and / or periodic monitoring of the application status in the system front end.

[0046] Determine if the current foreground application is in the application message control list.

[0047] Message notification permissions are dynamically adjusted based on the assessment results.

[0048] First, setting up and storing the application message control list can be achieved by creating a configuration file in the device's local storage, recording the mapping relationship between application package names and notification permissions. Notification permissions can be represented using binary flags, such as 1 for allowing notifications and 0 for disabling them. Furthermore, this list can be edited through a graphical user interface, allowing users to customize the scope of applications that need to be controlled.

[0049] Secondly, the system is awakened for monitoring when switching between foreground and background. There is already a real-time monitoring mechanism, and the periodic monitoring frequency can be set to 5 seconds or more to balance performance overhead and response speed.

[0050] Secondly, determining whether the current foreground application is in the application message control list requires string matching of the application package name. To improve efficiency, the package names in the control list can be pre-constructed as a hash table structure. When an application switching event is detected, a hash lookup can be used for quick determination.

[0051] Finally, dynamically adjusting message notification permissions based on the judgment results involves modifying the system's notification manager settings. When the application exists in the control list, the preset permissions are applied directly; when the application does not exist, the system's default notification settings interface is called to restore them.

[0052] By automating the monitoring of foreground application status and dynamically adjusting notification permissions, this solution solves the problem of users needing to frequently manually modify notification settings. First, it achieves automated control based on usage scenarios, requiring no user intervention. Second, a periodic monitoring mechanism ensures the timeliness of permission adjustments. Finally, a preset control list preserves the user's autonomy in selecting notifications for critical applications. This solution is particularly suitable for scenarios requiring focused use of specific applications, such as automatically blocking unnecessary notifications during navigation or video playback while maintaining notifications for important communication applications.

[0053] Furthermore, the periodic monitoring of the application status in the system foreground also includes monitoring when the system is woken up during foreground / background switching.

[0054] Specifically, the monitoring function is activated immediately when the application switches from the background to the foreground or vice versa, instead of waiting for the next periodic monitoring time. One implementation method is to register a system-level event listener. This allows for permission checks and adjustments the instant the application state changes, avoiding the delays that can occur with periodic monitoring.

[0055] By capturing foreground / background switching events to trigger the monitoring mechanism, the potential real-time limitations of periodic monitoring are resolved. Since it doesn't require waiting for the next monitoring cycle, permissions can be adjusted immediately upon changes in application status, thus more accurately matching the user's current usage scenario. Compared to existing technologies, this event-driven monitoring method significantly improves the response speed and accuracy of message management, especially in scenarios where users frequently switch applications.

[0056] Furthermore, the message notification permissions in the application message control list include:

[0057] Identification information that allows receiving message notifications.

[0058] Identifier information for disabling message notifications.

[0059] Specifically, the "Allow" notification flag is used to mark an application as having permission to receive notifications in a specific scenario, while the "Disallow" notification flag is used to mark applications that need to block notifications. These two flags can be implemented using binary flags, where "1" indicates permission and "0" indicates disallowment. Alternatively, the flags can be defined as an enumeration type, containing "ALLOW" and "DENY" status values. In practice, these flags can be stored in a database table, with one record per application, containing the application package name and permission status fields.

[0060] By explicitly defining two message notification permission identifiers, fine-grained control over application message notifications is achieved. The "Allow to receive" identifier ensures timely delivery of important messages from critical applications, while the "Deny to receive" identifier effectively blocks distracting notifications from unnecessary applications. Compared to the single notification on / off settings in existing technologies, this dual-identifier mechanism more precisely meets the differentiated needs of users in various usage scenarios. Especially in scenarios where it's necessary to simultaneously retain notifications from some applications and block other distractions, it eliminates the need for users to manually adjust application notification permissions one by one, significantly improving the efficiency and convenience of message management.

[0061] Furthermore, the dynamic adjustment of message notification permissions based on the judgment result includes:

[0062] When it is determined that the current foreground application is in the application message control list, the preset message control permissions of that application are read and executed.

[0063] If it is determined that the current foreground application is not in the application message control list, restore the system's default message notification settings.

[0064] Specifically, reading and executing the application's preset message control permissions can be achieved as follows: the system calls the query interface of the message control list to obtain the permission identifier field corresponding to the current application, and triggers the corresponding system-level notification management API based on the value of this field. For example, when the permission identifier is "Allowed," the restriction is lifted; when the identifier is "Denyed," the relevant notifications are intercepted. Restoring default settings can be done by clearing the permission override flag of the current process, allowing the system to revert to the user-preset global notification policy.

[0065] To address this, a dynamic permission adjustment mechanism effectively solves the problem of frequent manual switching required by traditional static notification management. Compared with existing technologies, it achieves precise, scenario-based notification management without user intervention, especially in scenarios requiring focus, such as driving. It can both block distracting notifications and ensure that important information is not missed.

[0066] Furthermore, when executing the application's preset message control permissions, only applications set in the application's message control list are allowed to receive message notifications.

[0067] Specifically, by limiting the scope of message notification permissions, only applications explicitly specified in the control list can receive message notifications. The execution process of message control permissions can include: first, checking if the current application exists in the control list's allowed message notification identifiers; if it exists, maintaining the application's message receiving function; if it does not exist, immediately blocking its message receiving channel. As a preferred implementation, this can be achieved by modifying the filtering rules of the system notification service, specifically by dynamically adding a whitelist filtering mechanism based on application package names in the system notification manager. Another possible implementation is to intercept system broadcast events and perform an application package name matching check before the message reaches the notification bar. By precisely controlling the scope of message notification reception, the problem of selective message reception in specific scenarios, which cannot be achieved by traditional manual settings, is effectively solved.

[0068] Furthermore, if a new application is added to the application message control list, the message control permissions of the new application are initialized and then manually enabled; the initialization operation includes disabling all message notification permissions of the new application.

[0069] Specifically, when system administrators or users need to manage messages for a new application, they first add the application to the application message control list. Adhering to a "security first" principle, the system immediately performs an initialization operation after adding a new application. This operation automatically disables all message notification permissions for the new application, including but not limited to banner notifications, sound alerts, application badges, and all other notification-related functions. This default disabling design effectively prevents new applications from sending potentially intrusive notifications without proper configuration.

[0070] After initialization, administrators need to manually configure the application's notification permissions precisely. This "disable first, configure later" double-confirmation mechanism not only ensures the controllability and security of message management but also gives administrators ample time to evaluate and set appropriate notification permissions. For example, they can selectively enable only important notification types or set notification permissions for specific time periods, thereby achieving granular message management.

[0071] Furthermore, it also includes:

[0072] Monitor the application's foreground / background switching status.

[0073] The judgment and permission adjustment steps are re-executed when an application switch is detected.

[0074] Specifically, monitoring the foreground / background switching state of an application can be achieved by registering system-level event listeners. For example, in Android, this can be done through the Activity Manager to listen for changes in the application stack, while in iOS, it can be done through the Notification Center to listen for application activation notification events. When an application switching event is detected, the system immediately triggers the foreground application judgment process, re-queries the application message control list, and executes the corresponding permission adjustment operation. Alternatively, state monitoring can be achieved by periodically checking the package name or application identifier of the currently active window using a polling method.

[0075] By responding to application switching events in real time, the system solves the problem of traditional static permission settings being unable to adapt to dynamic usage scenarios. When users quickly switch between different applications (e.g., alternating between navigation and communication applications), the system can automatically maintain a message notification strategy that matches the current usage scenario, without requiring manual user intervention. This dynamic adjustment mechanism is particularly suitable for scenarios that require frequent application switching but demand precise control over message interference, such as using navigation and communication tools simultaneously while driving. By binding permission judgments to system events, both the real-time nature of permission control and the resource consumption caused by continuous polling are ensured.

[0076] Example 2

[0077] A second aspect of the present invention provides an application message notification management system, comprising:

[0078] The settings module is used to configure and store the application message control list.

[0079] The monitoring module is used to monitor the status of the system's front-end applications in real time and / or periodically.

[0080] The judgment module is used to determine whether the current foreground application is in the application message control list.

[0081] The control module is used to dynamically adjust message notification permissions based on the judgment results.

[0082] Specifically, the settings module can receive user input through a graphical user interface and store preset applications and their corresponding message notification permissions in a structured data table. The monitoring module can use system-level APIs to obtain the package name or process information of the currently foreground application and trigger a periodic polling mechanism via a timer. The judgment module queries the application message control list to match the identifier information of the currently foreground application. The control module calls the system notification management interface based on the matching results to dynamically enable or disable message notification permissions for specific applications. The data storage module can persistently save configuration information using an SQLite database or key-value pair storage. The state switching module registers a system broadcast receiver to listen for application foreground / background switching events and trigger subsequent processing flows.

[0083] The modular design enables automated management of application messages. The system can monitor the foreground application status in real time and dynamically adjust message notification behavior based on predefined permission rules, avoiding the tediousness of manual user operations. The combination of periodic monitoring and an event-driven mechanism ensures timely permission adjustments while reducing system resource overhead. Furthermore, the modular architecture facilitates feature expansion and maintenance, such as supporting multi-scenario policy switching or third-party application integration. This solution effectively addresses users' differentiated message notification management needs in specific usage scenarios, improving operational convenience and user experience.

[0084] Furthermore, it also includes:

[0085] The data storage module is used to save the application message control list.

[0086] The state switching module is used to handle application foreground / background switching events.

[0087] Specifically, when an application is detected to switch from the background to the foreground or vice versa, the monitoring module is triggered to re-evaluate whether the currently foreground application is in the application message control list, and the control module is triggered to dynamically adjust message notification permissions based on the evaluation result. The data storage module can be implemented in various ways, such as using an SQLite database to store the application message control list or using an XML file format. The state switching module can be implemented by registering a system broadcast receiver.

[0088] By adding dedicated data storage and state switching modules, the persistent storage of the application message control list and the real-time response during application state transitions were resolved. The data storage module ensures the application message control list remains valid even after a system restart, while the state switching module promptly triggers permission adjustment processes when the application state changes, avoiding the cumbersome manual operation required by traditional solutions. This achieves automated management of application message notification permissions, maintaining real-time and accurate message control, especially in scenarios with frequent application switching.

[0089] Example 3

[0090] A third aspect of the present invention provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the steps of the application message notification control method as described in Embodiment 1.

[0091] Specifically, the computer-readable storage medium can be a non-volatile storage medium such as ROM, RAM, flash memory, hard disk, or solid-state drive. When a computer program is executed by the processor, it first loads an application message control list, which contains preset applications and their corresponding message notification permission settings. Then, by periodically monitoring the status of foreground applications, it determines whether the currently foreground application is in the application message control list. Based on the determination result, message notification permissions are dynamically adjusted: if the application is in the list, the preset message control permissions are read and executed; if it is not in the list, the system's default message notification settings are restored. As a preferred implementation, the monitoring process is activated when the system switches between foreground and background processes.

[0092] Example 4

[0093] This embodiment also provides an electronic device, which may be a mobile phone, smartwatch, camera, or other similar device. The electronic device may include: a memory for storing computer-readable instructions; and a processor for executing the computer-readable instructions; wherein, when the computer-readable instructions are executed by the processor, they perform the steps of the application message notification control method as described in Embodiment 1. The specific implementation and technical effects are similar to those in Embodiment 1, and will not be repeated here.

[0094] For ease of explanation, only one processor is described in the above-described electronic device. However, it should be noted that in some embodiments, the electronic device of the present invention may also include multiple processors, and therefore the steps performed by one processor as described in the present invention may also be performed jointly or individually by multiple processors. For example, if the processor of the electronic device performs steps and steps, it should be understood that steps and steps may also be performed jointly by two different processors or individually by one processor. For example, a first processor performs steps, a second processor performs steps, or a first processor and a second processor jointly perform steps, etc.

[0095] In some embodiments, the processor may include one or more processing cores (e.g., a single-core processor (S) or a multi-core processor (S)). By way of example only, the processor may include a Central Processing Unit (CPU), an Application Specific Integrated Circuit (ASIC), an Application Specific Instruction-set Processor (ASIP), a Graphics Processing Unit (GPU), a Physics Processing Unit (PPU), a Digital Signal Processor (DSP), a Field Programmable Gate Array (FPGA), a Programmable Logic Device (PLD), a controller, a microcontroller unit, a Reduced Instruction Set Computing (RISC) computer, or a microprocessor, or any combination thereof.

[0096] The above examples illustrate the present invention only to aid in understanding it and are not intended to limit the scope of the invention. Those skilled in the art can make various simple deductions, modifications, or substitutions based on the principles of this invention.

Claims

1. An application message notification control method, characterized in that, include: Set and store an application message control list, which includes preset applications and their corresponding message notification permissions; Real-time and / or periodic monitoring of the application status in the system front end; Determine if the currently foreground application is in the application message control list; Message notification permissions are dynamically adjusted based on the assessment results.

2. The application message notification control method as described in claim 1, characterized in that, The periodic monitoring of the application status in the system foreground also includes monitoring when the system is woken up during foreground / background switching.

3. The application message notification control method as described in claim 1, characterized in that, The message notification permissions in the application message control list include: Identification information that allows receiving message notifications; Identifier information for disabling message notifications.

4. The application message notification control method as described in claim 1, characterized in that, The dynamic adjustment of message notification permissions based on the judgment result includes: When it is determined that the current foreground application is in the application message control list, read and execute the application's preset message control permissions; When it is determined that the current foreground application is not in the application message control list, restore the system's default message notification settings; When executing the application's preset message control permissions, only applications set in the application's message control list are allowed to receive message notifications.

5. The application message notification control method as described in claim 4, characterized in that, If a new application is added to the application message control list, the message control permissions of the new application are initialized and then manually enabled; the initialization operation includes disabling all message notification permissions of the new application.

6. The application message notification control method as described in claim 1, characterized in that, Also includes: Monitor the application's foreground / background switching status; The judgment and permission adjustment steps are re-executed when an application switch is detected.

7. An application message notification control system, characterized in that, include: The settings module is used to configure and store the application message control list; The monitoring module is used to periodically monitor the status of the system's front-end applications. The judgment module is used to determine whether the current foreground application is in the application message control list; The control module is used to dynamically adjust message notification permissions based on the judgment results.

8. The system as described in claim 7, characterized in that, Also includes: The data storage module is used to store the application message control list; The state switching module is used to handle application foreground / background switching events.

9. A computer-readable storage medium, characterized in that, The storage medium stores a computer program, which, when executed by a processor, implements the steps of the application message notification control method as described in any one of claims 1-6.

10. An electronic device, characterized in that, include: processor; Memory; A computer program stored in the memory and executable on the processor, wherein when executed by the processor, the computer program implements the steps of the application message notification control method as described in any one of claims 1-6.

Images