Message reminding method and electronic device

Abstract

The application discloses a message reminding method and an electronic device. The electronic device can support a user to select a system default message allowed to disturb by one key. After a scene mode is started, the electronic device will perform message reminding when receiving the message regardless of whether an application generating the message is an application allowed to disturb. In this way, important messages can be avoided to be missed by the user, and convenient and intelligent use experience is provided for the user while reducing disturbance to the user. Alternatively, messages generated by an application can be classified into multiple types. The electronic device can support the user to select a type of the message allowed to disturb corresponding to the application. After the scene mode is started, the electronic device will perform message reminding only when receiving the message allowed to disturb of the type selected by the user corresponding to the application. In this way, more fine-grained selection experience can be provided for the user while reducing disturbance to the user, and the user can be avoided to miss the message of the selected type.

Description

Technical Field

[0001] This application relates to the field of terminal technology, and in particular to a message notification method and electronic device. Background Technology

[0002] With the rapid development of information technology, more and more applications can be installed on smart electronic devices (such as mobile phones and tablets), and the messages generated by these applications (such as push notifications and SMS messages) are growing exponentially. Living in an era of information overload, people's attention is frequently interrupted, and their time is fragmented, which can easily trigger user anxiety.

[0003] Currently, when users need to focus, they usually enable specific modes on their electronic devices (such as Do Not Disturb mode) to avoid being disturbed too much. Users can specify the applications and contacts that can be disturbed. After enabling this mode, the electronic device will only send message notifications (such as sound, vibration, pop-up notifications, etc.) when it receives messages from the specified applications or specified contacts (such as incoming calls), thereby reducing disturbances.

[0004] While this may reduce interruptions, users may easily miss messages in urgent situations (such as food delivery or ride-hailing), which could cause inconvenience and losses for them. Summary of the Invention

[0005] This application provides a message notification method and electronic device that can prevent users from missing important messages while minimizing disturbance to them, thus providing a convenient and intelligent user experience.

[0006] In a first aspect, embodiments of this application provide a message reminder method applied to an electronic device, wherein a first application is installed on the electronic device, the method comprising: the electronic device activating a first scene mode, the first application being an application that should not be disturbed; the electronic device receiving a first message from the first application, the first message including a first identifier, the first identifier being used to indicate that the type of the first message is a first type; the electronic device reminding the user of the first message, wherein the first type belongs to a first preset type.

[0007] Wherein, the first application can be an application installed on an electronic device, the first scenario mode can be a scenario mode created on an electronic device, the first message can be a message generated by the first application, and the first identifier can be an identifier used to indicate the type of the first message.

[0008] By implementing the method provided in the first aspect, when the scenario mode is enabled, the electronic device can remind users of preset types of messages. In this way, while minimizing disturbance to the user, it can prevent the user from missing preset types of messages and provide the user with a convenient and intelligent user experience.

[0009] In one possible implementation, the method further includes: the electronic device receiving a second message from a first application, the second message including a second identifier, the second identifier being used to indicate that the type of the second message is a second type; the electronic device not providing a notification for the second message, wherein the second type does not belong to a first preset type.

[0010] The second message mentioned above can be a different message from the first message.

[0011] In other words, for messages generated by the same application, electronic devices may not only send notifications for all messages or not send notifications at all, but will only send notifications for messages that belong to a preset type, and will not send notifications for messages that do not belong to the preset type.

[0012] In one possible implementation, the first preset type is the default of the electronic device, or the first preset type is selected by the user.

[0013] In the case where the first preset type is the default setting for electronic devices, after enabling the scenario mode, the electronic device will send a message reminder when it receives the message, regardless of whether the application that generated the message is an application that allows interruptions. This can minimize disturbances to the user while preventing the user from missing important messages, providing the user with a convenient and intelligent user experience.

[0014] In the case where the first preset type is selected by the user, after the scenario mode is enabled, the electronic device will only send a message reminder when it receives a message that allows interruptions for the user's selected type. This can provide users with a more granular selection experience while minimizing interruptions and prevent users from missing messages of their selected type.

[0015] In one possible implementation, when the first scenario mode is enabled, the electronic device does not alert the user to any type of message from the first application; when the first scenario mode is disabled, the electronic device alerts the user to any type of message from the first application. Before the electronic device receives the first message from the first application, the method further includes:

[0016] The electronic device detects a first operation, which is used to activate a first function. The first function is used to indicate that when a first scenario mode is activated, a notification of a first preset type of message received from a first application is displayed.

[0017] The first operation mentioned above can be the operation of activating the first function (such as the operation of turning on the smart experience switch option mentioned in the following embodiments), and the first function can be the smart experience function mentioned in the following embodiments.

[0018] In other words, after an electronic device activates a profile mode, if a message belongs to a preset type, the electronic device will still send a notification when it receives the message, even if the application that sent the message is not an application that is allowed to be disturbed, so as to prevent the user from missing important messages.

[0019] In one possible implementation, the electronic device further includes a second application, and the method further includes: the electronic device receiving a third message from the second application, the third message including a third identifier, the third identifier being used to indicate that the type of the third message is a third type; the electronic device providing a reminder about the third message, wherein the third type belongs to a second preset type.

[0020] The second application can be an application installed on the electronic device that is different from the first application. The third message can be a message generated by the second application. The third identifier can be an identifier used to indicate the type of the third message. The second preset type can be different from the first preset type.

[0021] In other words, the types of messages available to users can be different for different applications.

[0022] In one possible implementation, the third message is different from the first message.

[0023] In other words, different applications can generate different messages.

[0024] In one possible implementation, the first message and the third message can be any of the following: SMS message, incoming call message, or live message.

[0025] In one possible implementation, when the message is an SMS message, the SMS message includes an SMS verification code message; when the message is an incoming call message, the incoming call message includes an incoming call message with a preset caller ID, which includes a delivery ID or a ride-hailing ID; when the message is a live message, the live message includes live messages from one or more of the following scenarios: ride-hailing, instant delivery, flights, high-speed rail / trains, queuing, food pickup, sports scores, shared rentals, timing, exercise, and navigation.

[0026] In one possible implementation, the electronic device reminds the user of the first message, specifically by the electronic device reminding the user of the first message through a first reminder method, which includes one or more of sound, vibration, and interface prompts.

[0027] In other words, electronic devices can send notifications in various ways.

[0028] In one possible implementation, the interface prompts include one or more of the following: live window prompts and pop-up prompts.

[0029] In one possible implementation, the first application is a text messaging application. Before the electronic device receives the first message from the first application, the method further includes: the first application receiving the first text message; the first application generating a first message based on the first text message, wherein the first text message does not include a first identifier.

[0030] In one possible implementation, after the first application generates the first message based on the first SMS, the method further includes: the first application generating a first identifier based on the content of the first message.

[0031] In other words, after receiving a text message, the SMS application can process it and generate an identifier to indicate the type of the text message. This identifier is not included in the text message received by the SMS application.

[0032] In one possible implementation, the first application is a live application. Before the electronic device receives the first message from the first application, the method further includes: the first application receiving the first live message; the first application generating a first message based on the first live message, the first live message including a first identifier.

[0033] The live application can be an application that can obtain live messages, as mentioned in the following embodiments. The live messages obtained by the live application will include an identifier that indicates the type of the live message.

[0034] In one possible implementation, the electronic device includes a message management service module. The electronic device receives a first message from a first application. Specifically, the message management service module receives the first message from the first application. Before the electronic device alerts the user to the first message, the method further includes: the message management service module determines the type of the first message as a first type based on a first identifier, and determines that the first type belongs to a first preset type.

[0035] The aforementioned message management service module can be a service module in the operating system of an electronic device. After a message is generated, the application can send the message to the message management service module, which can determine the type of the message in order to decide whether to send a notification.

[0036] In one possible implementation, before the message management service module determines that the type of the first message is a first type based on the first identifier, the method further includes: the message management service module determining that the electronic device has enabled a first scenario mode.

[0037] In other words, the message management service module can monitor in real time whether a certain scenario mode is enabled on the electronic device. Only after the scenario mode is enabled will the message management service module determine the message type of the message sent by the application. Otherwise, the message management service module will not determine the message type of the message sent by the application.

[0038] In one possible implementation, the electronic device further includes a message reminder module, which reminds the user of the first message. Specifically, the message reminder module receives a fourth message sent by the message management service module; and the message reminder module reminds the user of the first message based on the fourth message.

[0039] The aforementioned message notification module can be, for example, a system application on an electronic device (such as a notification center).

[0040] In other words, when the message management service module determines that a certain message needs to be reminded, it can instruct the message reminder module to remind the message.

[0041] In a second aspect, embodiments of this application provide a chip system, including: a processor coupled to a memory, the memory being used to store programs or instructions, and when the program or instructions are executed by the processor, causing the chip system to perform the method described in any possible implementation of the first aspect above.

[0042] Thirdly, embodiments of this application provide an electronic device including one or more processors and one or more memories; wherein the one or more memories are coupled to the one or more processors, and the one or more memories are used to store computer program code, the computer program code including computer instructions, which, when the one or more processors execute the computer instructions, cause the electronic device to perform the method described in any possible implementation of the first aspect above.

[0043] Fourthly, embodiments of this application provide a computer storage medium storing a computer program, the computer program including program instructions that, when executed on an electronic device, cause the electronic device to perform the method described in any possible implementation of the first aspect above.

[0044] Fifthly, embodiments of this application provide a computer program product that, when run on a computer, causes the computer to perform the method described in any possible implementation of the first aspect above. Attached Figure Description

[0045] Figures 1A-1CThis is a schematic diagram illustrating a set of live view windows provided in an embodiment of this application;

[0046] Figure 1D This is a schematic diagram illustrating a method for notifying users of SMS messages according to an embodiment of this application;

[0047] Figures 1E-1F This is a schematic diagram illustrating a call notification method provided in an embodiment of this application;

[0048] Figure 1G This is a flowchart illustrating a common message notification method;

[0049] Figure 2 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application;

[0050] Figure 3 This is a flowchart illustrating a message notification method provided in an embodiment of this application;

[0051] Figures 4A-4G These are a set of user interface diagrams related to the message notification method provided in the embodiments of this application;

[0052] Figure 5 This is a schematic diagram illustrating a possible interaction flow between different modules involved in a message notification method provided in this application embodiment;

[0053] Figure 6 This is a flowchart illustrating a message notification method using SMS and live messages as examples, provided in an embodiment of this application.

[0054] Figure 7 This is a schematic diagram of a user interface involved in the message notification method provided in the embodiments of this application;

[0055] Figures 8A-8B This is another set of user interface diagrams related to the message notification method provided in the embodiments of this application;

[0056] Figure 9 This is a flowchart illustrating another message notification method provided in an embodiment of this application;

[0057] Figures 10A-10F This is another set of user interface diagrams related to the message notification method provided in the embodiments of this application;

[0058] Figure 11 This is a schematic diagram illustrating another possible interaction flow between different modules involved in a message notification method provided in an embodiment of this application;

[0059] Figure 12 This is a flowchart illustrating another message notification method using SMS and live messages as examples, provided in an embodiment of this application.

[0060] Figure 13 This is a schematic diagram of the software structure of an electronic device provided in an embodiment of this application;

[0061] Figure 14 This is a schematic diagram of the hardware structure of an electronic device provided in an embodiment of this application. Detailed Implementation

[0062] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. In the description of the embodiments of this application, unless otherwise stated, " / " means "or," for example, A / B can mean A or B; "and / or" in the text is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, and B existing alone. Furthermore, in the description of the embodiments of this application, "multiple" refers to two or more than two.

[0063] It should be understood that the terms "first," "second," etc., in the specification, claims, and drawings of this application are used to distinguish different objects, not to describe a specific order. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or apparatus that includes a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units not listed, or may optionally include other steps or units inherent to these processes, methods, products, or apparatuses.

[0064] In this application, the reference to "embodiment" means that a specific feature, structure, or characteristic described in connection with an embodiment may be included in at least one embodiment of this application. The appearance of this phrase in various places throughout the specification does not necessarily refer to the same embodiment, nor is it a mutually exclusive, independent, or alternative embodiment. It will be explicitly and implicitly understood by those skilled in the art that the embodiments described in this application can be combined with other embodiments.

[0065] The term "user interface (UI)" used in the following embodiments of this application refers to the medium interface through which an application or operating system interacts and exchanges information with the user. It realizes the conversion between the internal form of information and the form that the user can accept. The user interface is source code written in a specific computer language such as Java or Extensible Markup Language (XML). The interface source code is parsed and rendered on the electronic device, ultimately presenting content that the user can recognize. A common form of user interface is the graphical user interface (GUI), which refers to a user interface related to computer operation displayed graphically. It can be visible interface elements such as text, icons, buttons, menus, tabs, text boxes, dialog boxes, status bars, navigation bars, and widgets displayed on the screen of an electronic device.

[0066] For ease of understanding, some concepts involved in the embodiments of this application are introduced below.

[0067] 1. Scenario Mode

[0068] Context mode (also known as focus mode) is a feature setting on electronic devices that can block or limit messages generated by applications on the device (such as push notifications, SMS messages, incoming calls, etc.) to help users reduce distractions and improve their focus in specific scenarios.

[0069] Scenario modes can include various modes, such as work mode, sports mode, study mode, sleep mode, game mode, driving mode, and audio-visual mode.

[0070] Typically, when setting up a scenario mode, electronic devices allow users to select specific applications and / or contacts (i.e., applications and / or contacts that are allowed to be disturbed). In this way, after the scenario mode is enabled, the electronic device will only send message notifications (such as sound, vibration, pop-up notifications, etc.) when it receives messages from the specified applications or specified contacts (such as incoming call messages).

[0071] Electronic devices can support users in setting corresponding scenario modes based on the situation. When in a certain scenario, users can activate the corresponding scenario mode, and the designated applications and / or contacts can also be different in different scenario modes. For example, in a work scenario, a work mode can be activated, in which the designated applications are usually office applications, and the designated contacts are usually colleagues; as another example, in a sports scenario, a sports mode can be activated, in which the designated applications are usually sports and health applications, and the designated contacts are usually fitness friends / coaches, family members, etc.

[0072] The scenario mode can be manually activated by the user or automatically activated by the electronic device. For example, a user can click the activation option of a scenario mode to trigger the electronic device to activate that scenario mode; or, the electronic device can automatically activate a scenario mode when it detects that a preset trigger condition for a scenario mode is met. The preset trigger condition may include, but is not limited to, location, time, application usage, user physiological indicators, etc., and different scenario modes may have different preset trigger conditions.

[0073] In this embodiment of the application, after the electronic device activates the scenario mode, it can not only send message reminders when it receives messages from designated applications or contacts, but also send message reminders when it receives messages in certain specific scenarios (such as food delivery, ride-hailing, package pickup, loan repayment, flight, and other emergency scenarios), regardless of whether the application that generated the message is allowed to be disturbed, thereby preventing users from missing important information.

[0074] The specific setup process and internal implementation will be described in detail in subsequent embodiments, and will not be elaborated here.

[0075] 2. Message

[0076] Messages (also known as notifications or notification messages) can come in many types. Generally, messages can be categorized into social communication messages, service reminder messages, and informational / marketing messages.

[0077] Social communication messages can include instant messaging messages, audio calls, and video calls.

[0078] Service reminder messages can include subscription, travel, health, work reminders, account activity, order & logistics, financial, email, device status reminders, alarm / timer reminders, progress reminders, location sharing, and other messages.

[0079] Information marketing messages can include event information, content recommendations, news, etc., sent by operations personnel to users.

[0080] The message can be generated by a system application or a third-party application. A system application can be an application developed by the device manufacturer and installed in the device, while a third-party application can be an application provided by an application developer other than the device manufacturer.

[0081] Typically, social communication messages and service notifications are more likely to include messages with high real-time requirements, such as SMS verification codes, real-time updates for certain services (e.g., ride-hailing, food delivery), and incoming calls.

[0082] In this embodiment of the application, after the scenario mode is enabled, the electronic device can still send message reminders when it receives messages with high real-time requirements, so as to prevent users from missing key information.

[0083] The embodiments of this application can classify messages into live messages and ordinary messages.

[0084] Live messaging is suitable for a variety of scenarios, including but not limited to the scenarios shown in Table 1 below.

[0085]

[0086] Table 1

[0087] Live notifications can be displayed in the form of a live window. A live window is a notification format that helps users focus on ongoing tasks, allowing for quick viewing and immediate processing. It is characterized by its time-sensitive, timely, and dynamic nature. In terms of display format, live windows can be displayed in locations such as the status bar, notification center, and lock screen, primarily in capsule and card formats.

[0088] For example, taking a ride-hailing scenario, the real-time ride status can be displayed in the status bar. Figure 1A The notification will be displayed in capsule form, and the real-time status of your ride can be viewed in the notification center. Figure 1B The reminder is displayed in card format on the lock screen, showing the real-time taxi status. Figure 1C The system displays reminders in a card-like format. This allows users to see their ride-hailing progress in real-time through a status window, eliminating the need to frequently open the ride-hailing app to check the status, making it convenient and quick.

[0089] Ordinary messages can refer to messages other than live news.

[0090] In this embodiment of the application, messages with high real-time requirements may include live messages and some ordinary messages. These ordinary messages may include, for example, SMS verification code messages and incoming calls in emergency scenarios (such as food delivery or ride-hailing).

[0091] Regular messages can be notified in various ways, such as through sound, vibration, or on-screen notifications. The specific notification method can be either the default setting of the electronic device or manually configured by the user in the system notification management.

[0092] For example, taking the receipt of an SMS verification code message from a short message application as an example, the SMS verification code message can be in the form of... Figure 1D The notification will be displayed as a banner (i.e., a pop-up window). Optionally, it can also be combined with sound and / or vibration for notification.

[0093] For example, taking receiving a delivery call from a phone application as an example, the delivery call can be... Figure 1E The message notification will be sent in the form of a banner (i.e., a pop-up), or... Figure 1F The message notification is displayed in the form of a full-screen incoming call interface. Optionally, it can also be combined with sound and / or vibration for message notification.

[0094] Figure 1G The following is an example illustrating the specific process of a common message notification method. This message notification method may include the following steps:

[0095] S101. The electronic device activates a scene mode, wherein application A and application B are applications that are allowed to be disturbed in this scene mode, and application C and application D are applications that are not allowed to be disturbed in this scene mode.

[0096] S102. The electronic device provides a message notification when it receives messages from application A and application B, but does not provide a message notification when it receives messages from application C and application D.

[0097] S103, Electronic devices turn off scene modes.

[0098] S104. The electronic device will send a message notification when it receives messages from application A, application B, application C, and application D.

[0099] The aforementioned message notifications can be achieved through one or more of the following methods: sound, vibration, and interface prompts (such as pop-ups, live feeds, etc.).

[0100] From the above Figure 1G As shown in the message notification method, after activating the profile mode, electronic devices only send notifications when receiving messages from apps that allow interruptions. This makes it easy to miss messages in urgent situations (such as food delivery or ride-hailing). If users want to avoid missing messages, they need to set all potentially used apps as allowed interruptions, which leads to an increase in messages and reduces the effectiveness of minimizing interruptions. Furthermore, the inability to pre-set unfamiliar contacts (such as delivery drivers or ride-hailing drivers) as allowed interruptions can be inconvenient and result in a poor user experience.

[0101] To address the aforementioned issues, this application provides a message notification method. The electronic device allows users to select the system's default allowed messages with a single click. After enabling the scenario mode, regardless of whether the application generating the message is an allowed application, the electronic device will provide a message notification upon receiving the message. This minimizes user disturbance while preventing users from missing important messages, providing a convenient and intelligent user experience. Alternatively, if application-generated messages can be categorized into multiple types, the electronic device can allow users to select the allowed message type for each application. After enabling the scenario mode, the electronic device will only provide a message notification when it receives an allowed message of the user-selected type for the application. This minimizes user disturbance while providing a more granular selection experience, preventing users from missing messages of their chosen type.

[0102] It should be noted that the electronic devices mentioned in the embodiments of this application may be mobile phones, tablets, personal computers, smartwatches, smart bracelets, etc., and the embodiments of this application do not limit the type of electronic devices.

[0103] The structure of an electronic device provided in the embodiments of this application is described below.

[0104] Figure 2 An exemplary embodiment of the present application provides the structure of an electronic device.

[0105] See Figure 2 Electronic devices may include a settings module, a message initiation module, a message management service module, and a message notification module.

[0106] The settings module can be used to configure the functions of electronic devices.

[0107] The settings module can be a system application, such as a settings application.

[0108] The settings module may include a scenario mode settings module.

[0109] In some embodiments, the scenario mode setting module can also be a standalone application.

[0110] The scenario mode settings module can be used to create one or more scenario modes (such as work mode, exercise mode, study mode, sleep mode, game mode, etc.), and set the applications and contacts that can be disturbed in the corresponding scenario mode.

[0111] In this embodiment, the scenario mode setting module allows users to select preset types of messages that can be disturbed, such as live messages, SMS verification code messages, and incoming calls in emergency scenarios (e.g., food delivery, ride-hailing, etc.). The specific setting process will be described in detail in subsequent embodiments and will not be elaborated here.

[0112] Normally, a message can be generated from the message initiation module and sent to the message management service module via inter-process communication. The message management service module can then distribute the message to the message notification module to provide a notification.

[0113] The message initiation module can be used to generate messages and send them to the message management service module.

[0114] The message initiation module can be a system application (such as SMS, telephone, etc.) or a third-party application.

[0115] In this embodiment, the message initiation module can label the generated message with its type and send the generated message and its corresponding type to the message management service module. This allows the message management service module to determine whether the message belongs to a preset type based on its message type. For example, an SMS verification code message can be labeled as a verification code type; a food delivery call message can be labeled as a delivery type; all real-time messages can be uniformly labeled as a real-time type, regardless of the scenario, or they can be labeled separately according to the specific scenario. For example, a ride-hailing real-time message can be labeled as a ride-hailing real-time type; and a food delivery scenario can be labeled as a food delivery real-time type.

[0116] It should be noted that the message initiation module can mark all types of messages or mark messages of a preset type; this application embodiment does not limit this.

[0117] Taking an SMS application as an example, after receiving an SMS message, the application preprocesses it, such as determining the message type. This can be done based on information like the message content (e.g., a verification code). The type can be marked, for example, by the `msgtype` field (e.g., "=1" indicates a verification code type, "!=1" indicates no verification code type). Further, the preprocessed SMS message is obtained, which may include the message type, marked, for example, by the `actionData` field (e.g., "actionData.isVerCode='true'" indicates a verification code type, "actionData.isVerCode='false'" indicates no verification code type). The SMS application can then send the preprocessed SMS message to a message management service module, which can then determine the message type based on the marked information.

[0118] It's easy to understand that the marking process for other types of SMS messages besides verification codes is similar to the process described above, except that the values ​​of the msgtype and actionData fields will be different, which will not be elaborated here.

[0119] Taking an application that can obtain live messages as an example, after the application obtains the live message, the live message may include one or more fields that indicate the information of the live message (such as source, type, etc.). The application will send the live message to the message management service module so that the message management service module can determine the source, type, etc. of the live message based on the above one or more fields that indicate the information of the live message.

[0120] The message management service module can be used to manage messages generated by the message initiation module. For example, it can receive messages generated by the message initiation module; it can identify the type of message; and it can send messages to the message notification module.

[0121] In this embodiment of the application, the message management service module can also be used to monitor whether a scenario mode is enabled and whether reminders for some preset types of messages are allowed.

[0122] In this embodiment of the application, when the scenario mode is enabled and reminders for some preset types of messages are allowed, when the message management service module receives a message sent by the message initiating module, it can determine whether the message belongs to a preset type of message based on the message type. If it does, the message management service module can instruct the message reminder module to remind the message; if not, the message management service module can instruct the message reminder module not to remind the message.

[0123] In one possible implementation, the message management service module may include a LiveViewManager module and an advanced notification service (ANS) module. The LiveViewManager module can include a message recognition module. This module can determine whether a message belongs to a preset message type based on its type and send the recognition result to the ANS module. The ANS module can monitor whether contextual modes are enabled and whether notifications for certain preset message types are allowed. It can also receive the recognition result from the message recognition module and, based on that result, instruct the message notification module whether to send a notification for that message.

[0124] Taking live messages as an example, ANS can send one or more fields containing information indicating the live message (such as source, type, etc.) to the LiveViewManager module. The LiveViewManager module can then determine the source, type, etc., of the live message based on these fields. For example, if the fields are the type and event fields, the LiveViewManager module can determine the source of the live message (e.g., a third-party application or system application) based on the type field, and determine the type of the live message (e.g., ride-hailing, food delivery, flight, etc.) based on the event field.

[0125] In some embodiments, live messages from different sources can interact with different interfaces and message management service modules.

[0126] The message notification module can be used to provide message notifications when an electronic device receives a message.

[0127] The message notification module can be a system application, such as a notification center.

[0128] For live messages, notifications can be sent via a live view window. Alternatively, notifications can be sent via a combination of sound, vibration, or one or more other methods.

[0129] For regular messages, notification methods can include, but are not limited to, one or more of the following: sound, vibration, and pop-up window.

[0130] It's easy to understand that message notifications can be set by the default settings of electronic devices or manually configured by the user in the system notification management.

[0131] Based on the above Figure 2 The structure of the electronic device shown is described in detail below for Embodiment 1 and Embodiment 2.

[0132] Example 1

[0133] In Example 1, the electronic device allows users to select, with a single click, the allowed message type from the system's default preset settings. The preset types may include, but are not limited to, scenarios with high real-time requirements such as authentication, food delivery, ride-hailing, package pickup, loan repayment, and flights. Messages may include, but are not limited to, SMS, incoming calls, and live notifications. After enabling the scenario mode, the electronic device will send a notification upon receiving the message, regardless of whether the application generating the message is an allowed-distraction application. This minimizes disruption to the user while preventing them from missing important messages, providing a convenient and intelligent user experience.

[0134] Figure 3 The specific flow of a message notification method provided in an embodiment of this application is illustrated by way of example.

[0135] like Figure 3 As shown, this method can be applied to electronic devices. The specific steps of this method are described in detail below:

[0136] S301. The electronic device saves the setting data of Scene Mode 1, which includes the applications that are allowed to be disturbed under Scene Mode 1.

[0137] Specifically, the electronic device can detect the user's operation of setting profile mode 1, and in response to the operation, the electronic device can save the setting data of profile mode 1, which includes the applications that are allowed to be disturbed when profile mode 1 is enabled.

[0138] Among them, Scene Mode 1 can be a scene mode created by the user. Setting Scene Mode 1 can specifically include: setting the name of Scene Mode 1 (such as sports mode), setting the applications that can be disturbed, and setting the contacts that can be disturbed.

[0139] In this embodiment of the application, the electronic device can support users to set scene modes in the settings application.

[0140] For example, see Figure 4A , Figure 4A The user interface 410 shown may be a user interface provided by a settings application, and the user interface 410 may include one or more settings items (e.g., profile setting item 411). The electronic device can detect the user's operation on the profile setting item 411 (e.g., a click operation), and in response to the operation, the electronic device can display... Figure 4B The user interface 420 is shown as an example.

[0141] See Figure 4BThe user interface 420 may include a scenario mode that the user has created, wherein the user has created one or more scenario modes, from... Figure 4B As can be seen, the user has created 5 scene modes, and the current one is the sports mode. The user can swipe left or right to trigger the electronic device to display other scene modes that the user has created; alternatively, the user can click option 425 to trigger the electronic device to display them. Figure 4C The exemplary user interface 430 allows users to view all user-created scenario modes (such as driving mode, work mode, sports mode, game mode, audio-visual mode, etc.).

[0142] See Figure 4C The user interface 430 may also include a custom mode option 431. When the user clicks the custom mode option 431, the electronic device can display a user interface for creating a new scenario mode. Specifically, creating a scenario mode may include: setting the name of the scenario mode (e.g., sports mode), setting the applications that can be disturbed, and setting the contacts that can be disturbed.

[0143] Continue reading Figure 4B The user interface 420 may also include application and meta-service options 422 and contact options 423.

[0144] The electronic device can detect user actions (such as clicks) on application and meta-service options 422, and in response to these actions, the electronic device can display... Figure 4D The exemplary user interface 440 may include one or more applications (e.g., application A, application B, application C, etc.), wherein the selected application may be an application that is allowed to be disturbed. Figure 4D It's easy to see that the app allowed to be disturbed is app A. The electronic device allows the user to manually select one or more apps to be allowed to be disturbed. After selecting the apps to be allowed to be disturbed, the user can click the "Done" option to trigger the electronic device to save the apps allowed to be disturbed in this scenario. See further... Figure 4D Users can click the meta-services option to trigger the display of one or more meta-services on their electronic devices. Similar to selecting allowed applications to be disturbed, electronic devices can also allow users to manually select one or more allowed meta-services to be disturbed. Meta-services can refer to applications that do not require installation, unlike traditional applications that need to be installed. They feature instant access, embedded operation, and efficient development.

[0145] The electronic device can detect the user's action on the contact option 423 (e.g., a click), and in response to that action, the electronic device can display... Figure 4EThe exemplary user interface 450 may include one or more contact setting entries (e.g., block all, allow all, allow only existing contacts, allow only favorited contacts, block only specified contacts, etc.). The electronic device can allow the user to select one of the setting entries to set the contacts allowed to be disturbed in that scenario. After setting, the electronic device can save the list of allowed contacts for that scenario. Figure 4E It's easy to see that the setting selected by the user is to prevent everyone from setting this option. For specific contacts, the user can click... Figure 4E The "Add Contact" option triggers the electronic device to display a user interface for adding a specified contact, allowing the user to perform the action of adding the specified contact within that user interface.

[0146] It's easy to understand that after setting the allowed apps and allowed contacts to be disturbed in a certain scenario mode, if that scenario mode is enabled, the electronic device can send a message reminder when it receives a message from an allowed app, and send a call reminder when it receives a call from an allowed contact.

[0147] S302, The electronic device received message 1.

[0148] S303. The electronic device determines whether scene mode 1 is enabled. If yes, it executes the following step S305; otherwise, it executes the following step S304.

[0149] S304. The electronic device provides a notification for message 1.

[0150] S305. The electronic device determines whether message 1 is generated by an application that allows disturbances under scenario mode 1. If yes, then execute the above step S304; if no, then execute the following step S306.

[0151] S306. The electronic device determines whether the smart experience function is enabled. If yes, it executes the following step S308; otherwise, it executes the following step S307.

[0152] S307. The electronic device does not provide a notification for message 1.

[0153] S308. The electronic device determines whether the type of message 1 belongs to the preset type. If yes, it executes the above step S304; otherwise, it executes the above step S307.

[0154] For example, suppose that in scenario mode 1, the allowed interruptions include application A, but not application B.

[0155] When Scene Mode 1 is enabled and the Smart Experience feature is activated, the electronic device will send a notification when it receives messages from application A and messages of a preset type. It will not send a notification when it receives messages from other applications, including messages from application B. When Scene Mode 1 is disabled, the electronic device will still send a notification when it receives messages from applications other than application A and the aforementioned preset types.

[0156] When Scene Mode 1 is enabled and Smart Experience is disabled, the electronic device will send a notification when it receives a message from application A, but will not send a notification when it receives a message from application B. When Scene Mode 1 is disabled, the electronic device will still send a notification when it receives a message from application B.

[0157] Continue reading Figure 4B Taking scenario mode 1 as an example of sports mode, activating scenario mode 1 can specifically include: in response to the user's operation on activation option 424 (e.g., a click operation), the electronic device activates scenario mode 1. Activating the smart experience function can specifically include: in response to the user's operation on smart experience switch option 421 (e.g., a click operation), the electronic device can change the smart experience switch option from... Figure 4B The off state toggle is shown as follows Figure 4F The system is now enabled, and the smart experience feature is activated.

[0158] The aforementioned preset types may include, but are not limited to, authentication (e.g., verification codes), food delivery, ride-hailing, package pickup, loan repayment, and flight bookings—scenarios with high real-time requirements. Messages may include, but are not limited to, SMS, incoming calls, and live messages. In one implementation, for SMS and live messages, the scenario type can be determined based on the content of the SMS / live message; for incoming calls, the scenario type can be determined based on the identifier of the caller ID (e.g., identifiers for food delivery, ride-hailing, or bank calls).

[0159] In this embodiment, when the scenario mode is enabled, the intelligent experience function can be further enabled. The electronic device's system default settings include allowed interruption messages, and these messages can include the aforementioned preset types. After enabling the intelligent experience function, regardless of whether the application generating the message is an allowed interruption application, the electronic device will send a message reminder upon receiving the message. This minimizes user disturbance while preventing users from missing important messages, providing a convenient and intelligent user experience.

[0160] In some embodiments, the preset types for enabling the smart experience function may differ depending on the scenario mode. For example, taking authentication (e.g., CAPTCHA) as an example, in sleep mode, users typically do not use the authentication function, so the scenario type in sleep mode may not include authentication. However, in situations where users may use the authentication function, such as in work mode, the preset type may include authentication.

[0161] In this embodiment of the application, message notification can refer to one or more methods, such as sound, vibration, and interface prompts (e.g., pop-ups, live feeds), and the specific method used for message notification can be determined based on the system notification management settings. For example, see [link to relevant documentation]. Figure 4G Taking SMS applications as an example, from Figure 4G As can be seen, currently, when a new message is generated by a text messaging app, the notification methods are sound, vibration, and interface prompts. Interface prompts can be implemented through lock screen notifications, banner notifications, or desktop badges. Therefore, after enabling contextual modes, if notifications for messages generated by text messaging apps are allowed, the electronic device will also notify the user through sound, vibration, and interface prompts.

[0162] Specifically, if the system notification management is set to not notify users of messages from a certain application, then when setting up allowed applications in the scenario mode, if the user selects that application as an allowed application, the electronic device will not notify users when receiving messages from that application after the scenario mode is enabled; alternatively, when the user selects that application as an allowed application, the user can be prompted to go to the system notification management to set up notifications for messages from that application and to set the corresponding notification method.

[0163] In this application embodiment, "not providing message notifications" can mean that no message notifications are provided in any way, and new messages will not be displayed in the notification center. New messages will only be displayed when the user actively enters the application to view them. Alternatively, it can mean that message notifications are not provided in an explicit way (such as sound, vibration, interface prompts, etc.), but new messages will be displayed in the notification center.

[0164] In some embodiments, if a user has set up notifications for messages generated by a certain application in the system notification management, then when the user selects an application to be allowed to be disturbed, that application can be selected by default. In other words, the application can be selected as an application to be allowed to be disturbed by default. If the user does not want to set it as an application to be allowed to be disturbed, they can click on the application to trigger the electronic device to put it into an unselected state.

[0165] Figure 5An example is shown Figure 3 This illustrates a possible interaction flow between different modules involved in the message notification method.

[0166] like Figure 5 As shown, an electronic device may include a message initiation module, a settings module, a message management service module, and a message notification module. The message initiation module may include application A. The specific steps of this process are described in detail below:

[0167] S501, The settings module detected the user's operation of setting scenario mode 1.

[0168] S502. The settings module saves the settings data of scenario mode 1. The settings data includes the applications that are allowed to be disturbed under scenario mode 1. Among them, the applications that are allowed to be disturbed do not include application A.

[0169] The specific execution process of steps S501-S502 can be referred to the above. Figure 3 The relevant textual description of step S301 will not be repeated here.

[0170] S503, the message management service module monitors the activation status of scenario mode 1 and the activation status of intelligent experience function.

[0171] In this application embodiment, if the user creates one or more scenario modes (e.g., scenario mode 1), the electronic device can monitor the activation status of these one or more scenario modes (i.e., whether these one or more scenario modes are enabled) and the activation status of the smart experience function (i.e., whether the smart experience function is enabled) in real time through the message management service module.

[0172] S504, Application A generates message 1.

[0173] S505. Application A sends message 2 to the message management service module. Message 2 includes the type of message 1.

[0174] S506. When the above scenario mode 1 is enabled and the intelligent experience function is enabled, the message management service module determines whether the type of message 1 belongs to the preset type. If yes, then execute the following step S507; if no, then execute the following step S509.

[0175] The preset types mentioned above may include, but are not limited to, authentication (e.g., verification codes), food delivery, ride-hailing, package pickup, loan repayment, and flight bookings—scenarios with high real-time requirements. The generated messages may include, but are not limited to, SMS messages, incoming calls, and live updates. Different messages may use different formats to carry identifiers indicating the message type.

[0176] In some embodiments, step S503 may be executed after step S505, that is, the message management service module executes it after receiving message 2.

[0177] S507. The message management service module sends message 3 to the message reminder module. Message 3 is used to indicate that message 1 should be reminded.

[0178] S508, the message reminder module reminds message 1 based on message 3 (for example, by sound, vibration, interface prompts, etc.).

[0179] S509, The message management service module sends message 4 to the message reminder module. Message 4 is used to indicate that message 1 will not be reminded.

[0180] S510, the message notification module does not send a notification for message 1 based on message 4.

[0181] It is easy to understand that when scenario mode 1 is enabled but the smart experience function is not enabled, the message management service module can simply determine whether the application that generated message 1 is an application that is allowed to be disturbed. If so, it can instruct the message reminder module to remind the user of message 1. If not, it can instruct the message reminder module not to remind the user of message 1. When no scenario mode is enabled, the message management service module can directly instruct the message reminder module to remind the user of message 1.

[0182] It is easy to understand that message 2 above can also include the identifier of the application that generated message 1 (i.e., application A). In this way, the message management service module can determine whether the application that generated message 1 is an application that is allowed to be disturbed based on the identifier of the application that generated message 1.

[0183] Based on the above Figure 5 The process shown below, combined with Figure 6 The following describes the specific process of a message notification method provided in this application embodiment, using SMS and live messages as examples.

[0184] like Figure 6 As shown, this method can be applied to electronic devices, which may include a message initiation module, a settings module, a message management service module, and a message notification module. The message initiation module may include application A and application B. Application A may be, for example, an application that can obtain real-time messages, and obtaining real-time messages can be implemented based on a real-time software development kit (SDK). Application B may be, for example, a short message application. The specific steps of this method are described in detail below:

[0185] S601, The settings module detected the user's operation of setting scenario mode 1.

[0186] S602. The settings module saves the settings data of scenario mode 1. The settings data includes the applications that are allowed to be disturbed under scenario mode 1. The applications that are allowed to be disturbed do not include application A and application B.

[0187] S603, the message management service module monitors the activation status of scenario mode 1 and the activation status of intelligent experience function.

[0188] The specific execution process of steps S601-S603 can be referred to the above. Figure 5 The relevant textual descriptions of steps S501-S503 will not be repeated here.

[0189] Scenario 1: Text Message

[0190] S604. After receiving SMS 1, application B generates identifier 1, which is used to indicate the type of SMS 1 (e.g., verification code type).

[0191] In this embodiment of the application, after generating a message, the application can generate an identifier to indicate the type of the message based on the message. For example, taking SMS 1 as an example where the content includes a verification code, after receiving SMS 1, application B can generate identifier 1 based on the content of SMS 1. Identifier 1 can be used to indicate that the type of SMS 1 is a verification code.

[0192] S605. Application B sends message 1 to the message management service module. Message 1 includes SMS 1 and identifier 1.

[0193] The aforementioned identifier 1 may be independent of the aforementioned SMS 1, or it may be included in the aforementioned SMS 1.

[0194] S606. When the above scenario mode 1 is enabled and the intelligent experience function is enabled, the message management service module determines whether the type indicated by the identifier 1 belongs to the preset type. If yes, then the following step S607 is executed; if no, then the following step S609 is executed.

[0195] In some embodiments, step S603 may be executed after step S605, that is, the message management service module executes it after receiving message 1.

[0196] S607, The message management service module sends message 2 to the message reminder module. Message 2 is used to instruct that SMS 1 be reminded.

[0197] S608, the message reminder module reminds SMS 1 based on message 2 (for example, by sound, vibration, interface prompts, etc.).

[0198] S609, The message management service module sends message 3 to the message reminder module. Message 3 is used to indicate that no reminder will be given for SMS 1.

[0199] S610, the message reminder module does not send a reminder for SMS 1 based on message 3.

[0200] Among them, steps S609 and S610 are optional.

[0201] Scenario 2: Live Message

[0202] S611, Application A obtains real-time message 1.

[0203] Among them, the aforementioned live message 1 can be, for example, a live message generated in any of the scenarios in Table 1 above.

[0204] The aforementioned live message 1 can be generated by application A itself, or it can be generated by a message received by application A from the server.

[0205] S612. Application A sends message 4 to the message management service module. Message 4 includes real-time message 1 and identifier 2.

[0206] The aforementioned identifier 2 may be independent of the aforementioned live message 1, or it may be included in the aforementioned live message 1.

[0207] S613. When the above scenario mode 1 is enabled and the intelligent experience function is enabled, the message management service module determines whether the type indicated by the identifier 2 belongs to the preset type. If yes, then the following step S614 is executed; if no, then the following step S616 is executed.

[0208] Since live messages are usually something users need to keep track of in real time, in some embodiments, electronic devices can send alerts for any live message, without needing to determine whether the message type belongs to a preset type.

[0209] In some embodiments, step S603 may also be executed after step S612, that is, the message management service module executes it after receiving message 4.

[0210] S614. The message management service module sends message 5 to the message reminder module. Message 5 is used to instruct the reminder to provide a reminder for the real-time message 1.

[0211] S615, the message reminder module reminds the user of real-time message 1 based on message 5 (e.g., by displaying it in real time through the real-time window, and optionally by combining it with sound, vibration, etc.).

[0212] S616, The message management service module sends message 6 to the message reminder module. Message 6 is used to indicate that no reminder will be given for the real-time message 1.

[0213] S617, The message reminder module does not send a reminder for real-time message 1 based on message 6.

[0214] Steps S616 and S617 are optional.

[0215] It is understandable that the above-mentioned text messages and live messages are just examples. For other types of messages, the processing procedure can be similar to that of text messages and live messages.

[0216] Continue reading Figure 4B Regarding the Smart Experience function, users can only enable / disable it by clicking the Smart Experience switch option 421. However, once enabled, users cannot clearly see which types of messages are allowed to be disturbed by default, nor can they select a subset of these message types as allowed. Based on the above problems, this application provides the following two solutions:

[0217] Solution 1

[0218] See Figure 7 Electronic devices can Figure 4B The Smart Experience switch option 421 replaces the message alert switch option displayed for one or more types of messages. These one or more types can refer to the types of messages that are allowed to be disturbed by the system's default settings. These one or more types of messages may include, but are not limited to, the following: Figure 7 Examples include authentication messages (such as verification codes), travel messages, order & logistics messages, financial messages, and social communication messages.

[0219] Users can trigger their electronic devices to turn on / off by clicking the message notification switch option.

[0220] After enabling the scenario mode, if a certain type of message notification switch option is turned on, the electronic device will send a message notification when it receives a message of that type, regardless of whether the application that generated the message is an application that allows interruptions.

[0221] Solution 2

[0222] See Figure 8A , Figure 8A The exemplary user interface 810 and Figure 4B Similarly, but with a difference, electronic devices will Figure 4B The Smart Experience switch option 421 has been replaced and displayed as Figure 8AThe smart experience entry setting item 811 is located in the device. The electronic device can detect the user's action on the smart experience entry setting item 811 (e.g., a click action), and in response to the action, the electronic device can display... Figure 8B The exemplary user interface 820 is shown.

[0223] See Figure 8B The user interface 820 may include message notification switch options corresponding to one or more types of messages. These one or more types may refer to the types of messages that are allowed to be disturbed by the system's default settings, regardless of the scenario mode. Alternatively, they may refer to the types of messages that the user is more likely to pay attention to in the corresponding scenario mode from among the types of messages allowed to be disturbed by the system's default settings. For example, in sports mode, the above one or more types of messages may include messages that the user is more likely to pay attention to in a sports scenario, such as... Figure 8B The messages shown include those related to sports and health, weather, location, and social communication.

[0224] Continue reading Figure 8B When multiple message alert options are displayed for different message types, these options can be sorted according to preset rules. These rules may include, but are not limited to, the likelihood of a user paying attention to a message in a given scenario. The higher the likelihood of a user paying attention to a particular message type, the higher that type of message should be ranked. For example... Figure 8B As shown, in sports scenarios, users are most likely to pay attention to sports and health-related messages, therefore, sports and health-related messages can be ranked first.

[0225] By implementing the above-mentioned solutions one and two, on the one hand, users can clearly know which types of messages the system allows to disturb by default; on the other hand, users can choose one or more types of messages as allowed messages to disturb.

[0226] Example 2

[0227] In Example 2, the messages generated by the application can be divided into multiple types. The electronic device can support the user to select the type of message that can be disturbed by the application. After the scenario mode is enabled, the electronic device will only send a message reminder when it receives a message of the type of message that can be disturbed by the user selected by the application. In this way, the user can select the type of message that can be disturbed by the application. Compared with only being able to select the application that can be disturbed, it can provide the user with a more granular selection experience. While ensuring that the user is less disturbed, it can also prevent the user from missing the message of the type of message they selected.

[0228] Figure 9 The specific flow of a message notification method provided in an embodiment of this application is illustrated by way of example.

[0229] like Figure 9 As shown, this method can be applied to electronic devices. The specific steps of this method are described in detail below:

[0230] S901. The electronic device saves the setting data of scenario mode 1, which includes the applications that are allowed to be disturbed under scenario mode 1 selected by the user and the corresponding types of messages that are allowed to be disturbed.

[0231] Specifically, the electronic device detects the user's operation of setting scenario mode 1. In response to the operation, the electronic device saves the setting data of scenario mode 1, which includes the applications that the user selects to be disturbed when scenario mode 1 is enabled and the corresponding types of messages that are allowed to be disturbed.

[0232] Among them, Scene Mode 1 can be a scene mode created by the user. Setting Scene Mode 1 can specifically include: setting the name of Scene Mode 1 (such as sports mode), setting the applications that can be disturbed, and setting the contacts that can be disturbed.

[0233] Unlike the aforementioned Embodiment 1, the messages generated by the application can be divided into multiple types, and the application that can be allowed to be disturbed can include the type of message that the user selects to be disturbed by the application.

[0234] Similar to Embodiment 1, electronic devices can also support users to set up scene modes in the settings application. However, the step of setting up the allowed disturbing applications during the scene mode setting process is different from that in Embodiment 1. This step will be described in detail below.

[0235] Continue reading Figure 4B The electronic device can detect user actions (such as clicks) on application and meta-service options 422, and in response to these actions, the electronic device can display... Figure 10A The exemplary user interface 1010 may include settings entries for one or more applications (e.g., application A, application B, application C, etc.). Users can trigger the electronic device to display the type of message corresponding to an application by clicking on the settings entry of an application.

[0236] It should be noted that the embodiments of this application do not limit the rules for message classification. Messages can be classified according to actual needs, and can be coarse-grained or fine-grained.

[0237] It's easy to understand that different applications typically have different message types. Examples are given below.

[0238] 1. Taking an application that can obtain real-time information as an example

[0239] Continue reading Figure 10A Taking application A as an example, which is an application that can obtain live messages, the electronic device can detect the user's operation (such as a click) on the settings items of application A. In response to the operation, the electronic device can display... Figure 10B The user interface shown in the example may include the type of message corresponding to application A (e.g., live, news, chat, others).

[0240] Electronic devices can allow users to manually select one or more types of disturbances that can be allowed. The selected type can be any type of disturbance allowed. Figure 10B It is easy to see that all types of disturbances are allowed. See [link / reference] Figure 10B Users can also click on the selected type to trigger the electronic device to change the selected type from a selected state to an unselected state, at which point the type will change from a type that allows disturbance to a type that does not allow disturbance.

[0241] 2. Taking SMS applications as an example

[0242] Continue reading Figure 10A Taking application B as an example, which is a short message application, the electronic device can detect the user's operation (such as a click) on the settings items of application B. In response to this operation, the electronic device can display... Figure 10C The exemplary user interface may include the message type corresponding to application B (e.g., authentication, finance, order & logistics, travel, others).

[0243] Similarly, electronic devices can allow users to manually select one or more types of disturbances that can be allowed, and the selected type can be any type of disturbance allowed. Figure 10C It is easy to see from the text that the type of disturbance allowed is authentication-based; see reference. Figure 10C Users can also trigger the electronic device to switch the selected state of the authentication type (such as verification code) message to the unselected state by clicking on the authentication type (such as verification code) message. At this time, the authentication type will switch from the allowed to disturb type to the disallowed to disturb type.

[0244] 3. Taking social applications as an example

[0245] Continue reading Figure 10A Taking application C as an example, which is a social application, the electronic device can detect the user's actions (such as clicking) on ​​settings items of application C. In response to this action, the electronic device can display... Figure 10D The exemplary user interface may include the message type corresponding to application C (e.g., instant messaging, audio / video calls, video calls, official accounts, video accounts, service accounts, others).

[0246] In some embodiments, messages generated by application A can be further categorized, either coarser or finer. For example, instant messaging messages can be categorized into one-on-one messages and group chat messages; group chat messages can be further categorized into messages that mention me and messages that do not mention me; and so on.

[0247] Similarly, electronic devices can allow users to manually select one or more types of disturbances that can be allowed, and the selected type can be any type of disturbance allowed. Figure 10D It's easy to see that the user did not select the type of disturbance allowed.

[0248] S902, The electronic device received message 1.

[0249] S903. The electronic device determines whether scenario mode 1 is enabled. If yes, it executes the following step S905; otherwise, it executes the following step S904.

[0250] S904, The electronic device provides a notification for message 1.

[0251] S905. The electronic device determines whether message 1 is generated by an application that allows disturbances under scenario mode 1. If yes, it executes the following step S907; otherwise, it executes the following step SS906.

[0252] S906. The electronic device does not provide a notification for message 1.

[0253] S907. The electronic device determines whether the type of message 1 belongs to the type of message that is allowed to be disturbed in the corresponding application. If yes, then the above step S904 is executed; if no, then the above step S906 is executed.

[0254] For example, suppose the applications that allow interruptions include application A and application B. The types of messages that allow interruptions for application A include all types, while the types of messages that allow interruptions for application B include type 1.

[0255] When Scene Mode 1 is enabled, the electronic device will send notifications when it receives all types of messages corresponding to application A and type 1 messages corresponding to application B. It will not send notifications when it receives messages other than those corresponding to application A and application B. When Scene Mode 1 is disabled, the electronic device will still send notifications when it receives messages other than those corresponding to application A and application B.

[0256] Continue reading Figure 4B Taking the above scenario mode 1 as a sports mode as an example, turning on scenario mode 1 can specifically include: responding to the user's operation on the turn-on option 424 (such as a click operation), the electronic device turns on scenario mode 1.

[0257] In this embodiment of the application, message notification can refer to one or more methods, such as sound, vibration, and interface prompts (e.g., pop-ups, live feeds), and the specific method used for message notification can be determined based on the system notification management settings. For example, see [link to relevant documentation]. Figure 10E Taking SMS applications as an example, unlike the aforementioned Embodiment 1, each type of message can have its own notification method set individually. For example, with authentication-type messages (e.g., verification codes), the user can click on the settings entry for authentication-type messages (e.g., verification codes) to trigger the display on the electronic device. Figure 10F The exemplary user interface shown is from Figure 10E As can be seen, when SMS applications generate authentication messages, the notification methods are sound, vibration, and interface prompts. Among them, interface prompts can be implemented through lock screen notifications, banner notifications, and desktop badges. Therefore, after enabling the scenario mode, if notifications for authentication messages generated by SMS applications are allowed, then the electronic device will also notify the user through sound, vibration, and interface prompts.

[0258] Specifically, if the system notification management is configured to not alert users to a certain type of message generated by a particular application, then when setting the types of messages allowed to be disturbed in the scenario mode, if the user selects that type of message from that application as an allowed message, then after enabling the scenario mode, the electronic device may not alert users when receiving that type of message from that application; alternatively, when the user selects that type of message from that application as an allowed message, the user can be prompted to go to the system notification management to set whether to allow alerts for that type of message from that application and to set the corresponding alert method.

[0259] In this application embodiment, "not providing message notifications" can mean that no message notifications are provided in any way, and new messages will not be displayed in the notification center. New messages will only be displayed when the user actively enters the application to view them. Alternatively, it can mean that message notifications are not provided in an explicit way (such as sound, vibration, interface prompts, etc.), but new messages will be displayed in the notification center.

[0260] In some embodiments, if a user sets up notifications for a certain type of message generated by an application in the system notification management, then when the user selects the type of message to be allowed to be disturbed, that type of message in the application can be selected by default. That is to say, messages of that type in the application can be selected as allowed messages by default. If the user does not want to set it as an allowed message, they can click on the type to trigger the electronic device to set it to an unselected state.

[0261] Figure 11An example is shown Figure 9 This illustrates a possible interaction flow between different modules involved in the message notification method.

[0262] like Figure 11 As shown, an electronic device may include a message initiation module, a settings module, a message management service module, and a message notification module. The message initiation module may include application A. The specific steps of this process are described in detail below:

[0263] S1101, The settings module detected the user's operation of setting scenario mode 1.

[0264] S1102. The settings module saves the settings data of scenario mode 1. The settings data includes the applications that the user selects to be disturbed under scenario mode 1 and the corresponding types of messages that are allowed to be disturbed.

[0265] The specific execution process of steps S1101-S1102 can be referred to the above. Figure 9 The relevant textual description of step S901 will not be repeated here.

[0266] S1103. The message management service module monitors the activation status of scenario mode 1, the applications that the user selects to be disturbed under scenario mode 1, and the corresponding types of messages that are allowed to be disturbed.

[0267] In this embodiment of the application, if the user creates one or more scenario modes (e.g., scenario mode 1), the electronic device can monitor the activation status of these one or more scenario modes (i.e., whether these one or more scenario modes are enabled) in real time through the message management service module, and monitor in real time the application that the user selects to be disturbed under scenario mode 1 and the type of message that is allowed to be disturbed.

[0268] S1104, Application A generates message 1.

[0269] S1105. Application A sends message 2 to the message management service module. Message 2 includes the identifier of application A and the type of message 1.

[0270] S1106. When scenario mode 1 is enabled, the message management service module determines whether the application that generated message 1 is the application that the user selected to be allowed to disturb, and whether the type of message 1 is the type of allowed message corresponding to the application. If yes, then the following step S1107 is executed; if no, then the following step S1109 is executed.

[0271] Since the application that generated message 1 is application A, the above determination of whether the application that generated message 1 is the application that the user has selected to be allowed to be disturbed may specifically include: determining whether application A is the application that the user has selected to be allowed to be disturbed based on the identifier of application A.

[0272] In some embodiments, step S1103 may be executed after step S1105, that is, the message management service module executes it after receiving message 2.

[0273] S1107. The message management service module sends message 3 to the message reminder module. Message 3 is used to indicate that message 1 should be reminded.

[0274] S1108, The message reminder module reminds message 1 based on message 3 (for example, by sound, vibration, interface prompts, etc.).

[0275] S1109. The message management service module sends message 4 to the message reminder module. Message 4 is used to indicate that message 1 will not be reminded.

[0276] S1110, The message reminder module does not send a reminder for message 1 based on message 4.

[0277] Based on the above Figure 11 The process shown below, combined with Figure 12 The following describes the specific process of a message notification method provided in this application embodiment, using SMS and live messages as examples.

[0278] like Figure 12 As shown, this method can be applied to electronic devices, which may include a message initiation module, a settings module, a message management service module, and a message notification module. The message initiation module may include application A and application B, where application A may be, for example, an application that can obtain real-time messages, and application B may be, for example, a short message application. The specific steps of this method are described in detail below:

[0279] S1201, The settings module detected the user's operation of setting scenario mode 1.

[0280] S1202. The settings module saves the settings data of scenario mode 1. The settings data includes the applications that the user selects to be disturbed under scenario mode 1 and the corresponding types of messages that are allowed to be disturbed.

[0281] S1203 The message management service module monitors the activation status of scenario mode 1, the applications that the user selects to be disturbed under scenario mode 1, and the corresponding types of messages that are allowed to be disturbed.

[0282] The specific execution process of steps S1201-S1203 can be referred to the above. Figure 11 The relevant textual descriptions of steps S1101-S1103 are not repeated here.

[0283] Scenario 1: Text Message

[0284] S1204. After receiving SMS 1, application B generates identifier 1, which is used to indicate the type of SMS 1 (e.g., verification code type).

[0285] In this embodiment of the application, after generating a message, the application can generate an identifier to indicate the type of the message based on the message. For example, taking SMS 1 as an example where the content includes a verification code, after receiving SMS 1, application B can generate identifier 1 based on the content of SMS 1. Identifier 1 can be used to indicate that the type of SMS 1 is a verification code.

[0286] S1205, Application B sends message 1 to the message management service module. Message 1 includes SMS 1, identifier 1, and the identifier of Application B.

[0287] The aforementioned identifier 1 may be independent of the aforementioned SMS message 1, or it may be included in the aforementioned SMS message 1.

[0288] S1206. When scenario mode 1 is enabled, the message management service module determines whether the application that generated SMS 1 is the application that the user has selected to allow interruptions, and whether the type of SMS 1 is the type of message that the user is allowed to interrupt. If yes, then the following step S1207 is executed; otherwise, the following step S1209 is executed.

[0289] Since the application that generated SMS 1 is application B, the above determination of whether the application that generated SMS 1 is an application that the user has selected to be allowed to be disturbed can specifically include: determining whether application B is an application that the user has selected to be allowed to be disturbed based on the identifier of application B.

[0290] Since the type of SMS 1 is indicated by identifier 1, the above determination of whether the type of SMS 1 is the type of message that is allowed to be disturbed corresponding to the above application can specifically include: determining whether the type indicated by identifier 1 is the type of message that is allowed to be disturbed corresponding to application B based on identifier 1.

[0291] In some embodiments, step S1203 may be executed after step S1205, that is, the message management service module executes it after receiving message 1.

[0292] S1207. The message management service module sends message 2 to the message reminder module. Message 2 is used to instruct that SMS 1 be reminded.

[0293] S1208, The message reminder module reminds SMS 1 based on message 2 (e.g., through sound, vibration, interface prompts, etc.).

[0294] S1209. The message management service module sends message 3 to the message reminder module. Message 3 is used to indicate that no reminder will be given for SMS 1.

[0295] S1210, The message reminder module does not send a reminder for SMS 1 based on message 3.

[0296] Among them, steps S1209 and S1210 are optional.

[0297] Scenario 2: Live Message

[0298] S1211, Application A obtains real-time message 1.

[0299] Among them, the aforementioned live message 1 can be, for example, a live message generated in any of the scenarios in Table 1 above.

[0300] The aforementioned live message 1 can be generated by application A itself, or it can be generated by a message received by application A from the server.

[0301] S1212, Application A sends message 4 to the message management service module. Message 4 includes real-time message 1, identifier 2, and the identifier of application A.

[0302] The aforementioned identifier 2 may be independent of the aforementioned live message 1, or it may be included in the aforementioned live message 1.

[0303] S1213. When scenario mode 1 is enabled, the message management service module determines whether the application that generated the live message 1 is the application that the user selected to allow disturbance, and whether the type indicated by the identifier 2 is the type of message that the application is allowed to disturb. If yes, then the following step S1214 is executed; otherwise, the following step S1216 is executed.

[0304] Since the application that generated live message 1 is application A, the above determination of whether the application that generated live message 1 is an application selected by the user for permission to be disturbed may specifically include: determining whether application A is an application selected by the user for permission to be disturbed based on the identifier of application A.

[0305] Since live messages are usually something users need to pay attention to in real time, in some embodiments, electronic devices can alert users to any live message, regardless of whether the application that generated the live message 1 is an application that the user has selected to allow interruptions. In this case, the step of determining whether the application that generated the live message 1 is an application that the user has selected to allow interruptions does not need to be performed.

[0306] In some embodiments, step S1203 may be executed after step S1212, that is, the message management service module executes it after receiving message 4.

[0307] S1214. The message management service module sends message 5 to the message reminder module. Message 5 is used to instruct the reminder to provide a reminder for the real-time message 1.

[0308] S1215, The message reminder module reminds the user of real-time message 1 based on message 5 (e.g., by displaying it in real time through the real-time window, and optionally by combining it with sound, vibration, etc.).

[0309] S1216. The message management service module sends message 6 to the message reminder module. Message 6 is used to indicate that no reminder will be given for the real-time message 1.

[0310] S1217. The message reminder module does not send a reminder for real-time message 1 based on message 6.

[0311] Among them, steps S1216 and S1217 are optional.

[0312] It is understandable that the above-mentioned text messages and live messages are just examples. For other types of messages, the processing procedure can be similar to that of text messages and live messages.

[0313] The electronic device provided in this application embodiment can run an operating system (OS). This operating system can be various operating systems currently used in the industry, such as HarmonyOS, an operating system developed based on OpenHarmony; or other operating systems, for example... The iOS mobile operating system; it can also refer to various open-source operating systems or their derivatives, such as Linux OS, and other embedded operating systems; it can also be a future type of operating system, such as an AI operating system based on artificial intelligence. An operating system is a set of interconnected system software programs that manage and control the operation of electronic devices, utilize and run hardware and software resources, and provide public services to organize user interaction. The operating system occupies a pivotal position in electronic devices, connecting to the physical hardware layer below and providing a runtime environment for application software above.

[0314] An operating system typically includes a kernel layer, a middleware layer, and an application layer. The application layer includes applications, which can include system applications and third-party applications. The middleware layer is a suite of software, or frameworks, that provides various services to application developers, such as databases, multimedia, and graphics, or capabilities like distributed scheduling and system expansion. For example, the middleware layer can also be broadly divided into a framework layer and / or a system service layer. The framework layer provides application programming interfaces (APIs) and programming frameworks for applications in the application layer. The system service layer includes the system's core capabilities, providing services to applications through the framework layer. The kernel layer is the layer between hardware and software. The kernel layer can include hardware drivers and the operating system kernel. In addition to providing hardware drivers, the kernel layer also supports functions such as memory management and system process management.

[0315] The electronic devices we use in our daily lives come in various types and forms, and are applied in a wide range of scenarios. Therefore, based on the different forms and functions of electronic devices, different application scenarios, and different user needs, the operating systems used in these devices may also differ. These operating systems share commonalities but also have their own unique characteristics. Different operating systems affect user experience, application ecosystem, and system performance. The basic functions implemented by the electronic device provided in this application can be implemented using a general-purpose operating system or a dedicated operating system. To more clearly illustrate the implementation of the embodiments of this application under a specific operating system, the architecture of HarmonyOS is shown below. Those skilled in the art can deduce the implementation of the embodiments of this application under other specific operating systems, such as... Implementation under the operating system.

[0316] Figure 13 An exemplary embodiment of the software structure of an electronic device provided in this application is shown.

[0317] like Figure 13 As shown, the software architecture of an electronic device can be divided into several layers. In some embodiments, from bottom to top, these layers are: kernel layer, system service layer, framework layer, and application layer. The layers communicate with each other through software interfaces. System functions can be tailored, added, or combined at the subsystem granularity in different device deployment scenarios, and each subsystem can also be tailored, added, or combined at the functional granularity.

[0318] The Kernel Abstraction Layer (KAL) provides basic kernel capabilities to upper layers by shielding the differences between multiple kernels, including but not limited to process / thread management, memory management, file system, network management, and peripheral device management.

[0319] Kernel Subsystem: Supports the selection of a suitable OS kernel for different resource-constrained devices, including but not limited to Linux kernel, HarmonyOS kernel, LiteOS, etc.

[0320] Driver Subsystem: The driver framework is the foundation for the open system hardware ecosystem, providing unified peripheral access capabilities and a framework for driver development and management. The driver framework includes: display drivers, camera drivers, audio drivers, Bluetooth drivers, sensor drivers, etc.

[0321] The system service layer comprises the core capabilities of the system, providing services to applications through the framework layer. This layer includes, but is not limited to, the following subsystems:

[0322] The system's basic capability subsystems provide fundamental capabilities for the operation, scheduling, and migration of distributed applications across multiple devices. For example, they may include distributed soft bus, distributed data management, distributed task scheduling, and compiler / runner; they may also include multi-modal input subsystem, graphics subsystem, security subsystem, and AI subsystem.

[0323] Basic software service subsystems: provide common and general software services; for example, event notification subsystem, telephone service subsystem, multimedia subsystem, etc.

[0324] In some possible implementations, the event notification subsystem may include the aforementioned Figure 2 The message management service module shown.

[0325] Enhanced software service subsystem suite: Provides differentiated capability-enhancing software services for different devices; for example, it may include proprietary business subsystems for smart screens, wearable devices, and IoT devices.

[0326] Hardware service subsystem set: provides hardware services; for example, it may include location service subsystem, user IAM (Identity and Access Management) subsystem, wearable proprietary hardware service subsystem, biometric identification, IoT proprietary hardware service subsystem, etc.

[0327] Distributed task scheduling enables distributed service management (discovery, synchronization, registration, and invocation), supporting remote startup, remote invocation, remote connection, and migration of applications across devices.

[0328] Distributed data management enables data synchronization, data storage, data sharing, and data access across all scenarios and devices.

[0329] The distributed soft bus provides communication-related capabilities for seamless interconnection between multiple devices, including: WLAN service capabilities, Bluetooth service capabilities, soft bus, inter-process communication RPC (Remote Procedure Call) and other communication capabilities.

[0330] A compiler / runner is a unified compilation and runtime platform designed to support the joint compilation and execution of multiple programming languages ​​and multiple chip platforms. For example, a compiler / runner could be the ArkCompiler.

[0331] The framework layer provides application programming interfaces (APIs) and programming frameworks for applications in the application layer. Examples include the UI framework module (which provides a complete infrastructure for UI development, including UI functionalities such as components, layouts, animations, and interactive events, as well as real-time interface preview tools), the user application framework, and the Ability framework (an Ability is a lightweight application; the Ability framework schedules and manages the operation and lifecycle of Abilities). Different devices may run different operating systems, and therefore support different APIs.

[0332] The HarmonyOS API is a series of open capabilities provided to support HarmonyOS application development. The HarmonyOS API can be set at the framework layer or independently of the framework layer. Examples include: Audio API (audio service), Push API (push service), and Account API (account service).

[0333] The application layer can include applications in electronic devices, including but not limited to: desktop, notification center, settings, phone, SMS, social, travel, etc.

[0334] Among them, the aforementioned Figure 2 The message notification module shown could be, for example, a notification center.

[0335] Among them, the aforementioned Figure 2 The settings module shown can be, for example, a settings application.

[0336] Among them, the aforementioned Figure 2 The message initiation module shown can be an application that can generate messages, such as a telephone or SMS.

[0337] The following is a schematic diagram of the hardware structure of an electronic device provided in an embodiment of this application.

[0338] Figure 14The hardware structure of an electronic device provided in an embodiment of this application is illustrated by way of example.

[0339] like Figure 14 As shown, the electronic device may include: a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, a headphone jack 170D, a sensor module 180, buttons 190, a motor 191, an indicator 192, a camera 193, a display screen 194, and a subscriber identification module (SIM) card interface 195, etc. The sensor module 180 may include a pressure sensor 180A, a gyroscope sensor 180B, a barometric pressure sensor 180C, a magnetic sensor 180D, an accelerometer sensor 180E, a distance sensor 180F, a proximity sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, an ambient light sensor 180L, a bone conduction sensor 180M, etc.

[0340] It is understood that the structures illustrated in the embodiments of this application do not constitute a specific limitation on the electronic device. In other embodiments of this application, the electronic device may include more or fewer components than illustrated, or combine some components, or split some components, or have different component arrangements. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0341] Processor 110 may include one or more processing units, such as: application processor (AP), modem processor, graphics processing unit (GPU), image signal processor (ISP), controller, memory, video codec, digital signal processor (DSP), baseband processor, and / or neural network processing unit (NPU), etc. Different processing units may be independent devices or integrated into one or more processors.

[0342] The controller can serve as the nerve center and command center of an electronic device. Based on instruction opcodes and timing signals, the controller generates operation control signals to control the fetching and execution of instructions.

[0343] The processor 110 may also include a memory for storing instructions and data. In some embodiments, the memory in the processor 110 is a cache memory. This memory can store instructions or data that the processor 110 has just used or that are used repeatedly. If the processor 110 needs to use the instruction or data again, it can retrieve it directly from the memory. This avoids repeated accesses, reduces the waiting time of the processor 110, and thus improves the efficiency of the system.

[0344] In some embodiments, the processor 110 may include one or more interfaces. Interfaces may include an inter-integrated circuit (I2C) interface, an inter-integrated circuit sound (I2S) interface, a pulse code modulation (PCM) interface, a universal asynchronous receiver / transmitter (UART) interface, a mobile industry processor interface (MIPI), a general-purpose input / output (GPIO) interface, a subscriber identity module (SIM) interface, and / or a universal serial bus (USB) interface, etc.

[0345] The I2C interface is a bidirectional synchronous serial bus, including a serial data line (SDA) and a serial clock line (SCL). In some embodiments, the processor 110 may include multiple I2C buses. The processor 110 can couple to the touch sensor 180K, charger, flash, camera 193, etc., through different I2C bus interfaces. For example, the processor 110 can couple to the touch sensor 180K through the I2C interface, enabling the processor 110 and the touch sensor 180K to communicate through the I2C bus interface, thereby realizing the touch function of the electronic device.

[0346] The I2S interface can be used for audio communication. In some embodiments, the processor 110 may include multiple I2S buses. The processor 110 can be coupled to the audio module 170 via the I2S bus to enable communication between the processor 110 and the audio module 170. In some embodiments, the audio module 170 can transmit audio signals to the wireless communication module 160 via the I2S interface to enable the function of answering phone calls through a Bluetooth headset.

[0347] The MIPI interface can be used to connect the processor 110 to peripheral devices such as the display screen 194 and the camera 193. The MIPI interface includes a camera serial interface (CSI) and a display serial interface (DSI). In some embodiments, the processor 110 and the camera 193 communicate via the CSI interface to enable the electronic device to capture images. The processor 110 and the display screen 194 communicate via the DSI interface to enable the electronic device to display images.

[0348] The GPIO interface can be configured via software. It can be configured as a control signal or a data signal. In some embodiments, the GPIO interface can be used to connect the processor 110 to a camera 193, a display screen 194, a wireless communication module 160, an audio module 170, a sensor module 180, etc. The GPIO interface can also be configured as an I2C interface, an I2S interface, a UART interface, a MIPI interface, etc.

[0349] USB port 130 is a USB standard compliant interface, which can be a Mini USB port, Micro USB port, USB Type-C port, etc. USB port 130 can be used to connect a charger to charge electronic devices, and can also be used for data transfer between electronic devices and peripheral devices. It can also be used to connect headphones for audio playback. This interface can also be used to connect other terminal devices, such as AR devices.

[0350] It is understood that the interface connection relationships between the modules illustrated in the embodiments of this application are merely illustrative and do not constitute a limitation on the structure of the electronic device. In other embodiments of this application, the electronic device may also employ different interface connection methods or combinations of multiple interface connection methods as described in the above embodiments.

[0351] The charging management module 140 receives charging input from a charger. The charger can be a wireless charger or a wired charger. In some wired charging embodiments, the charging management module 140 receives charging input from the wired charger via a USB interface 130. In some wireless charging embodiments, the charging management module 140 receives wireless charging input via the wireless charging coil of the electronic device. While charging the battery 142, the charging management module 140 can also supply power to the electronic device via the power management module 141.

[0352] The power management module 141 connects the battery 142, the charging management module 140, and the processor 110. The power management module 141 receives input from the battery 142 and / or the charging management module 140, providing power to the processor 110, internal memory 121, external memory, display screen 194, camera 193, and wireless communication module 160, etc. The power management module 141 can also monitor parameters such as battery capacity, battery cycle count, and battery health status (leakage current, impedance). In some other embodiments, the power management module 141 may also be located within the processor 110. In other embodiments, the power management module 141 and the charging management module 140 may be located in the same device.

[0353] The wireless communication function of electronic devices can be realized through antenna 1, antenna 2, mobile communication module 150, wireless communication module 160, modem processor and baseband processor, etc.

[0354] Antenna 1 and antenna 2 are used to transmit and receive electromagnetic wave signals. Each antenna in the electronic device can be used to cover one or more communication frequency bands. Different antennas can also be reused to improve antenna utilization. For example, antenna 1 can be reused as a diversity antenna for a wireless local area network. In some other embodiments, the antennas can be used in conjunction with a tuning switch.

[0355] The mobile communication module 150 can provide solutions for wireless communication applications including 2G / 3G / 4G / 5G in electronic devices. The mobile communication module 150 may include at least one filter, switch, power amplifier, low noise amplifier (LNA), etc. The mobile communication module 150 can receive electromagnetic waves via antenna 1, and perform filtering, amplification, and other processing on the received electromagnetic waves before transmitting them to a modem processor for demodulation. The mobile communication module 150 can also amplify the signal modulated by the modem processor and convert it into electromagnetic waves for radiation via antenna 1. In some embodiments, at least some functional modules of the mobile communication module 150 may be housed in processor 110. In some embodiments, at least some functional modules of the mobile communication module 150 and at least some modules of the processor 110 may be housed in the same device.

[0356] The modem processor may include a modulator and a demodulator. The modulator modulates the low-frequency baseband signal to be transmitted into a mid-to-high frequency signal. The demodulator demodulates the received electromagnetic wave signal into a low-frequency baseband signal. The demodulator then transmits the demodulated low-frequency baseband signal to the baseband processor for processing. After processing by the baseband processor, the low-frequency baseband signal is transmitted to the application processor. The application processor outputs sound signals through an audio device (not limited to speaker 170A, receiver 170B, etc.) or displays images or videos through the display screen 194. In some embodiments, the modem processor may be a separate device. In other embodiments, the modem processor may be independent of the processor 110 and may be housed in the same device as the mobile communication module 150 or other functional modules.

[0357] The wireless communication module 160 can provide solutions for wireless communication applications in electronic devices, including wireless local area networks (WLANs) (such as wireless fidelity (Wi-Fi) networks), Bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), and infrared (IR) technologies. The wireless communication module 160 can be one or more devices integrating at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via antenna 2, performs frequency modulation and filtering of the electromagnetic wave signals, and sends the processed signal to processor 110. The wireless communication module 160 can also receive signals to be transmitted from processor 110, perform frequency modulation and amplification, and convert them into electromagnetic waves for radiation via antenna 2.

[0358] In some embodiments, antenna 1 of the electronic device is coupled to mobile communication module 150, and antenna 2 is coupled to wireless communication module 160, enabling the electronic device to communicate with networks and other devices via wireless communication technology. The wireless communication technology may include Global System for Mobile Communications (GSM), General Packet Radio Service (GPRS), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), Time-Division Code Division Multiple Access (TD-SCDMA), Long Term Evolution (LTE), BT, GNSS, WLAN, NFC, FM, and / or IR technologies. The GNSS may include Global Positioning System (GPS), Global Navigation Satellite System (GLONASS), BeiDou Navigation Satellite System (BDS), Quasi-Zenith Satellite System (QZSS), and / or Satellite Based Augmentation Systems (SBAS).

[0359] Electronic devices implement display functions through a GPU, a display screen 194, and an application processor. The GPU is a microprocessor for image processing, connecting the display screen 194 and the application processor. The GPU is used to perform mathematical and geometric calculations and for graphics rendering. The processor 110 may include one or more GPUs, which execute program instructions to generate or modify display information.

[0360] Display screen 194 is used to display images, videos, etc. Display screen 194 includes a display panel. The display panel may be a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode (AMOLED), a flexible light-emitting diode (FLED), a miniature LED, a microLED, a quantum dot light-emitting diode (QLED), etc. In some embodiments, the electronic device may include one or N displays 194, where N is a positive integer greater than 1.

[0361] In this embodiment of the application, the electronic device can output interface prompts (such as pop-ups or live windows) through the display screen 194 to provide message reminders.

[0362] Electronic devices can achieve shooting functions through ISP, camera 193, video codec, GPU, display 194 and application processor.

[0363] The external storage interface 120 can be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the electronic device. The external memory card communicates with the processor 110 through the external storage interface 120 to perform data storage functions. For example, music, video, and other files can be saved on the external memory card.

[0364] Internal memory 121 can be used to store computer executable program code, which includes instructions. Processor 110 executes various functional applications and data processing of the electronic device by running the instructions stored in internal memory 121. Internal memory 121 may include a program storage area and a data storage area. The program storage area may store the operating system, at least one application program required for a function (such as sound playback, image playback, etc.), etc. The data storage area may store data created during the use of the electronic device (such as audio data, phonebook, etc.). Furthermore, internal memory 121 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, universal flash storage (UFS), etc.

[0365] Electronic devices can implement audio functions such as music playback and recording through audio modules 170, speakers 170A, receivers 170B, microphones 170C, headphone jacks 170D, and application processors.

[0366] The audio module 170 is used to convert digital audio information into analog audio signals for output, and also to convert analog audio input into digital audio signals. The audio module 170 can also be used for encoding and decoding audio signals. In some embodiments, the audio module 170 may be located in the processor 110, or some functional modules of the audio module 170 may be located in the processor 110.

[0367] The speaker 170A, also known as a "loudspeaker," is used to convert audio electrical signals into sound signals. Electronic devices can listen to music or make hands-free calls through the speaker 170A.

[0368] In this embodiment of the application, the electronic device can also output sound through the speaker 170A to provide message reminders.

[0369] The receiver 170B, also known as the "earpiece," is used to convert audio electrical signals into sound signals. When an electronic device answers a phone call or voice message, the receiver 170B can be brought close to the ear to hear the voice.

[0370] Microphone 170C, also known as a "microphone" or "voice transducer," is used to convert sound signals into electrical signals. When making a phone call or sending a voice message, the user can speak by bringing their mouth close to microphone 170C, inputting the sound signal into microphone 170C. Electronic devices can have at least one microphone 170C. In some embodiments, electronic devices can have two microphones 170C, which, in addition to collecting sound signals, can also perform noise reduction. In other embodiments, electronic devices can have three, four, or more microphones 170C, enabling sound signal collection, noise reduction, sound source identification, and directional recording, among other functions.

[0371] The 170D headphone jack is used to connect wired headphones. The 170D headphone jack can be a USB 130 interface or a 3.5mm Open Mobile Terminal Platform (OMTP) standard interface, a CTIA (Cellular Telecommunications Industry Association of the USA) standard interface.

[0372] Pressure sensor 180A is used to sense pressure signals and convert them into electrical signals. In some embodiments, pressure sensor 180A can be disposed on display screen 194. There are many types of pressure sensors 180A, such as resistive pressure sensors, inductive pressure sensors, and capacitive pressure sensors. A capacitive pressure sensor may include at least two parallel plates with conductive material. When force is applied to pressure sensor 180A, the capacitance between the electrodes changes. The electronic device determines the pressure intensity based on the change in capacitance. When a touch operation is applied to display screen 194, the electronic device detects the intensity of the touch operation based on pressure sensor 180A. The electronic device can also calculate the touch position based on the detection signal from pressure sensor 180A. In some embodiments, touch operations applied to the same touch position but with different touch operation intensities can correspond to different operation commands. For example: when a touch operation with an intensity less than a first pressure threshold is applied to the SMS application icon, a command to view an SMS is executed. When a touch operation with an intensity greater than or equal to the first pressure threshold is applied to the SMS application icon, a command to create a new SMS is executed.

[0373] Touch sensor 180K, also known as a "touch panel," can be located on display screen 194. The touch sensor 180K and display screen 194 together form a touchscreen, also known as a "touchscreen." Touch sensor 180K detects touch operations applied to or near it. The touch sensor can transmit the detected touch operation to the application processor to determine the type of touch event. Visual output related to the touch operation can be provided through display screen 194. In other embodiments, touch sensor 180K may also be located on the surface of the electronic device, in a different position than display screen 194.

[0374] Buttons 190 include a power button, volume buttons, etc. Buttons 190 can be mechanical buttons or touch-sensitive buttons. The electronic device can receive button input and generate key signal inputs related to user settings and function control of the electronic device.

[0375] Motor 191 can generate vibration alerts. Motor 191 can be used for incoming call vibration alerts or for touch vibration feedback. For example, different vibration feedback effects can be corresponding to touch operations applied to different applications (such as taking photos, playing audio, etc.). Motor 191 can also correspond to different vibration feedback effects for touch operations applied to different areas of the display screen 194. Different application scenarios (such as time reminders, receiving messages, alarm clocks, games, etc.) can also correspond to different vibration feedback effects. The touch vibration feedback effect can also be customized.

[0376] Indicator 192 can be an indicator light, used to indicate charging status, power changes, or to indicate messages, missed calls, notifications, etc.

[0377] The SIM card interface 195 is used to connect a SIM card. The SIM card can be inserted into or removed from the SIM card interface 195 to achieve contact and separation with the electronic device. The electronic device can support one or N SIM card interfaces, where N is a positive integer greater than 1. The SIM card interface 195 can support Nano SIM cards, Micro SIM cards, SIM cards, etc. Multiple cards can be inserted into the same SIM card interface 195 simultaneously. The multiple cards can be of the same or different types. The SIM card interface 195 is also compatible with different types of SIM cards. The SIM card interface 195 is also compatible with external memory cards. The electronic device interacts with the network through the SIM card to achieve functions such as calls and data communication. In some embodiments, the electronic device uses an eSIM, i.e., an embedded SIM card. The eSIM card can be embedded in the electronic device and cannot be separated from it.

[0378] In this embodiment of the application, the electronic device can receive SMS messages and incoming calls through SIM card and network interaction.

[0379] It should be understood that, Figure 14 The electronic device shown is merely an example, and electronic devices can have more than... Figure 14 The more or fewer components shown can be combined into two or more components, or they can have different component configurations. Figure 14 The various components shown can be implemented in hardware, software, or a combination of hardware and software, including one or more signal processing and / or application-specific integrated circuits.

[0380] This application provides a chip system including: a processor coupled to a memory for storing programs or instructions, wherein when the program or instructions are executed by the processor, the chip system implements the methods described in any of the above method embodiments.

[0381] Optionally, the chip system may contain one or more processors. These processors can be implemented in hardware or software. When implemented in hardware, the processor can be a logic circuit, an integrated circuit, etc. When implemented in software, the processor can be a general-purpose processor, implemented by reading software code stored in memory.

[0382] Optionally, the chip system may contain one or more memories. The memory may be integrated with the processor or disposed separately from it; this application embodiment does not limit this. For example, the memory may be a non-transient processor, such as a read-only memory (ROM), which may be integrated with the processor on the same chip or disposed separately on different chips. This application embodiment does not specifically limit the type of memory or the arrangement of the memory and processor.

[0383] For example, the chip system may be a field programmable gate array (FPGA), an application-specific integrated circuit (ASIC), a system on chip (SoC), a central processor (CPU), a network processor (NP), a digital signal processor (DSP), a microcontroller unit (MCU), a programmable logic device (PLD), or other integrated chips.

[0384] It should be understood that each step in the above method embodiments can be completed by integrated logic circuits in the processor hardware or by instructions in software form. The method steps disclosed in the embodiments of this application can be directly manifested as being executed by a hardware processor, or being executed by a combination of hardware and software modules in the processor.

[0385] 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. The 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 processes or functions described in this application are 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 computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the 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 computer-readable storage medium can be any available medium accessible to a computer 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, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid-state disk (SSD)).

[0386] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. This program can be stored in a computer-readable storage medium, and when executed, it can include the processes described in the above method embodiments. The aforementioned storage medium includes various media capable of storing program code, such as ROM or random access memory (RAM), magnetic disks, or optical disks.

[0387] The above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit it. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of this application.

Claims

1. A message notification method, characterized in that, Applied to an electronic device on which a first application is installed, the method includes: The electronic device activates a first scene mode, and the first application is an application that should not be disturbed. The electronic device receives a first message from the first application, the first message including a first identifier, the first identifier being used to indicate that the type of the first message is a first type; The electronic device provides a notification for the first message, wherein the first type belongs to a first preset type.

2. The method according to claim 1, characterized in that, The method further includes: The electronic device receives a second message from the first application, the second message including a second identifier, the second identifier being used to indicate that the type of the second message is a second type; The electronic device does not provide a notification for the second message, wherein the second type does not belong to the first preset type.

3. The method according to claim 1 or 2, characterized in that, The first preset type is the default of the electronic device, or the first preset type is selected by the user.

4. The method according to any one of claims 1-3, characterized in that, When the first scenario mode is enabled, the electronic device does not send notifications for any type of message from the first application; when the first scenario mode is not enabled, the electronic device sends notifications for any type of message from the first application. Before the electronic device receives the first message from the first application, the method further includes: The electronic device detects a first operation, which is used to activate a first function. The first function is used to instruct that when the first scenario mode is activated, a notification is sent to the first preset type of message received from the first application.

5. The method according to any one of claims 1-4, characterized in that, The electronic device is also equipped with a second application, and the method further includes: The electronic device receives a third message from the second application, the third message including a third identifier, the third identifier being used to indicate that the type of the third message is a third type; The electronic device provides a notification for the third message, wherein the third type belongs to the second preset type.

6. The method according to claim 5, characterized in that, The third message is different from the first message.

7. The method according to claim 6, characterized in that, The first message and the third message can be any of the following: SMS message, incoming call message, or live message.

8. The method according to claim 7, characterized in that, When the message is an SMS message, the SMS message includes an SMS verification code message; When the message is an incoming call message, the incoming call message includes incoming call messages where the incoming call number is a preset incoming call identifier, and the preset incoming call identifier includes a delivery / food delivery identifier and a ride-hailing identifier; When the message is a live message, the live message includes live messages from one or more of the following scenarios: ride-hailing, instant delivery, flights, high-speed rail / trains, queuing, food pickup, sports scores, shared rentals, timing, exercise, and navigation.

9. The method according to any one of claims 1-8, characterized in that, The electronic device provides a notification for the first message, specifically including: The electronic device reminds the first message through a first reminder method, which includes one or more of sound, vibration, and interface prompts.

10. The method according to claim 9, characterized in that, The interface prompts include one or more of the following: live window prompts and pop-up prompts.

11. The method according to any one of claims 1-10, characterized in that, The first application is a text messaging application. Before the electronic device receives a first message from the first application, the method further includes: The first application received the first SMS message; The first application generates the first message based on the first SMS message, and the first SMS message does not include the first identifier.

12. The method according to any one of claims 11, characterized in that, After the first application generates the first message based on the first SMS message, the method further includes: The first application generates a first identifier based on the content of the first message.

13. The method according to any one of claims 1-12, characterized in that, The first application is a live application. Before the electronic device receives the first message from the first application, the method further includes: The first application receives the first live message; The first application generates the first message based on the first live message, and the first live message includes the first identifier.

14. The method according to any one of claims 1-13, characterized in that, The electronic device includes a message management service module, and the electronic device receives a first message from the first application, specifically including: The message management service module receives the first message from the first application; Before the electronic device notifies the user of the first message, the method further includes: The message management service module determines the type of the first message as the first type based on the first identifier, and determines that the first type belongs to the first preset type.

15. The method according to claim 14, characterized in that, Before the message management service module determines that the type of the first message is the first type based on the first identifier, the method further includes: The message management service module determines that the electronic device has enabled the first scenario mode.

16. The method according to claim 14 or 15, characterized in that, The electronic device also includes a message notification module, which notifies the user of the first message, specifically including: The message notification module receives the fourth message sent by the message management service module; The message notification module provides a notification for the first message based on the fourth message.

17. An electronic device, characterized in that, The electronic device includes one or more processors and one or more memories; wherein the one or more memories are coupled to the one or more processors, and the one or more memories are used to store computer program code, the computer program code including computer instructions, which, when executed by the one or more processors, cause the electronic device to perform the method as described in any one of claims 1-16.

18. A computer storage medium, characterized in that, The computer storage medium stores a computer program, which includes program instructions that, when executed on an electronic device, cause the electronic device to perform the method as described in any one of claims 1-16.

19. A computer program product, when run on a computer, causes the computer to perform the method as described in any one of claims 1-16.

Images