Information processing method and electronic device

Abstract

The application provides an information processing method and an electronic device, and relates to the technical field of terminals. The method is applied to an electronic device. A mode setting interface for a first scene mode is displayed in the electronic device. In response to performing a setting operation in the mode setting interface, a trigger condition of the first scene mode and a first prompt element displayed in the first scene mode and used for prompting that the electronic device is in the first scene mode are set. The electronic device automatically starts the first scene mode in response to the trigger condition being met. During the duration of the first scene mode, the first prompt element is displayed. In this way, the trigger condition of the first scene mode and the first prompt element are personalized, the user's perception of the scene mode is enhanced, and the user's use experience is improved.

Description

Technical Field

[0001] This application relates to the field of terminal technology, and in particular to an information processing method and an electronic device. Background Technology

[0002] As electronic devices have become more sophisticated, the concept of "scenario modes" has emerged to better assist users in different usage environments (e.g., learning, working, sleeping). Users can adjust the appropriate strategies of their electronic devices in different environments by activating different scenario modes. These strategies can include changes such as response methods (e.g., only answering calls from whitelisted numbers), ringing patterns, and message receiving methods (e.g., only receiving SMS messages).

[0003] However, in daily use, users need to enter a context mode by setting the activation time or using activation controls when they require it. But once the electronic device is in context mode, the user's awareness of the context mode is relatively poor during the activation process. Summary of the Invention

[0004] This application provides an information processing method and an electronic device that personalizes the triggering conditions and the first prompt element of a first scenario mode, and enhances the user's perception of the scenario mode by displaying the first prompt element during the continuous process of the first scenario mode, thereby improving the user's experience in the scenario mode.

[0005] To achieve the above objectives, the embodiments of this application adopt the following technical solutions:

[0006] Firstly, this application provides an information processing method applied to an electronic device. The electronic device includes multiple scenario modes, including a first scenario mode. Firstly, a mode setting interface for the first scenario mode is displayed in the electronic settings. Users can perform setting operations in the mode setting interface to configure the triggering conditions of the first scenario mode and the first prompt element displayed in the first scenario mode to indicate that the electronic device is in the first scenario mode, thereby achieving personalized settings for the triggering conditions and the first prompt element. Secondly, the electronic device automatically activates the first scenario mode in response to the fulfillment of the triggering conditions. Furthermore, it can also assist users in activating the first scenario mode in a timely manner when they cannot do so. Finally, during the continuous operation of the first scenario mode, the display of the first prompt element enhances the user's perception of the scenario mode.

[0007] In one possible implementation of the first aspect, when configuring the condition settings in the mode settings interface, firstly, in response to a setting operation performed on the condition settings, first information about the first scenario mode is obtained. Secondly, based on the first information, the triggering conditions of the first scenario mode and the first prompt element displayed under the first scenario mode are obtained. In this way, personalized settings for the triggering conditions and the first prompt element of the first scenario mode are achieved.

[0008] In one possible implementation of the first aspect, the first information is obtained from a first application or from a first file.

[0009] In one possible implementation of the first aspect, when setting condition settings and task settings, firstly, in response to a setting operation performed on a condition setting, first information of the first scenario mode is obtained. Secondly, in response to a setting operation performed on a task setting, the pending tasks to be completed in the first scenario mode are obtained. Finally, based on the first information and the pending tasks, the triggering conditions of the first scenario mode and the first prompt element displayed in the first scenario mode are obtained.

[0010] In one possible implementation of the first aspect, when setting task settings, firstly, in response to a setting operation performed on the task settings in the mode setting interface, the task setting interface is displayed. Secondly, at least one pending task to be completed in the first scenario mode is set in the task setting interface.

[0011] In one possible implementation of the first aspect, when only task settings are configured, in response to the configuration operation performed on the task settings, the scenario mode module obtains the to-do task to be completed in the first scenario mode. Secondly, based on the to-do task, the scenario mode module obtains the first prompt element to be displayed in the first scenario mode.

[0012] In one possible implementation of the first aspect, when displaying the first prompt element, firstly, a persistent live notification is displayed to inform the user that they are currently in the first scenario mode. This achieves the purpose of informing the user while minimizing the obstruction of the interface caused by the first prompt element. Secondly, in response to a triggering operation performed on the persistent live notification, a live window is displayed. This allows the user to be prompted only when they require the live window to be displayed, even if it has a larger obstructing area. Therefore, during the continuation of the first scenario mode, the obstruction of the interface caused by the first prompt element can be minimized.

[0013] The persistent live notification includes the first content of the first prompt element; the live window includes the second content of the first prompt element, and the first and second contents are different.

[0014] In one possible implementation of the first aspect, during the process of displaying the first prompt element through a live window, firstly, the live window includes at least one to-do task displayed in a first manner, the at least one to-do task including a first to-do task, to indicate that the first to-do task is in an incomplete state by displaying the first to-do task in the first manner. Secondly, in response to a triggering operation performed on the first to-do task, the display mode of the first to-do task is switched to a second mode, to indicate that the first to-do task has been completed by displaying the to-do task in the second mode.

[0015] In one possible implementation of the first aspect, while the first prompt element is displayed in a persistent live notification within a notification window, a trigger operation performed on the persistent live notification is responded to, and the mode settings interface for the first scenario mode is displayed. This achieves a "one-click" jump from the display interface to the mode settings interface. In other words, users no longer need to perform complex operations to enter the settings interface to trigger the display of the mode settings interface, thereby reducing the complexity of the operations required to enter the mode settings interface.

[0016] In one possible implementation of the first aspect, when the first prompt element is displayed, a live notification is displayed to inform the user that they are currently in the first scenario mode.

[0017] The live notification includes the third content of the first notification element; the display area of ​​the live notification includes the area where the camera aperture of the electronic device is located. In other words, when the live notification is displayed, it "blends" with the camera aperture of the electronic device, thereby reducing interface obstruction and presenting a more aesthetically pleasing display effect.

[0018] In one possible implementation of the first aspect, when the display duration of the live notification on the interface exceeds a preset time threshold, the live notification is canceled, and a notification icon is displayed on the interface, and / or a status bar indicator is displayed. In this way, the live notification can be "replaced" by a notification icon that minimizes interface obstruction, continuously reminding the user that they are currently in the first scenario mode, thereby further reducing the obstruction caused by the display of the first notification element on the interface.

[0019] In one possible implementation of the first aspect, after displaying the live notification, firstly, in response to an operation on the live notification, options for a first scenario mode are displayed. Secondly, in response to an operation on a first option of the first scenario mode, the first scenario mode is exited, and the options of the first scenario mode include the first option. And / or, in response to an operation on a second option of the first scenario mode, a mode settings interface for the first scenario mode is opened, and the options of the first scenario mode include the second option.

[0020] In one possible implementation of the first aspect, the notification icon is displayed around the area where the camera aperture is located. This allows for a continuous reminder to the user that they are currently in the first scenario mode by "replacing" the live notification with a notification icon that minimizes interface obstruction, thereby further reducing the obstruction caused by the display of the first notification element on the interface.

[0021] In one possible implementation of the first aspect, in response to a triggering action on a notification icon, a live window is displayed to prompt the user using the live window, which can display more detailed prompt information, thereby enriching the prompt information for prompting the user.

[0022] The live window includes a second content of the first prompt element, which is different from the third content.

[0023] In one possible implementation of the first aspect, during the display of the first prompt element through the live window, a trigger operation performed on the live window is responded to, and the task settings interface of the first scenario mode is displayed. Thus, even when the user has not set any tasks, and the screen is locked, the user can use the live window to achieve a "one-click" jump from the display interface to the task settings interface. In other words, the user no longer needs to perform complex operations to enter the settings interface to trigger the display of the task settings interface, thereby reducing the complexity of the operations required to enter the task settings interface.

[0024] In one possible implementation of the first aspect, during the display of the first prompt element via a live window and / or live notification, in response to a triggering operation for the live window or live notification, the first scenario mode is exited and the display of the first prompt element is stopped.

[0025] In one possible implementation of the first aspect, during the process of displaying the first notification element via a capsule notification on the lock screen, a live window of the lock screen is displayed in response to a triggering operation on the capsule notification.

[0026] In one possible implementation of the first aspect, in response to exiting the first scenario mode, a second prompt element is displayed to indicate to the user that the first scenario mode has been exited, and to further enhance the user's awareness of the first scenario mode.

[0027] In one possible implementation of the first aspect, the first prompt element is displayed on one or more of the home screen, lock screen, and always-on screen. And / or,

[0028] The first notification element can be displayed as one or more of the following: status bar icon, notification window notification, home screen desktop component, lock screen desktop live window, home screen desktop live window, always-on screen live window, lock screen desktop live notification, home screen desktop live notification, and always-on screen desktop live notification.

[0029] Live notifications include instant live notifications and persistent live notifications; instant live notifications include one or more of the following: capsule notifications on the lock screen, capsule notifications on the home screen, capsule notifications on the always-on display, card notifications on the lock screen, card notifications on the home screen, and card notifications on the always-on display; persistent live notifications include one or more of the following: capsule notifications on the lock screen, capsule notifications on the home screen, capsule notifications on the always-on display, card notifications on the lock screen, card notifications on the home screen, and card notifications on the always-on display.

[0030] In one possible implementation of the first aspect, when the triggering condition includes a first triggering condition, firstly, in response to a setting operation performed on a condition setting item, at least one candidate option for setting the first triggering condition is displayed. Secondly, in response to a selection operation performed on a third option among the at least one candidate option, the display module displays a configuration interface for the third option. Finally, the first triggering condition of the first scenario mode is set in the configuration interface of the third option.

[0031] In one possible implementation of the first aspect, when the triggering condition further includes a second triggering condition, firstly, an updated mode setting interface is displayed. Secondly, in response to a setting operation performed on a condition setting item, at least one candidate option for setting the second triggering condition is displayed. Then, in response to a selection operation performed on a fourth option among the at least one candidate option, the display module displays a configuration interface for the fourth option. Finally, the second triggering condition of the first scenario mode is set in the configuration interface of the fourth option.

[0032] In one possible implementation of the first aspect, firstly, the display module displays a first prompt message in the task configuration interface. Secondly, when the number of at least one pending task exceeds a preset threshold, the display module displays a second prompt message in the task configuration interface. This way, by providing prompts to the user, it assists the user in setting an appropriate number of pending tasks, reducing the probability of repeatedly triggering the task configuration interface and the probability of displaying too many pending tasks on the interface.

[0033] The first prompt message indicates that adding more to-do tasks is allowed, thus notifying the user that they can add more to-do tasks. The second prompt message indicates that the maximum number of configured to-do tasks has been reached, thus notifying the user that the maximum number of to-do tasks has been reached.

[0034] In one possible implementation of the first aspect, when at least one to-do task displayed in the live window has been completed, a third notification message is displayed in the live window to notify the user that all to-do tasks have been completed.

[0035] The third prompt message indicates that the user has completed all the to-do tasks. The third prompt message includes: the duration of the first mode, the motivational message, the motivational icon, etc.

[0036] In a second aspect, an electronic device is provided, the electronic device including a memory and one or more processors; the memory is coupled to the processors; wherein the memory stores computer program code, the computer program code including computer instructions, and when the computer instructions are executed by the processor, the electronic device performs the information processing method as described in the first aspect and any implementation thereof.

[0037] Thirdly, a computer-readable storage medium is provided, including computer instructions that, when executed on an electronic device, cause the electronic device to perform the information processing method as described in the first aspect and any implementation thereof.

[0038] Fourthly, a computer program product is provided that, when run on an electronic device, causes the electronic device to execute the information processing method as described in the first aspect and any of its implementations.

[0039] The beneficial effects that the electronic equipment provided in the second aspect, the computer-readable storage medium provided in the third aspect, and the computer program product provided in the fourth aspect can achieve can be referred to the beneficial effects that can be achieved in the first aspect and any of its implementations, and will not be repeated here. Attached Figure Description

[0040] Figure 1 This illustration shows one of the schematic diagrams of a mode setting interface provided in an embodiment of this application;

[0041] Figure 2 A schematic diagram of the hardware structure of an electronic device provided in an embodiment of this application is shown;

[0042] Figure 3 A schematic diagram of the software structure of an electronic device provided in an embodiment of this application is shown;

[0043] Figure 4 A flowchart of an information processing method provided in an embodiment of this application is shown;

[0044] Figure 5 This illustration shows a second schematic diagram of a mode setting interface provided in an embodiment of this application;

[0045] Figure 6This illustration shows a configuration interface diagram provided in an embodiment of this application;

[0046] Figure 7 This is shown as a third schematic diagram of a mode setting interface provided in an embodiment of this application;

[0047] Figure 8 This illustration shows one of the task setting interfaces provided in an embodiment of this application;

[0048] Figure 9 This is a second schematic diagram of a task setting interface provided in an embodiment of this application;

[0049] Figure 10 This illustration shows a lock screen interface provided in an embodiment of this application;

[0050] Figure 11 This illustration shows one of the schematic diagrams of a first prompt element display provided in an embodiment of this application;

[0051] Figure 12 This illustration shows a second schematic diagram of a first prompt element display provided in an embodiment of this application;

[0052] Figure 13 This document shows a fourth schematic diagram of a mode setting interface provided in an embodiment of this application.

[0053] Figure 14 This illustration shows a schematic diagram of a notification icon display provided in an embodiment of this application;

[0054] Figure 15 This is a third schematic diagram of a task setting interface provided in an embodiment of this application;

[0055] Figure 16 This illustration shows a third schematic diagram of a first prompt element display provided in an embodiment of this application;

[0056] Figure 17 This illustration shows a fourth schematic diagram of a first prompt element display provided in an embodiment of this application;

[0057] Figure 18 This illustration shows one of the schematic diagrams of a second prompt element display provided in an embodiment of this application;

[0058] Figure 19 This illustration shows a second schematic diagram of a second prompt element display provided in an embodiment of this application;

[0059] Figure 20 This illustration shows one of the module association diagrams provided in an embodiment of this application;

[0060] Figure 21This illustrates a second schematic diagram of module association provided in an embodiment of this application;

[0061] Figure 22 This illustrates a third schematic diagram of module association provided in an embodiment of this application;

[0062] Figure 23 This illustration shows a schematic diagram of a module interaction provided in an embodiment of this application;

[0063] Figure 24 A schematic diagram of the hardware structure of another electronic device provided in an embodiment of this application is shown. Detailed Implementation

[0064] The technical solutions of the embodiments of this application will be described below with reference to the accompanying drawings. In the description of this application, unless otherwise stated, " / " indicates that the objects before and after are in an "or" relationship. For example, A / B can represent A or B. "And / or" in this application 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 alone, A and B simultaneously, and B alone, where A and B can be singular or plural. Furthermore, in the description of this application, unless otherwise stated, "multiple" refers to two or more. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can represent: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple. Furthermore, to facilitate a clear description of the technical solutions in the embodiments of this application, the terms "first" and "second" are used in the embodiments of this application to distinguish identical or similar items with substantially the same function and effect. Those skilled in the art will understand that the terms "first" and "second" do not limit the quantity or execution order, and that "first" and "second" are not necessarily different. Meanwhile, in the embodiments of this application, the terms "exemplary" or "for example" are used to indicate that something is being used as an example, illustration, or description. Any embodiment or design scheme described as "exemplary" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or design schemes. Specifically, the use of terms such as "exemplary" or "for example" is intended to present related concepts in a concrete manner for ease of understanding.

[0065] Furthermore, the business scenarios described in the embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided by the embodiments of this application. As those skilled in the art will know, with the emergence of new business scenarios, the technical solutions provided by the embodiments of this application are also applicable to similar technical problems.

[0066] As electronic devices have become more sophisticated, the concept of "scenario modes" has been proposed to better assist users in different usage environments (e.g., learning, working, sleeping). When a user is in a usage environment with specific response needs, the appropriate strategies adopted by the electronic device in the current usage environment can be adjusted by configuring settings such as "filtering conditions" (e.g., application filtering conditions, system filtering conditions) or "allowing conditions" (e.g., application allowing conditions, system allowing conditions). These settings can include response methods (e.g., only answering calls from whitelisted numbers), ringing methods, and message receiving methods (e.g., only receiving SMS messages).

[0067] Specifically, such as Figure 1 As shown, taking Focus Mode as an example, the electronic device displays the Focus Mode settings interface. This interface includes filtering conditions that can be used to adjust the electronic device's response strategy in Focus Mode, such as application filtering conditions and system filtering conditions. When a user needs to activate Focus Mode, they can configure application filtering conditions to set which email messages, music notifications, and conversations need to be filtered during Focus Mode activation, and configure system filtering conditions to set the electronic device's ringing mode (e.g., enabling silent mode, low battery mode), etc., so that calls can be received according to the user's needs when Focus Mode is activated.

[0068] However, when an electronic device enters a context mode, the user's perception of the context mode is poor during the activation process. In some cases, the user can only perceive the activation of the context mode by changing the ringtone, which results in a poor user experience.

[0069] Based on the above, this application provides an information processing method. First, a mode setting interface for a first scenario mode is displayed in the electronic settings. Users can perform setting operations in the mode setting interface to configure the trigger conditions for the first scenario mode and the first prompt element displayed in the first scenario mode to indicate that the electronic device is in the first scenario mode, thereby achieving personalized settings for the trigger conditions and the first prompt element. Second, the electronic device automatically activates the first scenario mode in response to meeting the trigger conditions, thus assisting users in activating the first scenario mode when they cannot do so in a timely manner. Finally, during the continuous operation of the first scenario mode, displaying the first prompt element enhances the user's perception of the scenario mode, thereby improving the user experience.

[0070] The electronic device 100 involved in the information processing method described in this application embodiment can be found in [reference needed]. Figure 2 As shown. Electronic device 100 may include processor 110, external memory interface 120, internal memory 121, universal serial bus (USB) interface 130, charging management module 140, power management module 141, battery 142, antenna 1, antenna 2, mobile communication module 150, wireless communication module 160, display screen 170, etc.

[0071] It is understood that the structures illustrated in the embodiments of this application do not constitute a specific limitation on the electronic device 100. In other embodiments of this application, the electronic device 100 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.

[0072] 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.

[0073] The processor 110 may also include a memory for storing instructions and data, such as the trigger conditions for the first scenario mode and related data of the first prompt element. 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 is using repeatedly, such as the trigger conditions for the first scenario mode and related data of the first prompt element. If the processor 110 needs to use the instruction or data again, it can directly retrieve it from the memory. This avoids repeated access, reduces the waiting time of the processor 110, and thus improves the efficiency of the system.

[0074] USB port 130 is a USB standard compliant interface, specifically 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 device 100, and can also be used for data transfer between electronic device 100 and peripheral devices. It can also be used to connect headphones for audio playback. This interface can also be used to connect other electronic devices, such as AR devices.

[0075] 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 the 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 100. While charging the battery 142, the charging management module 140 can also supply power to the electronic device via the power management module 141.

[0076] The power management module 141 is used to connect 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, and provides power to the processor 110, internal memory 121, and external memory. Figure 2 (Not shown in the image), power supply for display screen 170 and wireless communication module 160, etc.

[0077] The mobile communication module 150 can provide solutions for wireless communication, including 2G / 3G / 4G / 5G, applied to the electronic device 100. 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 the 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.

[0078] A 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.

[0079] The wireless communication module 160 can provide solutions for wireless communication applications on the electronic device 100, 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.

[0080] In some embodiments, antenna 1 of electronic device 100 is coupled to mobile communication module 150, and antenna 2 is coupled to wireless communication module 160, so that electronic device 100 can communicate with networks and other devices through wireless communication technology.

[0081] Electronic device 100 implements display functions through a GPU, a display screen 170, and an application processor. The GPU is a microprocessor for image processing, connected to the display screen 170 and the application processor. The GPU is used to perform mathematical and geometric calculations and for graphics rendering. Processor 110 may include one or more GPUs, which execute program instructions to generate or modify display information.

[0082] The display screen 170 is used to display images, videos, mode setting interfaces related to scene modes, etc. The display screen 170 includes a display panel. The display panel can 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 MiniLED, a MicroLED, a Micro-OLED, a quantum dot light-emitting diode (QLED), etc. In some embodiments, the electronic device 100 may include one or N displays 170, where N is a positive integer greater than 1.

[0083] The external storage interface 120 can be used to connect an external storage card, such as a Micro SD card, to expand the storage capacity of the electronic device 100. The external storage card communicates with the processor 110 through the external storage interface 120 to perform data storage functions. For example, files such as music, videos, trigger conditions for the first scene mode, and related data of the first prompt element can be stored on the external storage card.

[0084] 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 electronic device 100 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, scene mode, etc.). The data storage area may store data created during the use of electronic device 100 (such as audio data, phonebook, trigger conditions for the first scene mode, related data of the first prompt element, 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.

[0085] The electronic device provided in this application embodiment can run an operating system (OS). This operating system can be various operating systems used in the industry, such as an operating system based on OpenHarmony, like HarmonyOS; or other operating systems such as Android. TM An operating system can refer to 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; or it can refer to future new operating systems, such as AI operating systems 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 interactions. In electronic devices, the operating system connects downwards to the physical devices at the hardware layer and upwards to provide a runtime environment for application software.

[0086] 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, such as... Figure 3As shown. The middleware layer includes a series of software providing various services to application developers, or frameworks providing various services such as databases, multimedia, and graphics, or capabilities such as distributed scheduling and system expansion. For example, the middleware layer may include 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 core capabilities of the system, providing services to applications through the framework layer. The kernel layer is the layer between hardware and software. The kernel layer may 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.

[0087] 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. 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 Android. TM Implementation under operating systems, etc.

[0088] The software architecture of electronic devices 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. Layers communicate with each other through software interfaces. System functions can be tailored, added, or combined at the subsystem level depending on the deployment scenario of different device forms. Each subsystem can also be tailored, added, or combined at the functional level.

[0089] The kernel layer includes, but is not limited to: the kernel abstract layer (KAL), the kernel subsystem, and the driver subsystem.

[0090] Kernel Abstraction Layer: By shielding the differences between multiple kernels, it provides basic kernel capabilities to the upper layers, including but not limited to process / thread management, memory management, file system, network management, and peripheral device management.

[0091] 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 (Lite Operating System), etc.

[0092] 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.

[0093] The system service layer comprises the core capabilities of the system, providing services to applications through the framework layer. This layer involves multiple subsystem sets, including but not limited to: basic system capability subsystem set, basic software service subsystem set, enhanced software service subsystem set, and hardware service subsystem set.

[0094] The system's basic capability subsystem set provides fundamental capabilities for the operation, scheduling, and migration of distributed applications across multiple devices. This set may include distributed soft bus, distributed data management, distributed task scheduling, and Ark multi-language runtime; it may also include multi-modal input subsystem, graphics subsystem, security subsystem, and AI business subsystem.

[0095] Basic software service subsystem set: provides public and general software services; the basic software service subsystem set may include event notification subsystem, telephone service subsystem, multimedia subsystem, etc.

[0096] Enhanced software service subsystem suite: Provides differentiated enhanced software services for different devices; the enhanced software service subsystem suite may include smart screen proprietary business subsystem, wearable proprietary business subsystem, IoT proprietary business subsystem, etc.

[0097] Hardware service subsystem set: Provides hardware services; the hardware service subsystem set 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.

[0098] 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.

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

[0100] 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 StarFlash communication capabilities.

[0101] Ark Multilingual Runtime is a unified compilation runtime platform designed to support the joint compilation and execution of multiple programming languages ​​and multiple chip platforms.

[0102] The framework layer provides application programming interfaces (APIs) and programming frameworks for applications in the application layer. The framework layer includes: the ArkUI framework (which provides a complete infrastructure for UI development of system applications, including UI functions such as components, layouts, animations, and interactive events, as well as a real-time interface preview tool), 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 have different operating systems, and the APIs they support may also differ.

[0103] 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. The HarmonyOS API includes the Audio API (audio service), Push API (push service), and Account API (account service), among others.

[0104] Applications can include system apps and extended / third-party apps. System apps can include settings, contacts, phone, camera, and database (Settings data). Figure 3 (not shown in the image), etc.

[0105] Here, the electronic device can display an interface, including the main screen, lock screen, always-on-display (AOD) screen, etc., and can also display a control bar (or status bar) and notification window within the interface. Figure 3 (Not shown in the image), Live notification ( Figure 3 (Not shown in the image), Live Stream Window ( Figure 3 (not shown in the image), etc. Extended applications / third-party applications can include social applications, travel applications, etc.

[0106] Electronic devices can display various interfaces, status bars, live notifications, live windows, and other content through different display modules. Specifically, display modules can include a main screen module, lock screen module, AOD (Away From Home) module, status bar module, and live window module. The main screen module displays the main screen interface. The lock screen module displays relevant content on the lock screen. The AOD module displays the AOD interface. The status bar module displays the status bar. The live window module displays live notifications and live windows.

[0107] In some examples, electronic devices can display primary prompts in the form of cards, a form of interface display. In the HarmonyOS system, universal cards are an optional component of applications and meta-services, allowing important information or operations to be placed at the forefront, achieving direct service access and reducing operational layers. Universal cards are often embedded in other system applications (desktop / minus one screen) as part of their interface, supporting click-to-launch of applications or meta-services. This allows users to access the display and dynamic changes of important information within services without opening meta-services, such as weather, key event memos, and lists of trending news.

[0108] Here, the scenario mode module in the electronic device is used to execute the step of activating the first scenario mode. Furthermore, the scenario mode module can also send a live notification to the live module when the first scenario mode is activated. The electronic device includes various scenario modes, such as focus mode, study mode, sleep mode, work mode, do not disturb mode, outdoor mode, silent mode, meeting mode, etc. The mode setting interfaces for different scenario modes can be the same or different.

[0109] For example, in sleep mode, users expect to receive fewer calls. In this case, considering that setting "filtering conditions" would require a lot of settings, when users set sleep mode, the settings interface corresponding to sleep mode can provide relevant settings for "allowed conditions" so that users only need to set the allowed calls, which simplifies the complexity of the settings operation that users need to perform when setting the scenario mode.

[0110] For another example, in work mode, users do not want to miss incoming calls. In this case, considering that the user needs to set "filter conditions" with less content, when the user sets the work mode, the relevant settings for "filter conditions" can be provided in the mode settings interface corresponding to the work mode, so that the user only needs to set the incoming calls that are not answered, which can also simplify the complexity of the setting operation that the user needs to perform when setting the scenario mode.

[0111] In this way, users can use different mode setting interfaces to specifically set the response strategy of electronic devices in different scenario modes, so that the set response strategy can be more suitable for the usage scenario applicable to that scenario mode, and thus help users to activate the scenario mode in a timely manner.

[0112] The electronic device also includes a calendar module, which is used to provide calendar information to users and receive course schedules configured / imported by users in the calendar.

[0113] The perception module allows users to define perception events for various scenario modes. The perception module can monitor the triggering conditions of scenario modes and notify the scenario mode module to activate (or switch) the scenario mode when the triggering time specified by the triggering conditions is reached.

[0114] The Advanced Notification Service (ANS) module (or Event Notification Subsystem) provides applications with the ability to subscribe to, publish, and unsubscribe from public events. Applications can subscribe to public events on demand. Once a public event is published, the system sends it to the applications that have subscribed to it. These public events may originate from the system (e.g., enabling the first-person scenario mode), other applications, or the application itself (applications may define custom public events to implement cross-application event communication capabilities, such as communication between the scenario mode module and the lock screen module, or between the scenario mode module and the sensing module).

[0115] The information processing method provided in this application can be applied to smart devices such as mobile phones, tablets, laptops, and desktop computers. Alternatively, the electronic devices can also include wearable devices such as head-mounted display devices (e.g., virtual reality devices, augmented reality devices, mixed reality devices), smartwatches, smart bracelets, and smart glasses. Furthermore, the electronic devices can also include smart home devices (such as televisions) and in-vehicle systems (such as vehicle terminals). The mobile phone can be a foldable screen phone or a non-foldable screen phone.

[0116] The following describes an information processing method provided by an embodiment of this application. This method is applied to an electronic device, which includes multiple scene modes, including a first scene mode. The method will be described using an electronic device comprising a display module and a scene mode module as an example. Figure 4 As shown, the method may include the following steps S401 to S404.

[0117] S401, The display module of the electronic device displays the mode setting interface of the first scenario mode.

[0118] In some implementations, the mode setting interface is displayed on the main screen of the electronic device. When the display module displays the mode setting interface of the first scenario mode, firstly, the main screen module in the display module obtains (or pulls up) the interface data of the mode setting interface of the first scenario mode from the scenario mode module. Secondly, the main screen module uses the interface data of the mode setting interface of the first scenario mode to display the mode setting interface of the first scenario mode on the main screen of the electronic device.

[0119] For example, the mode setting interface of the first scenario mode, such as Figure 5 As shown. The mode settings interface for the first scenario mode may include: mode activation control, condition settings, task settings, associated functions, allowed items, and filtering items. Figure 5 (Not shown in the image). The mode activation control is used to activate the first scenario mode. Once activated, the first scenario mode will automatically activate as needed, based on the trigger conditions in the condition settings. The condition settings are used to set the trigger conditions for the first scenario mode. The scenario mode module can detect these trigger conditions and execute actions such as issuing a command to activate the first scenario mode and sending real-time notifications. The task settings are used to set the to-do items that the user needs to complete in the first scenario mode. The association function is used to set the display mode of the mode settings interface, such as dark mode, eye protection mode, power saving mode, etc. The allowed items are used to set the incoming calls, received application information, and meta-services that are allowed to be answered in the first scenario mode. The filter items are used to set the incoming calls, received application information, and meta-services that are not allowed to be answered in the first scenario mode.

[0120] S402, In response to the setting operation performed in the mode setting interface, the scenario mode module obtains the triggering condition and the first prompt element of the first scenario mode.

[0121] For example, the scenario mode module can save the triggering conditions and the first prompt element of the first scenario mode to the database. In this way, users can personalize the triggering conditions and prompt information of the first scenario mode through the mode setting interface.

[0122] The first prompt element is used to indicate that the electronic device is in a first scenario mode. This element can display prompt information related to the first scenario mode. The prompt information can indicate the tasks to be completed in the first scenario mode, the location where the first scenario mode is activated, the time period during which the first scenario mode is activated, and the duration of the first scenario mode. For example, if the first scenario mode is a learning mode, the prompt information includes at least one of the following: the start time of the course, the location of the class, the course name, and the instructor's name. If the first scenario mode is a sleep mode, the prompt information includes at least one of the following: the start time of the sleep mode, the end time, and the ringing method during the sleep mode. If the first scenario mode is a work mode, the prompt information includes at least one of the following: the start time of a work meeting, the meeting room location, the meeting topic, and the participants.

[0123] Here, the first prompt element can be displayed through the live window, live notifications (e.g., instant live notifications, persistent live notifications), status bar icons, etc.

[0124] The aforementioned setting operation can refer to an operation performed by a user using a touch device on an electronic device. This can include single-point touch operations (e.g., tap, single click, long press, etc.) and multi-point touch operations, swipe operations, drag operations, etc., such as tapping a condition setting item in the mode settings interface. Alternatively, the setting operation can also refer to a voice control operation performed by a user using a sound acquisition device (e.g., a microphone) on a handheld electronic device. Alternatively, the setting operation can also refer to an operation performed by a user using an additional input device (e.g., a game controller, mouse, keyboard, etc.).

[0125] Here, the mode settings interface for the first scenario mode may include condition settings and / or task settings. Users can selectively configure the condition settings and / or task settings (or leave them unconfigured) to personalize the first scenario mode. Users can use at least three settings methods during the mode settings interface configuration: Method 1, setting only condition settings, i.e., setting only the trigger conditions for the first scenario mode; Method 2, setting both condition settings and task settings, i.e., setting both the trigger conditions for the first scenario mode and the tasks to be completed under the first scenario mode; Method 3, setting only task settings, i.e., setting only the tasks to be completed under the first scenario mode.

[0126] When the user sets different tasks, the content displayed by the first prompt element will also change accordingly. For example, taking the first scenario mode as the learning mode, if the user only sets the trigger conditions for the learning mode (that is, the condition settings), the content displayed by the first prompt element will only include the prompt information that can be obtained from the trigger conditions, such as the start time of the learning mode and the class location; however, if the user additionally configures to-do tasks (that is, the task settings), the content displayed by the first prompt element will include not only the start time of the learning mode and the class location, but also the to-do tasks that need to be completed in the learning mode.

[0127] Therefore, under the above-mentioned various settings, the scenario mode module can obtain the first prompt element that can be displayed in the first scenario mode according to the user's settings for condition settings and task settings.

[0128] In some examples, when a user uses method one above to configure only the conditional settings in the mode settings interface, firstly, in response to the setting operation performed on the conditional settings, the scenario mode module obtains the first information of the first scenario mode. Secondly, based on the first information, the scenario mode module obtains the triggering conditions of the first scenario mode and the first prompt element displayed under the first scenario mode.

[0129] The scenario mode module, after obtaining the first information, the triggering condition of the first scenario mode, and the first prompt element displayed under the first scenario mode, can save the first information, the triggering condition, and the first prompt element to the database.

[0130] The first information can be obtained from a first application installed on the electronic device. For example, the first information can be a timetable obtained from a calendar application, time information obtained from a clock application, location information obtained from a map application, etc. Alternatively, the first information can also be obtained from a first file downloaded to the electronic device (or stored in a cloud device corresponding to the electronic device), such as a timetable downloaded by the electronic device from an application software, or a meeting notification downloaded by the electronic device from a cloud device, etc.

[0131] Here, users can set at least two trigger conditions for the first scenario mode, so that the scenario mode module can more accurately determine the activation time of the first scenario mode based on the at least two trigger conditions set by the user.

[0132] In some implementations, when the triggering condition includes a first triggering condition, firstly, in response to a setting operation performed on a condition setting item, the display module displays at least one candidate option for setting the first triggering condition. Secondly, in response to a selection operation performed on a third option among the at least one candidate option, the display module displays a configuration interface for the third option. Finally, the first triggering condition for the first scenario mode is set in the configuration interface of the third option.

[0133] The display module can overlay at least one candidate option for setting the first trigger condition in the mode setting interface in the form of a "card". The display module can also display at least one candidate option for setting the first trigger condition on other interfaces, depending on the specific situation, and there are no restrictions here.

[0134] The selection operation described above can refer to an operation performed by a user using a touch device on an electronic device, which can include single-point touch operations (e.g., tap, single click, long press, etc.) and multi-point touch operations, swipe operations, drag operations, etc., such as tapping the first option. Alternatively, the selection operation can also refer to a voice control operation performed by a user using a sound acquisition device (e.g., microphone, etc.) on a handheld electronic device. Alternatively, the selection operation can also refer to an operation performed by a user using an additional input device (e.g., game controller, mouse, keyboard, etc.).

[0135] In some examples, when the display module displays at least one candidate option for configuring the first trigger condition, firstly, the main screen module in the display module obtains (or pulls up) the option data of at least one candidate option from the scenario mode module. Secondly, the main screen module uses the option data of at least one candidate option to display the at least one candidate option selectable by the user in the mode settings interface.

[0136] In other examples, when the display module displays the configuration interface for the third option, firstly, the main screen module within the display module retrieves (or pulls up) the interface data for the configuration interface of the third option from the scenario mode module. Secondly, the main screen module uses the interface data for the configuration interface of the third option to display the configuration interface of the third option on the main screen interface of the electronic device.

[0137] In different scenario modes, the at least one candidate option displayed by setting conditional settings can be different or the same. For example, when the first scenario mode is study mode, the at least one candidate option displayed may include: timed, when the application is launched, when the location is nearby, and calendar schedule. When the first scenario mode is sleep mode, the at least one candidate option displayed may include: timed, when the application is launched, monitoring vital signs, and sleep schedule. When the first scenario mode is work mode, the at least one candidate option displayed may include: timed, when the application is launched, when the location is nearby, and meeting schedule.

[0138] Here, "Timed" is used to set the activation period of the first scenario mode; that is, to activate the first scenario mode within a specified time period. "When App Opens" is used to set the trigger application for the first scenario mode; that is, to activate the first scenario mode when the user opens a specified application. "When Near Location" is used to set the trigger location for the first scenario mode; that is, to activate the first scenario mode when the electronic device is near a specified location. "Calendar Schedule" is used to set the schedule for activating the learning mode; that is, by associating with the calendar schedule, the learning mode is activated based on the class times in the calendar schedule. "Sleep Schedule" is used to set the sleep schedule for activating the sleep mode; that is, by associating with the sleep schedule, the sleep mode is activated based on the rest times in the sleep schedule. The sleep schedule can be user-defined or summarized by monitoring the user's vital signs (e.g., heart rate, respiration, etc.). "Monitor Vital Signs" is used to set the vital signs information required to activate the sleep mode; that is, to activate the sleep mode by monitoring the vital signs set by the user. "Meeting Schedule" is used to set the schedule for activating the work mode; that is, by associating with the meeting schedule, the work mode is activated based on the meeting times in the meeting schedule.

[0139] For example, taking the first scenario mode as the learning mode, the main screen of the electronic device displays the mode settings interface for the learning mode. The mode settings interface for the learning mode includes a mode activation control, condition settings (i.e., "add trigger method"), task settings (i.e., "learning plan"), associated functions, and allowed items, such as... Figure 6 As shown in (a). After the user clicks on "Add Trigger Method", at least one candidate option is displayed: scheduled, when the application starts, when nearby, and calendar / timetable, as shown. Figure 6 As shown in (b), the calendar timetable configuration interface is displayed after the user makes a selection. The calendar timetable configuration interface displays multiple linked timetables (e.g., Timetable 1, Timetable 2), as shown in (b). Figure 6 As shown in (c), users can select from multiple timetables and set the selected timetable 1 and timetable 2 as the first trigger conditions for the learning mode. Thus, when the start time of a course in timetable 1 or timetable 2 arrives, the scenario mode module can automatically activate the learning mode.

[0140] After setting the first trigger condition, the user can again use the mode setting interface to set a second trigger condition for activating the first scenario mode. In some implementations, when the trigger condition also includes a second trigger condition, firstly, the display module displays the updated mode setting interface. Secondly, in response to a setting operation performed on a condition setting item, the display module displays at least one candidate option for setting the second trigger condition. Then, in response to a selection operation performed on a fourth option among the at least one candidate option, the display module displays the configuration interface for the fourth option. Finally, the second trigger condition for the first scenario mode is set in the configuration interface of the fourth option.

[0141] The display method of at least one candidate option for setting the second trigger condition is the same as the display method of at least one candidate option for setting the first trigger condition. The at least one candidate option for setting the second trigger condition may be the same as or different from the at least one candidate option for setting the first trigger condition.

[0142] For example, taking the first scenario mode as the learning mode and the first trigger condition as the calendar timetable, the main screen of the electronic device displays the mode settings interface for the learning mode. The mode settings interface for the learning mode includes a mode activation control, condition settings (i.e., "Add Trigger Method"), task settings (i.e., "Study Plan"), associated functions, and allowed items. After the user clicks on "Add Trigger Method," at least one candidate option is displayed: scheduled, when the application starts, when near a location, and calendar timetable. After the user selects "Calendar Timetable," the configuration interface for "Calendar Timetable" is displayed. In the configuration interface of "Calendar Timetable," the user selects timetable 1 and timetable 2, setting them as the first trigger condition for the learning mode, and clicks on the settings controls (such as...) in the configuration interface of "Calendar Timetable." Figure 7 As shown in (a), the updated mode settings interface will be displayed.

[0143] In this case, the updated mode settings interface will display the first trigger condition that has been set, which is the associated calendar timetables: Timetable 1 and Timetable 2, such as... Figure 7 As shown in (b). Based on this, users can click "Add Trigger Method" again to configure a second trigger condition for the learning mode.

[0144] In other examples, when a user uses method two above to configure both conditional and task settings, firstly, in response to the setting operation performed on the conditional settings, the scenario mode module obtains the first information of the first scenario mode and saves it to the database. Secondly, in response to the setting operation performed on the task settings, the scenario mode module obtains the to-do tasks that should be completed in the first scenario mode and can save these to-do tasks to the database. Finally, based on the first information and the to-do tasks, the scenario mode module obtains the triggering conditions of the first scenario mode and the first prompt element displayed in the first scenario mode.

[0145] In some implementations, when setting task settings, firstly, in response to a setting operation performed on the task settings in the mode setting interface, the display module displays the task setting interface. Secondly, at least one pending task to be completed in the first scenario mode is set in the task setting interface. In this case, the scenario mode module obtains at least one pending task and saves the obtained at least one pending task to the database.

[0146] In some examples, when the display module displays the task settings interface, firstly, the main screen module within the display module retrieves (or pulls up) the interface data of the task settings interface from the scenario mode module. Secondly, the main screen module uses the interface data of the task settings interface to display the task settings interface on the main screen interface.

[0147] For example, taking the first scenario mode as the learning mode, the main screen of the electronic device displays the mode settings interface for the learning mode. The mode settings interface for the learning mode includes a mode activation control, condition settings (i.e., "Add Trigger Method"), task settings (i.e., "Learning Plan"), associated functions, and allowed items. Users can perform click operations on the "Learning Plan," such as... Figure 8 As shown in (a). After the user clicks on the "Study Plan", the task settings interface is displayed on the main screen, as shown. Figure 8 As shown in (b). Users can set up to-do tasks to be completed in learning mode by "Add Task" in the task settings interface.

[0148] Here, considering that if a user sets a small number of to-do tasks, and completes them quickly, the task setting interface needs to be triggered again to add more tasks. This repeated triggering of the task setting interface increases the data processing load on the electronic device. Conversely, if a user sets a large number of to-do tasks, and cannot complete them during the first scenario, the display of too many tasks will also increase the data processing load on the electronic device.

[0149] Therefore, to better assist users in setting up to-do tasks, setting prompts can be displayed in the task setting interface. This provides guidance during the task setting process, helping users to set an appropriate number of tasks. In some implementations, firstly, the display module shows a first prompt in the task configuration interface. Secondly, when the number of at least one to-do task exceeds a preset threshold, the display module shows a second prompt in the task configuration interface. This way, by providing prompts to the user, it helps them set an appropriate number of to-do tasks, reducing the probability of repeatedly triggering the task configuration interface and displaying too many to-do tasks on the interface.

[0150] The first prompt message indicates that adding more to-do tasks is allowed, thus notifying the user that they can add more to-do tasks. The second prompt message indicates that the maximum number of configured to-do tasks has been reached, thus notifying the user that the maximum number of to-do tasks has been reached.

[0151] The maximum number of tasks that can be set in the first scenario mode (i.e., the preset threshold) can be determined based on the duration of the first scenario mode. For example, when the duration of the first scenario mode is "4 hours", the preset threshold for the number of tasks is 2; while when the duration of the first scenario mode is "8 hours", the preset threshold for the number of tasks is 5.

[0152] For example, when the number of to-do tasks set by the user has not reached the maximum limit (i.e., the preset threshold), the first prompt message displayed in the task settings interface is "You can add learning tasks, which will be displayed on the home screen and lock screen after the mode is enabled." Figure 9 As shown in (a), as the number of to-do tasks set by the user gradually increases, when the number of to-do tasks set by the user reaches the limit, the task settings interface displays a second prompt message: "The learning task limit has been reached. Delete existing tasks and then add new ones." Figure 9 As shown in (b).

[0153] In other examples, when the user adopts method three above and only configures the task settings in the mode settings interface, firstly, in response to the setting operation performed on the task settings, the scenario mode module obtains the to-do task that should be completed in the first scenario mode. Secondly, based on the to-do task, the scenario mode module obtains the first prompt element to be displayed in the first scenario mode.

[0154] S403. In response to the fulfillment of the triggering condition, the scenario mode module activates the first scenario mode. In this way, the activation of the first scenario mode is automatically achieved without the need for the user to perform any additional operations, and the complexity of the triggering operation of the first scenario mode is also reduced.

[0155] S404. During the continuation of the first scenario mode, a first prompt element is displayed on the interface to indicate to the user that the user is currently in the first scenario mode and to enhance the user's perception of the first scenario mode.

[0156] The first notification element can be displayed on the home screen, lock screen, and Always-on Display (AOD) screen. Specifically, the first notification element can be displayed as one or more of the following: status bar icon, notification window notification, home screen component, lock screen live window, home screen live window, always-on display live window, lock screen live notification, home screen live notification, and always-on display live notification.

[0157] The notification window can be triggered by swiping down or swiping up on the desktop.

[0158] Here, live notifications can include instant live notifications and persistent live notifications. When the first notification element is displayed via an instant live notification, the display method of the first notification element includes one or more of the following: capsule notification on the lock screen, capsule notification on the home screen, capsule notification on the always-on display screen, card notification on the lock screen, card notification on the home screen, and card notification on the always-on display screen.

[0159] When the first notification element is displayed via a persistent live notification, the display method of the first notification element may include one or more of the following: capsule notification on the lock screen, capsule notification on the home screen, capsule notification on the always-on display screen, card notification on the lock screen, card notification on the home screen, and card notification on the always-on display screen.

[0160] For example, when the first notification element is displayed as a "card notification on the lock screen desktop," the display effect of the first notification element is as follows: Figure 10 As shown in (a). When the first notification element is displayed as a "notification from a notification window", the display effect of the first notification element is as follows: Figure 10 As shown in (b). When the first notification element is displayed as a "capsule notification on the lock screen desktop," the display effect of the first notification element is as follows: Figure 10 As shown in (c). When the first notification element is displayed in the "status bar indicator" mode, the display effect of the first notification element is as follows: Figure 10 As shown in (d).

[0161] In some examples, when the first prompt element is displayed on the lock screen (or home screen), firstly, the lock screen module (or home screen) retrieves the first prompt element from the profile module. Secondly, the lock screen module (or home screen) uses the first prompt element to populate the interface frame of the lock screen (or home screen) to display the first prompt element on the lock screen (or home screen).

[0162] In other examples, when the first prompt element is displayed on the lock screen (or home screen) as a live notification (or live window), firstly, the live module responds to the instruction from the lock screen module (or home screen module) and obtains the element data of the first prompt element from the profile module via an interface. Secondly, the live module uses the element data of the first prompt element to display it as a live notification (or live window) on the lock screen (or home screen).

[0163] In other examples, when the first prompt element is displayed as a status bar identifier, the status bar module first retrieves the element data of the first prompt element from the scenario mode module via an interface. Then, using the element data, the status bar module displays the first prompt element as a status bar identifier in the status bar.

[0164] In some implementations, when displaying the first prompt element, the display module first shows a persistent live notification on the interface to inform the user that they are currently in the first scenario mode. This achieves the purpose of prompting the user while minimizing the obstruction of the interface caused by the first prompt element. Secondly, in response to a trigger operation performed on the persistent live notification, a live window is displayed. This way, the user is only prompted by displaying a larger live window when they require it, thus minimizing the obstruction of the interface caused by the first prompt element during the continuation of the first scenario mode.

[0165] In this context, "persistent live notification" and "live window" refer to notification information that can be displayed on the interface for an extended period. A persistent live notification includes the first content of the first prompt element, and a live window includes the second content of the first prompt element. Here, the first content displayed in the persistent live notification and the second content displayed in the live window can be the same or different. Furthermore, the display positions of the live window and live notification vary across different interfaces.

[0166] In this context, both the first and second content items are information related to the first scenario mode that can be used to prompt the user. For example, when the first scenario mode is a learning mode, the first and second content items can be used to indicate that the user is currently in a learning mode, the tasks to be completed in the learning mode, the duration of the learning mode, the start time of the course, the location of the class, the course name, and the instructor's name. When the first scenario mode is a work mode, the first and second content items can be used to indicate that the user is currently in a work mode, the tasks to be completed in the work mode, the duration of the work mode, the start time of the work meeting, the meeting room location, the meeting topic, and the attendees.

[0167] The aforementioned trigger operation can refer to an operation performed by a user using a touch device on an electronic device, which can include single-point touch operations (e.g., tap, single click, long press, etc.) and multi-point touch operations, swipe operations, drag operations, etc., such as tapping a persistent live notification. Alternatively, a trigger operation can also refer to a voice control operation performed by a user using a sound acquisition device (e.g., a microphone) on a handheld electronic device. Furthermore, a trigger operation can also refer to an operation performed by a user using an additional input device (e.g., a game controller, mouse, keyboard, etc.).

[0168] In some implementations, during the process of displaying the first notification element via a capsule notification on the lock screen, a live window of the lock screen is displayed in response to a triggering operation performed on the capsule notification.

[0169] For example, taking the first scenario mode as the learning mode, during the continuous operation of the first scenario mode, a first prompt element is displayed through a persistent live notification. The persistent live notification is displayed in the form of a "capsule notification on the lock screen desktop." The persistent live notification is used to indicate that the current mode is learning mode, such as... Figure 11 As shown in (a). In this case, in response to the user's click on the "Capsule Notification on the Lock Screen," the "Live Window on the Lock Screen" (also known as the Lock Screen Card) is displayed. The "Live Window on the Lock Screen" can display information such as the duration of the learning mode, at least one to-do task, etc. Figure 11 As shown in (b).

[0170] Alternatively, the "Live Stream Window on the Lock Screen" can display only course information: course name, location, and time, without showing to-do tasks, such as... Figure 11 As shown in (c).

[0171] For another example, taking the first scenario mode as the learning mode, during the continuous operation of the first scenario mode, a first prompt element is displayed through a persistent live notification. The persistent live notification is displayed in the form of a "capsule notification on the home screen," and is used to indicate that the current mode is learning mode. Figure 11 As shown in (d). In this case, in response to the user's click action on the persistent live notification, the first notification element is displayed as a "component on the home screen desktop". This component on the home screen desktop can display course information such as the course name, location, and time. Figure 11 As shown in (e).

[0172] In some implementations, when the first prompt element is displayed through a live window, firstly, the live window includes at least one to-do task displayed in a first manner, wherein the at least one to-do task includes a first to-do task that the user has not completed. Thus, displaying the first to-do task in the first manner indicates that the first to-do task is incomplete. Secondly, in response to a trigger operation performed on the first to-do task, the display module switches the display mode of the first to-do task to a second mode. Thus, displaying the first to-do task in the second mode indicates that the first to-do task has been completed.

[0173] The display effect of the to-do task when displayed in the first mode differs from the display effect when displayed in the second mode. The display effect may include at least one of the following: display identifier (e.g., display icon), display color, display position, display size, and display transparency.

[0174] In some implementations, if at least one to-do task displayed in the live view window has been completed, a third notification message is displayed in the live view window to inform the user that all to-do tasks have been completed.

[0175] The third prompt message is used to indicate that the user has completed all the to-do tasks. The third prompt message may include: the duration of the first mode, motivational text, motivational icon, etc.

[0176] For example, taking the first scenario mode as the learning mode, the to-do tasks set in the first scenario mode include: memorizing one chapter of English vocabulary, memorizing one chapter of a professional course, reading one English professional article, writing a short essay of 100 words, and listening to two online political lectures. When the learning mode is activated, all to-do tasks are displayed with the first color and the first identifier. After completing the to-do task "reading one English professional article," the user performs a click operation on "reading one English professional article," such as... Figure 12 As shown in (a). In this case, "Read an English academic article" will be displayed in a second color and with a second identifier to indicate that the user has completed the to-do task of "Read an English academic article," as shown in (a). Figure 12 As shown in (b).

[0177] After the user completes all the to-do tasks, that is, after the user clicks on the last to-do task displayed in the first manner, "Listen to two online political classes" (e.g. Figure 12 As shown in (c), the third prompt message is displayed in the live view window: "You're awesome! You've completed 5 learning tasks today." Figure 12 As shown in (d).

[0178] In other implementations, during the display of the first notification element via the notification window, a trigger operation is performed in response to the notification window to display the mode settings interface for the first scenario mode. This achieves a "one-click" jump from the display interface to the mode settings interface. In other words, users no longer need to perform complex operations to enter the settings interface to trigger the display of the mode settings interface, thereby reducing the complexity of the operations required to enter the mode settings interface.

[0179] For example, taking the first scenario mode as the learning mode, when the user performs a click operation on the notification window (such as...) Figure 13 After (as shown in (a)), the mode settings interface will be displayed on the main screen, as follows. Figure 13 As shown in (b), this allows users to further configure the learning mode in the mode settings interface.

[0180] In other implementations, during the process of displaying the first prompt element via live notification, the display module shows the live notification on the interface to inform the user that they are currently in the first scenario mode. This achieves the purpose of prompting the user without excessively obstructing the interface.

[0181] In this context, "live notification" refers to a notification message briefly displayed on the interface. Live notifications include the third content of the first notification element. Here, the third content displayed in the live notification may be the same as or different from the first content displayed in the persistent live notification and the second content displayed in the live window.

[0182] Here, the third content refers to information related to the first scenario mode that can be used to prompt the user. For example, when the first scenario mode is a learning mode, the third content can be used to indicate that the user is currently in a learning mode, the tasks to be completed in this mode, the duration of the learning mode, the start time of the course, the location of the class, the course name, and the instructor's name. When the first scenario mode is a work mode, the third content can be used to indicate that the user is currently in a work mode, the tasks to be completed in this mode, the duration of the work mode, the start time of the work meeting, the meeting room location, the meeting topic, and the attendees.

[0183] The display area for live notifications includes the area where the camera lens of the electronic device is located. In other words, when live notifications are displayed, they are "blended" with the camera lens of the electronic device, thus reducing interface obstruction and presenting a more aesthetically pleasing display effect.

[0184] In some implementations, after displaying a live notification, if the duration of the live notification on the interface exceeds a preset time threshold, the display module cancels the display of the live notification and displays a notification icon and / or a status bar icon on the interface. In this way, the live notification can be "replaced" by a notification icon or status bar icon that has less obstruction of the interface, continuously reminding the user that they are currently in the first scenario mode, thereby further reducing the obstruction of the interface caused by the display of the first prompt element.

[0185] For example, the live notification is displayed on the interface for 5 to 10 seconds. After 10 seconds, the display module will no longer show the live notification on the interface, but will instead display a notification icon and / or status bar icon. In this case, the notification icon and / or status bar icon "replace" the live notification and are displayed on the interface for a longer period of time to prompt the user.

[0186] In some implementations, the notification icon is displayed around the area where the camera aperture is located. This not only continuously alerts the user and reduces interface obstruction, but also improves the aesthetics of the interface display.

[0187] In some implementations, when a notification icon is displayed on the interface, in response to a triggering operation on the notification icon, the display module displays a live window on the interface to provide prompts to the user using the live window, which can display more detailed prompt information.

[0188] The live feed window includes a second piece of content from the first notification element. This second piece of content displayed in the live feed window may be the same as or different from the third piece of content displayed in the live notification.

[0189] For example, taking the first scenario mode as the learning mode, during the continuous operation of the first scenario mode, a first prompt element is displayed through a live notification. The live notification is displayed as a "capsule notification on the lock screen desktop," indicating that "learning mode has been enabled." The display area of ​​the live notification includes the area where the camera aperture of the electronic device is located, such as... Figure 14 As shown in (a). In this case, in response to a live notification display duration exceeding a preset time threshold (e.g., 10 seconds), a persistent notification icon is displayed on the lock screen, where the notification icon is displayed around the area where the camera aperture is located, as shown in (a). Figure 14 As shown in (b).

[0190] In response to a user's click on the notification icon, a "Live Window on the Lock Screen" (also known as the lock screen card) is displayed. This "Live Window on the Lock Screen" can display information such as the duration of the learning mode and at least one pending task. Figure 14 As shown in (c).

[0191] In other implementations, users can also receive live notifications displayed on the lock screen (such as...). Figure 14 (as shown in (a)) Execute a click operation or other triggering operation to trigger the display of the "Live Window on the Lock Screen Desktop" (e.g. Figure 14 (as shown in (c)).

[0192] Taking the first scenario mode as the learning mode as an example, during the continuous operation of the first scenario mode, a first prompt element is displayed through a live notification. The live notification is displayed as a "capsule notification on the home screen," indicating that "learning mode has been activated." The display area of ​​the live notification includes the area where the camera aperture of the electronic device is located, such as... Figure 14 As shown in (d). In this case, in response to a live notification display duration exceeding a preset time threshold (e.g., 10 seconds), a persistent notification icon is displayed on the main screen, where the notification icon is displayed around the area where the camera aperture is located, as shown in (d). Figure 14 As shown in (e).

[0193] In response to a user's click on the notification icon, a "Live Stream Window" is overlaid on the main screen. This "Live Stream Window" can display information such as the duration of the learning mode and at least one pending task. Figure 14 As shown in (f).

[0194] In other implementations, users can also receive live notifications displayed on the home screen (such as...). Figure 14 (as shown in d) Perform click operations or other triggering operations to trigger the display of the "live window on the main screen desktop" (e.g., Figure 14 (as shown in f).

[0195] In some implementations, the live view window on the main screen desktop also includes task editing controls, such as... Figure 15 As shown. In response to a trigger operation performed on the task editing control, the main screen module in the display module displays the task settings interface, allowing the user to reset the to-do tasks within the task settings interface. Furthermore, users can use the additional task editing control in the live window to achieve a "one-click" jump from the display interface to the task settings interface. In other words, users no longer need to perform complex operations to enter the settings interface to trigger its display, thus reducing the complexity of the operations required to access the task settings interface.

[0196] In other implementations, the live window on the main screen desktop also includes a task close control, such as... Figure 15As shown. In response to the trigger operation executed by the task close control, the live window on the main desktop is closed, and the main screen module in the display module cancels the display of the live window on the main desktop in the interface. This achieves "one-click" closure of the live window on the main desktop.

[0197] In other implementations, during the display of the first prompt element through the live window, in response to a trigger operation performed on the live window, the display module displays the task settings interface of the first scenario mode. Thus, even when the user has not set any tasks, and even in a locked screen state, the user can use the live window to achieve a "one-click" jump from the display interface to the task settings interface. In other words, the user no longer needs to perform complex operations to enter the settings interface to trigger the display of the task settings interface, thereby reducing the complexity of the operations required to enter the task settings interface.

[0198] Here, the content displayed in the Live Stream window differs depending on whether the user has set any to-do tasks. Specifically, when the user has set any to-do tasks, the Live Stream window displays at least one to-do task, such as... Figure 16 As shown in (a). When the user has not set any tasks, the live window has at least two display modes: Mode 1, the live window can display a task addition control, such as... Figure 16 As shown in (b); in Method Two, the live stream window can display information related to the first scenario mode. For example, taking the first scenario mode as the learning mode, the live stream window can display course information such as course name, class location, and class time. Figure 16 As shown in (c).

[0199] In other examples, if the user sets the first prompt element to "dark mode" through the association function in the mode settings interface, then the first prompt element can be displayed in "dark" mode. For instance, taking the live window as the first prompt element, the live window can be displayed in "dark" mode, such as... Figure 16 As shown in (d).

[0200] In other examples, when the user has not set any pending tasks, and the Live Window is displayed in the manner described in Method 1 above, the user can trigger the display of the mode settings interface or task settings interface of the first scenario mode by activating the task addition control in the Live Window, such as... Figure 16 As shown in (e).

[0201] In other examples, when the user has set up to-do tasks, the live stream window can also be displayed in the form described in Method 2 above. That is, the live stream window only displays information related to the first scenario mode (for example, taking the first scenario mode as the learning mode, the live stream window only displays course information: course name, class location, and class time, etc.). Figure 17 (As shown in (a)). In this case, the user can click (or otherwise trigger the action) on the live window to switch the displayed content, changing the information related to the first scenario mode to the user-set to-do tasks, such as... Figure 17 As shown in (b).

[0202] Users can switch the content displayed in the live stream window by performing a trigger operation on the live stream window. Alternatively, users can set an additional switching control in the live stream window, and then perform a trigger operation on the switching control to switch the content displayed in the live stream window. The settings can be adjusted according to the actual situation, and there are no restrictions here.

[0203] Here, after the first scenario mode is activated, during the process of reminding the user through live notifications (including instant and persistent live notifications), the mode icon in the status bar, and the live window displayed in the lock screen, various notification methods can switch between each other. For example, after the instant live notification disappears, the first scenario mode's mode icon is displayed in the status bar, along with the persistent live notification. Alternatively, instant live notifications, the mode icon in the status bar, and the persistent live notification can be displayed simultaneously. Or, instant live notifications and the mode icon in the status bar can be displayed simultaneously, and after the instant live notification disappears, the persistent live notification is displayed (the mode icon in the status bar remains displayed).

[0204] In some implementations, during the display of the first prompt element via a live window and / or live notification, the scenario mode module exits the first scenario mode in response to a triggering operation performed on the live window or live notification. In this case, the display module stops displaying the first prompt element on the interface.

[0205] In some implementations, in response to exiting the first scenario mode, the display module displays a second prompt element on the interface to indicate to the user that the first scenario mode has been exited. This can also enhance the user's awareness of the first scenario mode and improve the user experience.

[0206] The second notification element can be displayed on the home screen, lock screen, and Always-on Display (AOD) screen. Specifically, the second notification element can be displayed as one or more of the following: notification window notification, lock screen notification, home screen notification, and always-on display notification.

[0207] Here, live notifications include instant live notifications. When a second notification element is displayed via an instant live notification, the second notification element can be displayed in one or more of the following ways: capsule notification on the lock screen, capsule notification on the home screen, capsule notification on the always-on display screen, card notification on the lock screen, card notification on the home screen, and card notification on the always-on display screen.

[0208] In some examples, when the second prompt element is displayed on the lock screen (or home screen), firstly, the lock screen module (or home screen) retrieves the second prompt element from the profile module. Secondly, the lock screen module (or home screen) uses the second prompt element to populate the interface frame of the lock screen (or home screen) to display the second prompt element on the lock screen (or home screen).

[0209] In other examples, when the second notification element is displayed on the lock screen (or home screen) as a live notification, firstly, the live module responds to the instruction from the lock screen module (or home screen module) and retrieves the element data of the second notification element from the profile module via an interface. Secondly, the live module uses the element data of the second notification element to display it as a live notification (e.g., an instant live notification) on the lock screen (or home screen).

[0210] For example, when the second notification element is displayed as a "card notification on the lock screen desktop," the display effect of the second notification element is as follows: Figure 18 As shown in (a). During the process of displaying the second notification element in the "Notification Window Notification" display mode, the display effect of the second notification element is as follows: Figure 18 As shown in (b). During the process of displaying the second notification element in the "Capsule Notification on Lock Screen Desktop" display mode, the display effect of the second notification element is as follows: Figure 18 As shown in (c).

[0211] In some implementations, after displaying the live notification, firstly, in response to an operation on the live notification, options for the scenario mode are displayed. Secondly, in response to an operation on the first option of the scenario mode, the scenario mode is turned off. And / or, in response to an operation on the second option of the scenario mode, the scenario mode settings interface is opened. Thus, even if the scenario mode module has activated the first scenario mode based on user-set trigger conditions, the user can also turn off the first scenario mode according to their own environment.

[0212] In some examples, the first option can be a mode-closing control. When exiting the first scenario mode via the first option, a trigger operation is executed in response to the mode-closing control, thus exiting the first scenario mode. In this way, even if the scenario mode module has enabled the first scenario mode based on the trigger conditions set by the user, the user can also disable the first scenario mode according to their own environment.

[0213] In other examples, the second option can be a pattern editing control. When the pattern settings interface of the first scenario mode is opened via the second option, a trigger operation is performed on the pattern editing control to open the pattern settings interface of the first scenario mode. Thus, when the scenario mode module activates the first scenario mode based on the trigger conditions set by the user, the user can also adjust the first scenario mode according to their own environment.

[0214] For example, taking the first scenario mode as the learning mode, when the first scenario mode is enabled, live notifications are displayed on the main screen in the form of "capsule notifications." At this time, the live notifications are used to indicate that "learning mode has been enabled," such as... Figure 19 As shown in (a).

[0215] In response to a user's click on the live notification, a mode-closing control for the first scenario mode is displayed. After the user clicks the mode-closing control, the first scenario mode is closed, and a second notification element is displayed. This second notification element is a live notification displayed as a "capsule notification" on the main screen, indicating that "Learning Mode is off," as shown below. Figure 19 As shown in (b).

[0216] Alternatively, in response to a user's click on the live notification, the mode editing control for the first scenario mode is displayed. After the user clicks on the mode editing control, the mode settings interface for the first scenario mode opens, such as... Figure 19 As shown in (c).

[0217] In other implementations, in response to the duration of the first scenario mode reaching a time threshold, the scenario mode module exits the first scenario mode and records in the database that the first scenario mode is in a closed state. This helps users automatically exit the first scenario mode, reducing the probability that users will forget to close it.

[0218] The time threshold can be determined based on the triggering conditions of the first scenario mode. For example, taking the first scenario mode as the learning mode, the activation condition of the learning mode is "to activate the learning mode according to the class time in the calendar timetable". Then, the learning mode will automatically exit after the class time has passed.

[0219] In other implementations, users can also exit the first scenario mode by entering the mode settings interface and triggering the mode enable control (or a separately set mode disable control) in the mode settings interface, and record in the database that the first scenario mode is in a disabled state.

[0220] In some implementations, when the first prompt element is displayed through the live window, persistent live notification, or notification icon, the display module cancels the display of the live window, persistent live notification, or notification icon after exiting the first scenario mode.

[0221] In some examples, when the first notification element is displayed on the lock screen (or home screen) via a persistent live notification (or live window), after the profile module exits the first profile mode, the live module responds to the cancellation command sent by the profile module and cancels the persistent live notification (or live window) displayed on the lock screen (or home screen).

[0222] In other examples, when the first prompt element is displayed in the status bar, the status bar module cancels the display of the first prompt element in the status bar after the profile module exits the first profile mode.

[0223] The following, combined with Figure 20 This document describes the interaction relationships between the database, the scenario mode module, the live feed module, and the status bar module. The scenario mode module can write the status of the first scenario mode to the database. The scenario mode module can also send live feed notifications (including instant and / or persistent live feed notifications) to the live feed module. The status bar module can monitor the status of the first scenario mode recorded in the database and, when the first scenario mode is active, query the scenario mode module for the first prompt element (e.g., the mode icon).

[0224] The following, combined with Figure 21 This document explains the connection process between the scenario mode module, calendar module, calendar sharing module, perception module, and lock screen module during the process of users associating course schedules with learning mode.

[0225] The scenario mode module includes at least a learning mode module, a timetable adaptation module, a scenario mode UI module, a full-scene perception / execution adaptation module, and a lock screen course display module. When the perception module triggers a mode switch, the learning mode module triggers the timetable adaptation module to refresh the timetable time frame data. The timetable adaptation module generates the timetable time frame data and sends it to the full-scene perception / execution adaptation module. Based on the timetable time frame data, the full-scene perception / execution adaptation module detects whether there is a scenario mode switching requirement and, if so, switches the scenario mode of the electronic device accordingly.

[0226] The timetable adaptation module can also perform tasks such as querying the timetable list from the timetable broadcast module, querying course information in the timetable, and querying the list of course instances for a specified time range.

[0227] The scenario mode UI module provides a configuration interface for users to configure the course schedule associated with the learning mode. The lock screen course display module displays course information from the course schedule associated with the learning mode when the user locks the screen.

[0228] The calendar sharing module includes a timetable broadcasting module. When the timetable data changes, the calendar module broadcasts the timetable configured / imported by the user in the calendar module to the perception module, so that the learning mode trigger event (that is, the timetable perception event) can be defined through the public event perception module in the perception module.

[0229] The perception module also includes a time-fence service, which is responsible for monitoring the class times in the timetable and notifying the scenario mode module to switch the learning mode when the class time arrives.

[0230] When the screen is locked, the lock screen module retrieves course information from the lock screen course display module of the scenario mode module and displays the course information on the lock screen interface.

[0231] The following, combined with Figure 22This document describes the process of the lock screen module displaying a live view window in an "immersive" mode. The scenario mode module provides a task scheduling module, a scenario editing interface module, a scenario linkage module, and a database. The scenario mode module provides a scenario setting interface through the scenario editing interface module and receives data such as trigger conditions and pending tasks entered by the user through setting operations in the scenario setting interface, saving this information to the database. The task scheduling module generates the first prompt element based on the trigger conditions and pending tasks saved in the database. When the scenario mode module detects that the trigger conditions are met and activates the first scenario mode, the scenario mode module sends a live notification to the lock screen module through the advanced notification service (ANS) module, enabling the lock screen module to publish live notifications. Upon receiving the live notification, the lock screen module displays the live notification on the lock screen interface through the live notification module. During the live notification display process, when the user triggers the display of the live window in "immersive mode" through the live notification, the lock screen immersive live module in the lock screen module pulls up the data of the live window from the task schedule module in the scenario mode module and displays the live window in "immersive mode" on the lock screen interface.

[0232] If the user modifies information such as tasks to be done during the live view window display, the task scheduling module will display the modified data and update the data in the database upon receiving the modification information.

[0233] The following, combined with Figure 23 This document describes the interaction process between multiple modules during the activation and deactivation of the first scenario mode. The first prompt element includes at least three display phases: the mode activation phase, the lock screen display phase, and the mode deactivation phase.

[0234] In the initial phase of the mode, the scenario mode module activates the first scenario mode when the triggering conditions are met, and simultaneously sends an instant live notification and / or a persistent live notification to the live module. The live module displays the instant live notification and / or the persistent live notification. After the display duration of the instant live notification exceeds a preset time threshold, the live module displays a notification icon and cancels the display of the instant live notification. In some embodiments, the persistent live notification may be displayed directly without displaying the instant live notification; or, in other embodiments, the mode icon may be displayed directly in the status bar after the instant live notification is displayed, without displaying the persistent live notification; or, in other embodiments, the persistent live notification and the mode icon in the status bar may be displayed after the instant live notification is displayed; or, in other embodiments, the persistent live notification and the mode icon in the status bar may be displayed directly without displaying the instant live notification.

[0235] For example, when a user is using an electronic device, since the user is constantly focused on the device, to reduce the obstruction of the interface by the primary notification element, the display of the primary notification element used to prompt the user can be reduced. In this case, after displaying the live notification, the mode icon can be displayed directly in the status bar instead of the persistent live notification. This achieves the purpose of prompting the user while minimizing interface obstruction.

[0236] For another example, when a user is not using the electronic device, they are unlikely to see the short-duration live notifications because they are not paying attention to the device. In this case, instead of displaying live notifications, persistent live notifications and / or mode icons can be shown directly to reduce the display of unnecessary prompts and the consumption of computing resources on the electronic device.

[0237] The scenario mode module records the on / off status, mode icon, and mode name of the first scenario mode in the database. After the status bar module detects a change in the status of the first scenario mode in the database, the status bar module can either retrieve the mode icon of the first scenario mode from the scenario mode module (taking the first prompt element as the mode icon as an example) or the scenario mode module can automatically send the mode icon to the status bar module, and the status bar module will display the mode icon of the first scenario mode in the status bar.

[0238] During the lock screen display phase, the system enters lock screen mode when the user triggers the lock screen (or the system automatically triggers the lock screen). The lock screen module, through the live feed module, displays live notifications (including instant and / or persistent live feeds) while the screen is locked. When a live feed notification is triggered by the user, the live feed module retrieves data from the live feed window from the scenario module, or the scenario module sends a to-do task to the live feed module, displaying the live feed window while the screen is locked, and showing the to-do task retrieved from the database within the live feed window. When the user completes the to-do task, the display method of the to-do task in the live feed window is adjusted.

[0239] During the mode shutdown phase, the user triggers an instant live notification to close the first scenario mode via the scenario mode module. The scenario mode module sends an instant live notification and a command to cancel persistent notifications to the live module. The live module displays the instant live notification and cancels persistent notifications. The scenario mode module records the shutdown status of the first scenario mode in the database. After the status bar module detects a change in the status of the first scenario mode in the database, it removes the mode icon from the status bar.

[0240] In some solutions, multiple embodiments of this application can be combined, and the combined solution can be implemented. Optionally, some operations in the processes of each method embodiment may be combined, and / or the order of some operations may be changed. Furthermore, the execution order between the steps of each process is merely exemplary and does not constitute a limitation on the execution order between steps; other execution orders are also possible. It is not intended to indicate that the execution order is the only possible order in which these operations can be performed. Those skilled in the art will conceive of various ways to reorder the operations described in the embodiments of this application. In addition, it should be noted that the process details involved in one embodiment of this application are also applicable to other embodiments in a similar manner, or different embodiments may be combined.

[0241] Furthermore, some steps in the method embodiments can be equivalently replaced with other possible steps. Alternatively, some steps in the method embodiments may be optional and can be deleted in certain use cases. Or, other possible steps may be added to the method embodiments. Moreover, the various method embodiments can be implemented individually or in combination.

[0242] It is understood that, in order to achieve the above functions, the aforementioned electronic device includes hardware and / or software modules corresponding to perform each function. Based on the algorithmic steps of the various examples described in conjunction with the embodiments disclosed herein, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application in conjunction with the embodiments, but such implementation should not be considered beyond the scope of this application.

[0243] This application embodiment can divide the electronic device into functional modules according to the above method example. For example, each function can be divided into its own functional module, or two or more functions can be integrated into one processing module. The integrated module can be implemented in hardware. It should be noted that the module division in this embodiment is illustrative and only represents one logical functional division. In actual implementation, there may be other division methods.

[0244] This application also provides an electronic device, such as... Figure 24As shown, the electronic device may include one or more processors 2401, memory 2402, and communication interface 2403. The memory 2402 and communication interface 2403 are coupled to the processor 2401. For example, the memory 2402, communication interface 2403, and processor 2401 may be coupled together via a bus 2404. The communication interface 2403 is used for data transmission with other devices. The memory 2402 stores computer program code. The computer program code includes computer instructions, which, when executed by the processor 2401, cause the electronic device to perform the information processing method described in this application.

[0245] The processor 2401 may be a processor or controller, such as a central processing unit (CPU), a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It can implement or execute the various exemplary logic blocks, modules, and circuits described in conjunction with this disclosure. The processor may also be a combination that implements computational functions, such as a combination of one or more microprocessors, a combination of a DSP and a microprocessor, etc.

[0246] The bus 2404 can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. The bus 2404 can be divided into address bus, data bus, control bus, etc. For ease of representation, Figure 24 The bus is represented by a single thick line, but this does not mean that there is only one bus or one type of bus.

[0247] This application also provides a computer-readable storage medium storing computer program code. When the processor executes the computer program code, the electronic device performs the relevant method steps in the above method embodiments. This application also provides a chip including a memory and one or more processors; the memory is coupled to the processors; wherein the memory stores computer program code, which includes computer instructions. When the computer instructions are executed by the processor, the chip performs the relevant method steps in the above method embodiments. The electronic device, computer storage medium, and chip provided in this application are all used to execute the corresponding methods provided above. Therefore, the beneficial effects they achieve can be referred to the beneficial effects in the corresponding methods provided above, and will not be repeated here. Through the description of the above embodiments, those skilled in the art can clearly understand that, for the sake of convenience and brevity, only the division of the above functional modules is used as an example. In practical applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above.

[0248] In the several embodiments provided in this application, it should be understood that the disclosed apparatus and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of modules or units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another device, or some features may be ignored or not executed. Furthermore, the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between devices or units may be electrical, mechanical, or other forms.

[0249] The units described as separate components may or may not be physically separate. A component shown as a unit can be one or more physical units, meaning it can be located in one place or distributed across multiple different locations. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs. Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated units described above can be implemented in hardware or as software functional units.

[0250] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a readable storage medium. Based on this understanding, the technical solution of the embodiments of this application, in essence, or the part that contributes, or all or part of the technical solution, can be embodied in the form of a software product. This software product is stored in a storage medium and includes several instructions to cause a device (which may be a microcontroller, chip, etc.) or processor to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0251] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions within the technical scope disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. An information processing method, characterized in that, The method is applied to an electronic device, the electronic device including multiple scenario modes, the multiple scenario modes including a first scenario mode; the method includes: Displays the mode settings interface for the first scenario mode; In response to the setting operation performed in the mode setting interface, the triggering condition and the first prompt element of the first scenario mode are obtained; In response to the fulfillment of the triggering condition, the first scenario mode is activated; During the continuation of the first scenario mode, the first prompt element is displayed, wherein the first prompt element is used to indicate that the electronic device is in the first scenario mode.

2. The method according to claim 1, characterized in that, The mode setting interface includes condition setting items; the step of obtaining the trigger condition and first prompt element of the first scenario mode in response to the setting operation performed in the mode setting interface includes: In response to a setting operation performed on the condition setting item, first information of the first scenario mode is obtained; Based on the first information, obtain the triggering conditions and the first prompt element for the first scenario mode.

3. The method according to claim 2, characterized in that, The first information is obtained from the first application or from the first file.

4. The method according to any one of claims 2-3, characterized in that, The mode setting interface also includes task setting items; the method further includes: In response to a setting operation performed on the task setting item, retrieve the pending tasks in the first scenario mode; The step of obtaining the triggering conditions and the first prompt element of the first scenario mode based on the first information includes: Based on the first information and the task to be done, obtain the triggering conditions and the first prompt element of the first scenario mode.

5. The method according to claim 4, characterized in that, The response is a setting operation performed on the task settings item, and retrieves the pending tasks in the first scenario mode, including: In response to a setting operation performed on the task setting item, the task setting interface is displayed; At least one to-do task is set in the first scenario mode in the task settings interface.

6. The method according to any one of claims 1-5, characterized in that, The display of the first prompt element includes: Display a persistent live notification; the persistent live notification includes the first content of the first prompt element; In response to a triggered operation on the persistent live notification, a live window is displayed; the live window includes a second content of a first notification element, the first content and the second content being different.

7. The method according to any one of claims 1-6, characterized in that, In the process of displaying the first prompt element through the live window, the method further includes: The live window includes at least one to-do task displayed in a first manner; the at least one to-do task includes a first to-do task. In response to a trigger operation on the first task, the display mode of the first task is switched to a second mode; the second mode is used to indicate that the task has been completed.

8. The method according to any one of claims 1-6, characterized in that, During the process of displaying the first notification element through a notification window, the method further includes: In response to a notification triggered by the notification window, the mode settings interface of the first scenario mode is displayed.

9. The method according to any one of claims 1-5, characterized in that, The display of the first prompt element includes: Display a live notification; the live notification includes the third content of the first prompt element; the display area of ​​the live notification includes the area where the camera aperture of the electronic device is located.

10. The method according to claim 9, characterized in that, After displaying the live notification, the method further includes: When the display duration of the real-time notification exceeds a preset time threshold, a notification icon is displayed, and / or a status bar icon is displayed.

11. The method according to claim 9, characterized in that, After displaying the live notification, the method further includes: In response to actions taken in response to live notifications, the options for the first scenario mode are displayed; In response to an operation on the first option of the first scenario mode, exit the first scenario mode, the options of the first scenario mode including the first option; and / or, In response to an operation on the second option of the first scenario mode, the mode settings interface of the first scenario mode is opened, and the options of the first scenario mode include the second option.

12. The method according to claim 10, characterized in that, The notification icon is displayed around the area where the camera aperture is located.

13. The method according to claim 9, characterized in that, After displaying the notification icon, the method further includes: In response to a triggering action on the notification icon, a live window is displayed; the live window includes a second content of the first notification element, the second content being different from the third content.

14. The method according to any one of claims 1-5, characterized in that, In the process of displaying the first prompt element through the live window, the method further includes: In response to the triggered operation performed on the live window, the task settings interface of the first scenario mode is displayed.

15. The method according to any one of claims 1-12, characterized in that, In the process of displaying the first prompt element through a live window and / or live notification, the method further includes: In response to a triggering operation on the live window or live notification, exit the first scenario mode and stop displaying the first prompt element.

16. The method according to claim 1, characterized in that, The method further includes, during the process of displaying the first notification element via capsule notifications on the lock screen: In response to the triggering operation of the capsule notification, a live window of the lock screen is displayed.

17. The method according to any one of claims 1-16, characterized in that, The method further includes: In response to exiting the first scenario mode, a second prompt element is displayed; the second prompt element is used to prompt the electronic device to exit the first scenario mode.

18. The method according to any one of claims 1-17, characterized in that, The first prompt element is displayed on one or more of the main screen, lock screen, and always-on screen; and / or, The first prompt element is displayed in one or more of the following ways: status bar icon, notification window notification, main screen desktop component, lock screen desktop live window, main screen desktop live window, off-screen desktop live window, lock screen desktop live notification, main screen desktop live notification, and off-screen desktop live notification. The live notifications include instant live notifications and persistent live notifications; the instant live notifications include one or more of the following: capsule notifications on the lock screen, capsule notifications on the home screen, capsule notifications on the always-on screen, card notifications on the lock screen, card notifications on the home screen, and card notifications on the always-on screen; the persistent live notifications include one or more of the following: capsule notifications on the lock screen, capsule notifications on the home screen, capsule notifications on the always-on screen, card notifications on the lock screen, card notifications on the home screen, and card notifications on the always-on screen.

19. An electronic device, characterized in that, The device includes a memory and one or more processors; the memory is coupled to the processors; the memory stores computer program code, the computer program code including computer instructions, which, when executed by the processor, cause the electronic device to perform the information processing method as described in any one of claims 1-18.

20. A computer-readable storage medium, characterized in that, Includes computer instructions that, when executed on an electronic device, cause the electronic device to perform the information processing method as described in any one of claims 1-18.

21. A computer program product, characterized in that, When the computer program product is run on an electronic device, the electronic device performs the information processing method as described in any one of claims 1-18.

Images