A method of creating a scenario mode and a related apparatus

Abstract

The application discloses a method for creating a scene mode and a related device. The application relates to the technical field of terminals. In the method, an electronic device can determine configuration information of a scene mode according to historical data collected. In this way, different scene modes corresponding to different scenes can be set, and the user does not need to manually set the configuration information in the creation of each scene mode. Moreover, the configuration information can be determined according to the habit of the user in using the electronic device, and the created scene mode is more suitable for the user, and the user experience is good.

Description

Technical Field

[0001] This application relates to the field of terminal technology, and in particular to a method and related apparatus for creating scenario modes. Background Technology

[0002] Users can use electronic devices in various scenarios. These devices often have numerous applications installed, and users are frequently interrupted by notifications or calls in different situations. To improve user focus, electronic devices can create scenario modes. The configuration information for these scenarios includes allowed contacts for calls and allowed applications for notifications. How to make these created scenario modes more closely match user habits is a problem that continues to be solved in this field. Summary of the Invention

[0003] This application provides a method and related apparatus for creating scenario modes, allowing electronic devices to determine scenario mode configuration information based on historical data. This results in scenario modes that are more tailored to the user, leading to a better user experience.

[0004] In a first aspect, this application provides a method for creating a scenario mode, the method being applied to an electronic device, the method comprising: acquiring first historical data related to a first scenario, the first historical data including operating data of the electronic device in the first scenario; determining at least one configuration information of a first scenario mode of the electronic device, the at least one configuration information of the first scenario mode including first configuration information indicating a first function of the electronic device in the first scenario mode, the first configuration information being determined based on the first historical data; and displaying the first configuration information.

[0005] Firstly, different scenario modes can be set for different scenarios without requiring users to manually set configuration information when creating each scenario mode, reducing user steps and avoiding a complicated experience during scenario mode creation. Furthermore, the configuration information can be determined based on the user's electronic device usage habits, resulting in scenario modes that are more tailored to the user and provide a better user experience.

[0006] In conjunction with the first aspect, in some embodiments, before displaying the first configuration information, the method further includes: receiving and responding to an operation to create the first scenario mode. In some implementations, the electronic device may receive a user operation that triggers the creation of the first scenario mode. The user operation may include one or more of the following: touch operation, click operation, gesture operation, voice operation, and eye-tracking operation. For example, the electronic device responds to a click operation acting on the add mode control 221 to display... Figure 2C The user interface 230 shown.

[0007] In conjunction with the first aspect, in some embodiments, the at least one configuration information further includes second configuration information, and the method further includes: displaying the second configuration information, the second configuration information indicating a second function of the electronic device in the first scenario mode, the second configuration information being determined based on the first historical data.

[0008] In conjunction with the first aspect, in some embodiments, the method further includes: activating the first scenario mode, wherein the electronic device sets corresponding functions based on at least one first configuration information of the first scenario mode.

[0009] In conjunction with the first aspect, in some embodiments, the first configuration information is determined based on first preset configuration information and the first historical data, and the first preset configuration information indicates a preset first function of the electronic device in the first scenario mode.

[0010] Thus, the configuration information for the first scenario mode needs to take into account both the user's usage habits and the developer's pre-defined ideas for the first scenario mode.

[0011] In conjunction with the first aspect, in some embodiments, obtaining the first historical data related to the first scenario specifically includes: determining the application related to the first scenario based on the application type; and obtaining the first historical data related to the first scenario based on the running data of the application related to the first scenario. For details, please refer to... Figure 1A The method flow is shown.

[0012] In conjunction with the first aspect, in some embodiments, the running data of the application related to the first scenario includes the first application. The specific steps of obtaining the first historical data related to the first scenario based on the running data of the application related to the first scenario include: obtaining a first time period in which the first application runs; and obtaining one or more of the following within the first time period: incoming call information, notification information, and location information.

[0013] In conjunction with the first aspect, in some embodiments, the first configuration information is used to indicate an application that allows the first scenario mode to output notifications, and the determination of at least one configuration information for the first scenario mode of the electronic device includes: determining the first configuration information based on the notification message obtained within the first time period, the first configuration information including a second application.

[0014] In conjunction with the first aspect, in some embodiments, the first notification message includes: the number of times a notification from the second application has been opened exceeds a first threshold.

[0015] In this way, electronic devices are more likely to open notifications from the second application within the first time period. If notifications from the second application are allowed in the first scenario mode, the user experience will be improved.

[0016] In conjunction with the first aspect, in some embodiments, the first configuration information is used to indicate the contacts that the first scenario mode allows to receive calls, and determining at least one configuration information of the first scenario mode of the electronic device includes: determining the first configuration information based on the incoming call information obtained within the first time period, the configuration information including a first contact.

[0017] In conjunction with the first aspect, in some embodiments, the first incoming call information includes: the number of calls from the first contact person exceeds a second threshold, and / or, the duration of the calls from the first contact person exceeds a third threshold.

[0018] In this way, electronic devices are more likely to answer calls from the first contact person in the first time period. If calls from the first contact person are allowed in the first scenario mode, the user experience will be improved.

[0019] In conjunction with the first aspect, in some embodiments, the first configuration information is used to indicate that the first scenario mode is activated when a first condition is met, and the at least one configuration information for determining the first scenario mode of the electronic device includes: determining the first configuration information based on the first time period and / or the first location information.

[0020] In conjunction with the first aspect, in some embodiments, the first condition includes: being within the first time period and / or within the first location range, the first location information including: the duration of being within the first location range exceeds a fourth threshold.

[0021] In this way, electronic devices are more likely to be in the first scenario when they are in the first time period and / or in the first location. If the first scenario mode is automatically activated when they are in the first time period and / or in the first location, the user experience will be improved.

[0022] In conjunction with the first aspect, in some embodiments, the method further includes: updating the first configuration information based on the operating data of the electronic device in the first scenario mode, and / or updating the first configuration information according to user modifications to the first configuration information.

[0023] This allows the configuration information for the first scenario mode to be updated.

[0024] In conjunction with the first aspect, in some embodiments, after displaying the first configuration information, the method further includes: receiving and responding to an operation to create a second scenario mode, the electronic device displaying the first configuration information, the second scenario mode being associated with the first scenario mode.

[0025] In conjunction with the first aspect, in some embodiments, after displaying the first configuration information, the method further includes: deleting the created first scenario mode; receiving an operation to create the third scenario mode, the third scenario mode being related to the first scenario mode; determining at least one configuration information of the third scenario mode, the at least one configuration information of the third scenario mode being determined based on the operating data of the electronic device in the first scenario mode, and / or the configuration information of the first scenario mode.

[0026] In this way, when an electronic device creates a custom scenario mode, the scenario mode with the highest similarity to the custom scenario mode can be identified, and the configuration information of the custom scenario mode is the configuration information of the scenario mode with the highest similarity.

[0027] In conjunction with the first aspect, in some embodiments, after displaying the first configuration information, the method further includes: acquiring second historical data related to the second scenario, the second historical data including the operating data of the electronic device in the second scenario; determining at least one configuration information corresponding to a fourth scenario mode of the electronic device, the at least one configuration information of the fourth scenario mode including third configuration information, the third configuration information indicating the first function of the electronic device in the fourth scenario mode, the third configuration information being determined based on the second historical data; and displaying the third configuration information, wherein the second scenario mode is different from the first scenario mode, and the first configuration information is different from the third configuration information.

[0028] In this way, the electronic device obtains different configuration information for different scenario modes.

[0029] In a second aspect, this application provides an electronic device including a memory, a processor, and computer instructions stored in the memory, wherein the processor executes the computer program to implement the method described in the first aspect or any embodiment of the first aspect.

[0030] Thirdly, this application provides a chip system including a processing circuit and an interface circuit. The interface circuit is used to receive code instructions and transmit them to the processing circuit. The processing circuit is used to allow the code instructions to execute the method described in the first aspect or any embodiment of the first aspect.

[0031] Fourthly, embodiments of this application provide a computer-readable storage medium storing a computer program that, when run on a processor, implements the method described in the first aspect or any of the embodiments of the first aspect.

[0032] Fifthly, embodiments of this application provide a computer program product, including a computer program that, when run on a processor, implements the method described in the first aspect or any of the embodiments of the first aspect.

[0033] The beneficial effects of aspects two through five can be referenced from the beneficial effects of aspect one above. Attached Figure Description

[0034] Figure 1A A flowchart illustrating a method for generating configuration information for a scenario mode, provided in an embodiment of this application;

[0035] Figure 1B This is a schematic flowchart of a method for creating a scenario mode provided in an embodiment of this application;

[0036] Figures 2A-2C The user interface provided in this application embodiment for triggering the creation of a first scenario mode under scenario 1;

[0037] Figures 2D-2E The user interface provided in this application embodiment for triggering the creation of a first scenario mode in case 2;

[0038] Figure 2F The user interface provided in this application embodiment displays configuration information for a first scenario mode in case 1;

[0039] Figure 2G The user interface provided in this application embodiment displays configuration information for a first scenario mode in scenario 2;

[0040] Figures 3A-3D Several user interfaces for displaying configuration information of scene modes are provided in the embodiments of this application;

[0041] Figure 3E The user interface of the application for viewing and modifying permission notifications provided in the embodiments of this application;

[0042] Figure 3F The user interface provided for viewing and modifying allowed callers in the embodiments of this application;

[0043] Figure 4A This application provides a user interface for adding activation conditions to an electronic device.

[0044] Figure 4B To add a user interface for enabling conditions to another electronic device provided in the embodiments of this application;

[0045] Figure 4C To add a user interface for enabling conditions to another electronic device provided in the embodiments of this application;

[0046] Figures 4D-4F The user interface for modifying and deleting activation conditions for several electronic devices provided in the embodiments of this application;

[0047] Figure 4GThe user interface for modifying the associated system functions of the electronic device provided in the embodiments of this application;

[0048] Figure 5 This application provides a user interface for deleting scene modes on an electronic device.

[0049] Figure 6 An exemplary illustration shows a flowchart of a method for creating a scenario pattern according to an embodiment of this application;

[0050] Figure 7 A schematic diagram of the internal modules of an electronic device provided in an embodiment of this application;

[0051] Figure 8 A schematic diagram of the hardware structure of an electronic device 100 provided in an embodiment of this application;

[0052] Figure 9 This is a schematic diagram of the software structure of an electronic device 100 provided in an embodiment of this application. Detailed Implementation

[0053] The technical solutions of the embodiments of this application are described below with reference to the accompanying drawings. In the description of the embodiments of this application, the terminology used is for the purpose of describing specific embodiments only and is not intended to limit the application. As used in the specification and appended claims of this application, the singular expressions “a,” “the,” “the,” “the,” and “this” are intended to also include expressions such as “one or more,” unless the context clearly indicates otherwise. It should also be understood that in the following embodiments of this application, “at least one” and “one or more” refer to one or more (including two). “At least one of the following” or similar expressions refer to any combination of these items, including any combination of a single item or a plurality of items. For example, at least one of a, b, or c can represent: a, b, c, a and b, a and c, b and c, or a, b, and c, where a, b, and c can be single or multiple. The term "and / or" describes 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, or B alone, where A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects have an "or" relationship.

[0054] References to "one embodiment" or "some embodiments" in this specification mean that one or more embodiments of this application include a specific feature, structure, or characteristic described in connection with that embodiment. Therefore, the phrases "in one embodiment," "in some embodiments," "in other embodiments," "in still other embodiments," etc., appearing in different parts of this specification do not necessarily refer to the same embodiment, but rather mean "one or more, but not all, embodiments," unless otherwise specifically emphasized. The terms "comprising," "including," "having," and variations thereof mean "including but not limited to," unless otherwise specifically emphasized. The term "connection" includes direct connections and indirect connections, unless otherwise stated. "First" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated.

[0055] In the embodiments of this application, the words "exemplarily" or "for example" are used to indicate examples, illustrations, or explanations. Any embodiment or design described as "exemplarily" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or design solutions. Specifically, the use of the words "exemplarily" or "for example" is intended to present the relevant concepts in a specific manner.

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

[0057] First, some terms and concepts are involved in the embodiments of this application.

[0058] A scenario refers to the environment in which an electronic device exists. In this application's embodiments, the scenario refers to the user's state when using the electronic device. Specifically, scenarios may include, but are not limited to: learning scenarios, sports scenarios, driving scenarios, work scenarios, sleep scenarios, do-not-disturb scenarios, gaming scenarios, audio-visual scenarios, consumption scenarios, etc. This application's embodiments do not impose any limitations on this.

[0059] Scene modes (also known as focus modes) refer to a type of mode that electronic devices can turn on or off during operation. Scene modes can be understood as a type of operating mode for electronic devices. There are various scene modes, such as Do Not Disturb mode, Sleep mode, Study mode, Work mode, Sports mode, Game mode, Audio / Video mode, Driving mode, and Consumption mode.

[0060] In some implementations, electronic devices have multiple preset scenario modes. The scenario modes provided in this application embodiment are designed to offer different functional settings for users to better utilize electronic devices in different scenarios. Electronic devices can have various scenario modes preset based on various scenarios. For example, preset scenario modes include one or more of the following: Do Not Disturb mode, Sleep mode, Study mode, Work mode, Sports mode, Game mode, Audio-visual mode, Driving mode, Consumption mode, etc. In this application embodiment, the above-mentioned preset scenario modes are only illustrative examples, and other more preset scenario modes may be included, which are not limited thereto.

[0061] After activating a scenario mode, the electronic device can adjust system functions to allow the user to fully immerse themselves in the scenario and improve user focus. In other words, scenario modes are designed to provide a better user experience in different scenarios. The configuration information of a scenario mode indicates the functional settings of the electronic device in that scenario mode. In the embodiments of this application, there is a correspondence between scenarios and scenario modes. For example, a learning scenario corresponds to a learning mode.

[0062] In some implementations, users may expect different system functions from electronic devices depending on the scenario. For example, users might expect different contacts for incoming calls or different applications for notifications. Electronic devices need different configuration information for different scenario-specific settings. However, since the configuration information for scenario modes indicates a wide range of function settings, if users manually set all the information, they may not easily understand the meaning of the specific information and may need to perform complicated procedures, resulting in a poor user experience.

[0063] To address the aforementioned issues, this application provides a method for creating scenario modes. In this method, an electronic device can determine the scenario mode configuration information using collected historical data and / or preset configuration information.

[0064] This allows for the creation of different scenario modes for various situations, eliminating the need for users to manually configure settings during the creation process. Furthermore, the configuration information can be determined based on the user's electronic device usage habits, resulting in automatically created scenario modes that better suit individual user needs and provide a superior user experience across different scenarios.

[0065] The following describes a method for creating a scenario mode provided by an embodiment of this application.

[0066] Figure 1A An exemplary flowchart illustrating a method for generating configuration information for scenario modes according to an embodiment of this application is provided. Electronic devices can create various scenario modes. Figure 1A The creation of the first scenario mode will be used as an example for introduction.

[0067] The method includes:

[0068] S101, The electronic device acquires first historical data related to the first scenario. The first historical data includes the operating data of the electronic device in the first scenario in the past.

[0069] Before executing S101, the electronic device can collect historical data in real time, including the device's operational data. Operational data refers to information generated during the operation of the electronic device, reflecting its performance, status, and health. In this embodiment, the electronic device's operational data can characterize the user's use of the device. Specifically, the electronic device's operational data can characterize one or more of the following: notifications, incoming calls, application operation, etc. It is not limited to these; the electronic device's operational data can also characterize many other situations, and this is not limited.

[0070] For example, historical data may include one or more of the following: the number of times the user interface of each application was accessed via notification; the number of times notifications of each application were deleted; the duration of calls from each contact; the number of calls from each contact; the runtime of each application; the running time of each application; the running frequency of each application; data collected by each sensor, etc. The data collected by the aforementioned sensors may include, but is not limited to: the location data of the electronic device, the user's physiological indicators (e.g., heart rate), etc.

[0071] In some implementations, electronic devices can obtain their operational data in real time or receive operational data from a server. Optionally, electronic devices can also receive operational data from other electronic devices logged into the same system account. In other words, historical data can also refer to the historical data of multiple electronic devices used by the same user.

[0072] It is understandable that electronic devices acquire historical data in real time. That is to say, in Figure 1A In the process shown, the electronic device is constantly acquiring historical data.

[0073] In one possible implementation, the electronic device can delete historical data. Specifically, the electronic device can periodically delete a portion of the historical data. For example, the electronic device can delete historical data acquired more than 7 days ago, storing only historical data from the current time within the last 7 days.

[0074] The first historical data refers to the operational data of the electronic device in the first scenario, that is, the operational data of the electronic device in the first scenario before the time the first historical data was extracted. In the embodiments of this application, the operational data of the electronic device in the first scenario can characterize the user's use of the electronic device in the first scenario. Specifically, the operational data of the electronic device in the first scenario can characterize one or more of the following: notification status, incoming call status, application operation status, etc., of the electronic device in the first scenario. It is not limited to the above; the operational data of the electronic device in the first scenario can also characterize more situations, and this is not limited.

[0075] For example, the first historical data includes one or more of the following: the number of times the user interface of each application was accessed through a notification in the first scenario; the number of times notifications of each application were deleted in the first scenario; the duration of calls from each contact in the first scenario; the number of calls from each contact in the first scenario; the runtime of each application in the first scenario; the running time of each application in the first scenario; the running frequency of each application in the first scenario, etc.

[0076] Specifically, S101 may include steps S101-1 and S101-2.

[0077] S101-1. The electronic device determines the time period M1 for running the M-type application based on the time when the M-type application is started and stopped. The electronic device running the M-type application can be considered to be in the first scenario.

[0078] The first scenario mentioned above can refer to a scenario where an M-type application is running. In this embodiment, the scenario can be determined based on the type of application running on the electronic device. Specifically, the type of application can be determined based on the tag carried by the application.

[0079] For example, the first scenario could include a scenario where an electronic device is running an application with tag b. That is, an M-class application can refer to an application with tag b.

[0080] Here, label 'b' corresponds to the first scenario. The aforementioned operation can include foreground and background operation. That is, the electronic device can determine its specific scenario based on the label of the currently running application. It is understandable that the electronic device can run applications with label 'b' in the first scenario, and it can also run applications with other labels.

[0081] Application tags can be determined during the application development phase. That is, after an application is listed on an app store, the app store can obtain the application's tags. Application tags characterize the type of application. For example, application tags may include, but are not limited to: social tags, photography tags, game tags, learning tags, office tags, sports and health tags, consumer tags, video tags, music tags, travel and navigation tags, etc. In this embodiment, the names of the application tags are merely illustrative; other names can be used for the application tags, and this is not limited.

[0082] For example, a photography scenario includes a scenario where an electronic device runs an application tagged with photography; a learning scenario includes a scenario where an electronic device runs an application tagged with learning; a gaming scenario includes a scenario where an electronic device runs an application tagged with gaming; a work scenario includes a scenario where an electronic device runs an application tagged with office; a sports scenario includes a scenario where an electronic device runs an application tagged with sports; a sports scenario includes a scenario where an electronic device runs an application tagged with sports and health; an audio-visual scenario includes a scenario where an electronic device runs an application tagged with video; an audio-visual scenario includes a scenario where an electronic device runs an application tagged with music; and a driving scenario includes a scenario where an electronic device runs an application tagged with travel navigation. In this embodiment of the application, the correspondence between the above application tags and scenarios is only illustrative and may include other correspondences, which are not limited thereto.

[0083] In one possible implementation, an electronic device can run multiple applications simultaneously, and these applications may have different tags. That is, an electronic device running multiple applications at a given time can be in multiple scenarios. For example, if an electronic device is running application app1 (tagged with "learning") and application app2 (tagged with "game") simultaneously, it can be considered that the electronic device is simultaneously in a learning scenario and a game scenario.

[0084] In another possible implementation, an application may have multiple tags. That is, an electronic device running a single application at a given time can also be in multiple scenarios. For example, if an electronic device is running application app3 with both the learning and game tags, it can be considered that the electronic device is simultaneously in both a learning scenario and a game scenario.

[0085] Optionally, the first scenario described above can also be determined using sensor data collected by the electronic device. For example, the electronic device can determine whether it is currently in a motion scenario, a sleep scenario, a driving scenario, etc., based on sensor data.

[0086] In the embodiments of this application, the above-described method for determining when an electronic device is in the first scenario is merely illustrative. Other methods may also be used to determine when an electronic device is in the first scenario, and no limitation is made thereto.

[0087] In some implementations, since the M-class application includes one or more applications, and the applications may be started and closed multiple times, the time period M1 may include one or more time periods.

[0088] The S101-2 electronic device acquires historical data within time period M1, i.e., the first historical data.

[0089] The electronic device acquiring time period M1 can be understood as: the electronic device is determined to be in the first scenario within time period M1. Therefore, the electronic device acquiring historical data within time period M1 is equivalent to acquiring the first historical data under the first scenario.

[0090] For example, an electronic device determines that it starts a learning application at 8:00 AM and closes it by 12:00 PM. Between 8:00 AM and 12:00 PM, it acquires historical data including: Data 1, 5 incoming calls from contact X1; Data 2, 30-minute call duration from contact X2; and Data 3, 3 clicks on application X3's notification display of its user interface. Therefore, the historical data for the learning scenario determined by the electronic device includes: Data 1, Data 2, and Data 3. Data 1, Data 2, and Data 3 are provided as examples only.

[0091] S102. The electronic device determines the configuration information of the first scenario mode based on the first historical data and / or the preset configuration information of the first scenario mode. The configuration information of the first scenario mode indicates the function settings of the electronic device in the first scenario mode. The first scenario corresponds to the first scenario mode.

[0092] In some implementations, after acquiring the first historical data, the electronic device can determine the configuration information of the first scenario mode. The configuration information of the first scenario mode includes the functional settings of the electronic device under the first scenario mode. This configuration information may include: the activation condition A1 of the first scenario mode, the contacts allowed to receive calls A2, and the applications allowed to send notifications A3.

[0093] The activation condition A1 can contain one or more conditions. If any one of the conditions in activation condition A1 is met, the first scenario mode can be automatically activated; if none of the conditions in activation condition A1 are met, scenario mode A can be automatically deactivated. Activation condition A1 can include one or more of the following: time-dimensional conditions, location-dimensional conditions, and application-dimensional conditions. Specifically, activation condition A1 includes one or more of the following: time period, location range, or specific application name. The electronic device can determine whether it meets the time-dimensional condition based on whether the current time falls within a time period; the electronic device can determine whether it meets the location-dimensional condition based on whether the current location falls within a location range; and the electronic device can determine whether it meets the application-dimensional condition based on whether an application is currently running.

[0094] For example, the activation condition A1 includes the time dimension condition "8:00-18:00". When the time period "8:00-18:00" is within the time period, the first scenario mode can be automatically activated; when the time period "8:00-18:00" is not within the time period, the first scenario mode can be automatically deactivated.

[0095] Activation condition A1 includes the location dimension condition "within 300 meters of location XX". When the electronic device is within the location range of "within 300 meters of location XX", the first scenario mode can be automatically activated; when the electronic device is not within the location range of "within 300 meters of location XX", the first scenario mode can be automatically deactivated. It is not limited to "within 300 meters"; the electronic device's default location dimension condition does not impose any restrictions on this range.

[0096] Enabling condition A1 includes the condition "Application XX" at the application level. When the electronic device is running "Application XX", the first scenario mode can be automatically enabled; when the electronic device stops running "Application XX", the first scenario mode can be automatically disabled.

[0097] In the embodiments of this application, the above-mentioned enabling condition A1 is only illustrative. Enabling condition A1 may also have more dimensions, and the conditions included in enabling condition A1 may also have other more or fewer contents, which is not limited.

[0098] For example, activation condition A1 may also include sleep-related conditions, such as the condition "activate during sleep". The electronic device may automatically activate the first scenario mode when it detects that the user is asleep. The electronic device may automatically deactivate the first scenario mode when it detects that the user is not asleep. Activation condition A1 may also include motion-related conditions, such as the condition "activate during exercise". The electronic device may automatically activate the first scenario mode when it detects that the user is in motion. The electronic device may automatically deactivate the first scenario mode when it detects that the user is not in motion.

[0099] The number of contacts included in the allowed caller ID A2 can be one or more. In this embodiment, allowing a call means that the electronic device can receive and output a call notification. For example, outputting a call notification may be done in one or more of the following ways: outputting an audio signal, outputting a vibration signal, displaying a pop-up window containing the call notification, etc. In other words, when allowing a call, the electronic device will proactively notify the user that the device has received a call notification.

[0100] Incoming calls other than those allowed are called blocked calls. The blocked calls scenarios can be categorized into the following types:

[0101] Scenario a: After enabling the profile mode, the electronic device can receive incoming call notifications from the other electronic device, but does not output an incoming call notification. Furthermore, after exiting the profile mode, the electronic device then outputs a missed call notification.

[0102] Scenario b: After enabling the scenario mode, the electronic device can receive incoming call notifications from the other electronic device and output the notification silently. This silent notification means that when the electronic device receives an incoming call notification, it does not output a sound signal, vibration signal, or pop-up window, but instead saves the notification in the notification center interface, which the user can then actively view later. In other words, in scenario b, the electronic device will not actively notify the user that it has received an incoming call notification.

[0103] In the embodiments of this application, the above-mentioned situations of blocking incoming calls are only illustrative examples, and may include other more or fewer situations, which are not limited thereto.

[0104] In one possible implementation, when an incoming call from the other electronic device is a blocked call, the other electronic device can sense that the other electronic device has activated a context mode. For example, when the other electronic device calls the other electronic device, it can output an audio signal saying, "The number you dialed is in context mode, please try again later." Alternatively, the other electronic device may not sense that the other electronic device has activated a context mode. For example, when the other electronic device calls the other electronic device, it can output an audio signal saying, "The number you dialed is temporarily unavailable, please try again later." In this embodiment, no limitation is made.

[0105] In this embodiment of the application, after activating the first scenario mode, the electronic device allows incoming calls from contact A2; for incoming calls from anyone other than contact A2, the electronic device blocks the incoming calls. The blocking of calls includes, but is not limited to, the situations described in a and b above.

[0106] The number of applications included in the "Allow Notifications" application A3 can be one or more. In this embodiment, "Allow Notifications" means that the electronic device can receive and output notifications. Different applications may output notifications in different ways. For example, outputting incoming call notifications may include one or more of the following: outputting an audio signal, outputting a vibration signal, displaying a pop-up window containing the notification, etc. In other words, when notifications are allowed, the electronic device will proactively notify the user that the electronic device has received a notification.

[0107] Notifications other than allowed notifications are called prohibited notifications. Prohibited notifications in scenario patterns can be specifically categorized as follows:

[0108] Scenario c: After activating the profile mode, the electronic device can receive notifications but does not output them. Furthermore, after exiting the profile mode, the electronic device then outputs the notification.

[0109] Scenario d: After enabling the scenario mode, the electronic device can receive notifications and output them silently. Silent notifications mean that when the electronic device receives a notification, it does not output a sound signal, vibration signal, or pop-up window, but instead saves the notification in the notification center interface, which the user can then actively view later. In other words, in scenario b, the electronic device will not actively notify the user that a notification has been received.

[0110] In the embodiments of this application, the above-mentioned situations of prohibiting notification are only illustrative examples, and may include other more or fewer situations, which are not limited thereto.

[0111] In this embodiment, after activating the first scenario mode, the electronic device allows notifications from application A3; for notifications from applications other than application A3, the electronic device blocks notifications. The blocking of notifications includes, but is not limited to, the cases described above, c and d.

[0112] In one possible implementation, the electronic device also includes various meta-services. Meta-services are applications within the electronic device that do not require installation. Meta-services differ from traditional applications in that they are more lightweight. The application A3 that allows notifications can also be understood as both the application that allows notifications and the meta-service A3. The following explanation will use an application whose configuration information includes allowing notifications as an example.

[0113] Optionally, the configuration information for the first scenario mode may also include one or more of the following: whether to repeat the ringing of incoming calls; whether to answer incoming calls intelligently; whether to enable the smart experience; and the association with other modes, such as whether to associate with dark mode, eye protection mode, power saving mode, etc.

[0114] Among these, "Repeated Ringing" can be understood as the electronic device issuing another call notification when a call from the same contact (A2) is received again within a certain time interval between receiving a call from a contact mentioned above. "Smart Answering Calls" means the electronic device can answer blocked calls (calls from anyone other than contact A2) through a smart assistant. "Smart Experience" means the electronic device provides timely services to the user; for example, in the event of an emergency (such as an earthquake or severe weather), it can output a notification containing information about the emergency, regardless of the restrictions on allowed notifications set above. "Associated Dark Mode" means that dark mode is simultaneously enabled when the first scenario mode is enabled, and simultaneously disabled when the first scenario mode is disabled. "Associated Eye Protection Mode" means that eye protection mode is simultaneously enabled when the first scenario mode is enabled, and simultaneously disabled when the first scenario mode is disabled. "Associated Power Saving Mode" means that power saving mode is simultaneously enabled when the first scenario mode is enabled, and simultaneously disabled when the first scenario mode is disabled. The scenarios are not limited to the aforementioned associated modes; they can also be associated with other modes without limitation.

[0115] Dark Mode, also known as Dark Color Mode, is a UI theme that contrasts with Light Mode. Dark Mode reduces screen brightness by using dark backgrounds and light text, which can reduce power consumption of electronic devices to some extent. Eye Comfort Mode reduces blue light radiation and alleviates eye strain by adjusting screen colors and brightness. Power Saving Mode reduces power consumption and extends battery life by adjusting settings and functions of electronic devices; for example, it can limit background processes, reduce the performance of some devices, and disable unnecessary functions.

[0116] In the embodiments of this application, the configuration information of the first scenario mode described above is only illustrative and may include other more or less information, which is not limited thereto.

[0117] In some implementations, the configuration information for the first scenario mode can be determined in the following three ways:

[0118] Method 1: Determined based on first historical data.

[0119] In some implementations, the electronic device can determine the configuration information of the first scenario mode using method 1 without obtaining the preset configuration information.

[0120] In the embodiments of this application, the above-described use of method 1 to determine the configuration information of the first scenario mode is only an illustrative example. Method 1 may also be used in more or fewer cases, and this is not limited.

[0121] In some implementations, electronic devices can determine the configuration information of a first scenario mode based on first historical data.

[0122] For example, after acquiring the first historical data, the electronic device can obtain one or more of the following information from the first historical data: the most frequent running time period B1 of the application with tag b, the running time of the application with tag b exceeding threshold m1, the running frequency of the application with tag b exceeding threshold m2, the application to which the notification belongs is B4, the number of times the notification has been opened exceeds threshold m3, the contact B5 whose call duration exceeds threshold m4, the number of times the contact has received a call exceeds threshold m5, the number of times the contact has rejected a call exceeds threshold m6, the application to which the notification belongs is B8, the duration of the location B9 of the electronic device exceeding threshold m8, etc. The time period B1 can be determined based on the running time of each application in the first scenario in the first historical data. For example, the time period B1 can specifically refer to a certain time period within a day.

[0123] Understandably, during time period B1, the electronic device is more likely to be in the first scenario. Enabling the first scenario mode during time period B1 would improve the user experience. When the electronic device is in the first scenario, the user is more likely to accept calls from contact set M1. Allowing calls from contact set M1 in the first scenario mode would improve the user experience. When the electronic device is in the first scenario, the user is more likely to receive notifications from application set M2. Allowing notifications from application set M2 in the first scenario mode would improve the user experience. When the electronic device is near location B9, it is more likely to be in the first scenario. Enabling the first scenario mode near location B9 would improve the user experience.

[0124] For example, the contact set M1 includes: contact B5 and / or contact B6. Optionally, the contact set M1 does not include contact B7. The application set M2 includes application B4, and the application set M2 also includes: application B2, application B3, the intersection of application B2 and application B3, and the union of application B2 and application B3. Optionally, the application set M2 does not include application B8.

[0125] In this embodiment, the aforementioned time period B1, contact set M1, and application set M2 can also be determined through other means based on the first historical data, and there is no limitation on this.

[0126] In this scenario, the electronic device can set activation condition A1 to be within the time period B1 and near the location B9. Optionally, activation condition A1 can also be set to launch application B2. The electronic device can set the contacts A2 to allow incoming calls to contact set M1. The electronic device can set the applications A3 to allow notifications to to application set M2.

[0127] In Mode 1, the configuration information of the first scenario mode, except for the activation condition A1, the contacts allowed to receive calls A2, and the applications allowed to receive notifications A3, is set by default by the electronic device.

[0128] In the embodiments of this application, the process of determining the configuration information of the first scenario mode described above is only an illustrative example. The electronic device may also obtain other more or less information through the first historical data to determine the configuration information of the first scenario mode, which is not limited in this respect.

[0129] Method 2: Determine the preset configuration information based on the first scenario mode.

[0130] In some implementations, the electronic device can use method 2 to determine the configuration information of the first scenario mode when it has pre-set configuration information and the information obtained from the first historical data is insufficient. In the embodiments of this application, the above-described use of method 2 to determine the configuration information of the first scenario mode is only illustrative, and method 2 can also be used in cases involving more or fewer scenarios, without limitation.

[0131] In one possible implementation, if the electronic device determines that there is no first historical data related to the first scenario, the electronic device can set the configuration information of the first scenario mode to the preset configuration information of the first scenario mode.

[0132] In some implementations, the electronic device not only has multiple preset scenario modes, but can also store preset configuration information for each scenario mode. The preset configuration information can be set by developers based on the theoretically satisfactory user needs when the electronic device is in each scenario mode. In other words, the preset configuration information indicates the preset functional settings of the electronic device in each scenario mode. The preset configuration information can include: activation conditions, allowed callers, and allowed notification applications. The activation conditions, allowed callers, and allowed notification applications mentioned above can be compared analogously to the activation condition A1, allowed callers A2, and allowed notification applications A3 included in the configuration information for the first scenario mode, and will not be elaborated upon here.

[0133] Optionally, the preset configuration information may also include: whether to create a default scene mode; whether to repeat the ringtone for incoming calls; whether to intelligently answer incoming calls; whether to enable smart experience; whether to associate with dark mode; whether to associate with eye protection mode; whether to associate with power saving mode, etc. The optional contents of the above preset configuration information can be compared with the optional contents of the configuration information for the first scene mode, and will not be repeated here.

[0134]

[0135] Table 1-1

[0136]

[0137] Table 1-2

[0138] Tables 1-1 and 1-2 exemplarily illustrate the preset configuration information for various scenario modes provided in the embodiments of this application. Referring to Tables 1-1 and 1-2, the preset configuration information specifically includes the following categories: default creation, time fence, geofence, geofence triggering device, application start / stop, do-not-disturb policy, repeated call ringing, smart answering, notification do-not-disturb policy, smart experience, dark mode, eye protection mode, and power saving mode; exemplarily, electronic devices have preset configuration information for the following scenario modes: do-not-disturb mode, sleep mode, study mode, work mode, sports mode, game mode, audio-visual mode, driving mode, and custom mode.

[0139] The category "Default Creation" indicates whether an electronic device creates a scenario mode by default. A default creation scenario mode means that the electronic device can automatically create a scenario mode without requiring user intervention.

[0140] The category "Time Fence" is used to characterize the time dimension of the conditions in the activation conditions.

[0141] The category "Location Fence" is used to enable conditions in the location dimension of the conditions.

[0142] The category "Geofence Trigger Device" is used to restrict the types of electronic devices that can trigger conditions in the above-mentioned location dimensions.

[0143] The category "Application Start / Stop" is used to characterize the location dimension conditions in the activation conditions of the scenario mode.

[0144] The category "Do Not Disturb Policy" is used to characterize the contacts allowed to receive calls. Specifically, the "Do Not Disturb Policy" category includes the following policies: block all calls, allow all calls, allow calls from existing contacts, allow calls from favorite contacts, allow calls from specific contacts, and block calls from specific contacts. In this embodiment, the policies included in the "Do Not Disturb Policy" category are merely illustrative, and may include other policies, which are not limited thereto.

[0145] Existing contacts include one or more contacts stored in the Contacts app. Electronic devices can add or delete stored contacts within the Contacts app based on user actions. Favorited contacts include one or more contacts stored in the Contacts app that the user has saved. Electronic devices can add or delete favorited contacts within the Contacts app based on user actions.

[0146] Designated contacts include one or more contacts specified by the electronic device. These designated contacts may include contacts with specific tags. For example, contact tags may include one or more of the following: friends, colleagues, family members, teachers, classmates, etc. For instance, if the default configuration information for the learning mode includes allowing designated contacts to call, then the designated contacts may include contacts tagged with "teacher" and contacts tagged with "classmate," without limitation. The designated contacts included in the default configuration information for different scenario modes may differ, which can be set by the developers according to the characteristics of each scenario mode.

[0147] The category "Repeated ringing" indicates whether repeated ringing is allowed.

[0148] The category "Smart Answering" indicates whether the smart assistant is allowed to answer blocked calls.

[0149] The category "Do Not Disturb Policy" is used to characterize applications that allow notifications. Specifically, the "Do Not Disturb Policy" category includes the following policies: application types that allow notifications and application types that block notifications.

[0150] The category "Dark Mode" indicates whether a scene mode is associated with Dark Mode. The category "Eye Protection Mode" indicates whether a scene mode is associated with Eye Protection Mode. The category "Power Saving Mode" indicates whether a scene mode is associated with Power Saving Mode. A scene mode's association with other modes can be categorized as associated or not associated. For example, if the first scene mode is not associated with Power Saving Mode, turning the first scene mode on or off will not affect the power saving mode's on or off status on the electronic device. If the first scene mode is associated with Power Saving Mode, then turning the first scene mode on will simultaneously enable Power Saving Mode, and turning the first scene mode off will simultaneously disable Power Saving Mode.

[0151] In one possible implementation, the association of the aforementioned scenario modes with other modes can further include the following strategies: no association, association, association on, and association off. For example, if the first scenario mode is not associated with dark mode, then turning the first scenario mode on or off will not affect whether dark mode is on or off in the electronic device. If the first scenario mode is associated with dark mode, then turning on the first scenario mode will simultaneously turn on dark mode, and turning off the first scenario mode will simultaneously turn off dark mode. If the first scenario mode is associated with turning on dark mode, then turning on the first scenario mode will simultaneously turn on dark mode, and turning off the first scenario mode will not affect whether dark mode is off. If the first scenario mode is associated with turning off dark mode, then turning on the first scenario mode will not affect whether dark mode is on or off, and turning off the first scenario mode will simultaneously turn off dark mode.

[0152] The following are examples of pseudocode related to Tables 1-1 and 1-2.

[0153] "version":1,

[0154] "intelligentSceneList":[

[0155] {"modeId":1,"isPreset":true},

[0156] {"modeId":2,"isPreset":true},

[0157] {"modeId":3,"isPreset":false},

[0158] {"modeId":4,"isPreset":false},

[0159] {"modeId":5,"isPreset":false},

[0160] {"modeId":6,"isPreset":false},

[0161] {"modeId":7,"isPreset":false},

[0162] {"modeId":8,"isPreset":false} ]

[0164] The "version" indicates the information category included in the preset configuration information, and "version: 1" indicates the category "default creation". "modeId" indicates the mode number; Tables 1-1 and 1-2 list 8 scenario modes, each indicated by a number from 1 to 8. "isPreset" indicates the specific setting for the category "default creation". ""modeId":1,"isPreset":true" indicates that the electronic device will create scenario mode number 1 by default. ""modeId":4,"isPreset":false" indicates that the electronic device will not create scenario mode number 4 by default. In this embodiment, the above pseudocode is for illustrative purposes only and is not intended to limit the scope of the application.

[0165] For example, as shown in Table 1-1, the preset configuration information for Do Not Disturb mode includes: default creation of Do Not Disturb mode; no activation conditions; blocking all incoming calls; enabling repeat ringback tones; disabling smart answering; disabling all app notifications; disabling smart experience; not associated with dark mode; not associated with eye protection mode; and not associated with power saving mode. For the preset configuration information of other scenario modes, please refer to the contents shown in Tables 1-1 and 1-2 above, which will not be elaborated upon here.

[0166] In some implementations, the preset configuration information can be set by developers based on the theoretically satisfactory needs of users in various scenario modes of electronic devices. For example, based on the common human sleep time of "23:00-07:00", the time fence for sleep mode is set to "23:00-07:00". Based on the common human study time of "weekdays 08:00-12:00-14:00-18:00", the time fence for study mode is set to "weekdays 08:00-12:00-14:00-18:00". Based on the common human use of social media apps, video apps, or music apps when watching movies or listening to music, the "notification do-not-disturb policy" for video / audio mode is set to "allow notifications from social media apps, video apps, and music apps".

[0167] In the embodiments of this application, the contents of Tables 1-1 and 1-2 above are only illustrative examples. The preset configuration information of each scenario mode may also include more or less content, which is not limited.

[0168] In some implementations, after obtaining the preset configuration information for each scenario mode, the electronic device sets the configuration information of the first scenario mode as the preset configuration information for the first scenario mode. The preset configuration information for each scenario mode includes the preset configuration information for the first scenario mode.

[0169] The preset configuration information for the first scenario mode is the same as the preset configuration information for the first scenario mode. For example, if the first scenario mode is a preset scenario mode, such as a learning mode, the electronic device can set the configuration information of the first scenario mode to the preset configuration information of the learning mode.

[0170] Method 3: Determined based on the preset configuration information of the first historical data and the first scenario mode.

[0171] In some implementations, the electronic device can determine the configuration information of the first scenario mode using method 3 when it has obtained preset configuration information and the information obtained from the first historical data is relatively sufficient. In the embodiments of this application, the above-described use of method 3 to determine the configuration information of the first scenario mode is only illustrative and can also include the use of method 3 in more or fewer situations, which is not limited.

[0172] In some implementations, the electronic device can determine the configuration information of the first scenario mode based on the first historical data and the preset configuration information of the first scenario mode.

[0173] Specifically, in method 3, the activation condition A1, the allowed caller A2, and the allowed notification application A3 in the configuration information of the first scenario mode can be determined based on the information contained in the first historical data and the information contained in the preset configuration information of the first scenario mode.

[0174] Specifically, the electronic device can set the activation condition A1 to one or more of the following: the time dimension condition in the activation conditions included in the preset configuration information of the first scenario mode, and the intersection or union of the time period B1 mentioned in method 1 above; the location dimension condition in the activation conditions included in the preset configuration information of the first scenario mode, and the intersection or union of the location B9 mentioned in method 1 above; the application dimension condition in the activation conditions included in the preset configuration information of the first scenario mode, and the intersection or union of the application B2 mentioned in method 1 above.

[0175] The electronic device can set the allowed caller A2 to be the intersection or union of the allowed caller information contained in the preset configuration information of the first scenario mode and the contact set M1 mentioned in method 1 above. The electronic device can set the allowed notification application A3 to be the intersection or union of the allowed notification application information contained in the preset configuration information of the first scenario mode and the application set M2 mentioned in method 1 above.

[0176] In other words, in Method 3, the specific content included in the configuration information of the first scenario mode needs to take into account both the user's usage habits and the developer's pre-conceived ideas for the first scenario mode.

[0177] The electronic device can also determine information in the configuration information of the first scenario mode other than the activation condition A1, the contacts allowed to receive calls A2, and the applications allowed to receive notifications A3, based on the information contained in the preset configuration information of the first scenario mode.

[0178] In the embodiments of this application, the preset configuration information of the first scenario mode mentioned in method 3 and the preset configuration information of the first scenario mode mentioned in method 2 are the same concept. For details, please refer to the relevant description of method 2 above, which will not be repeated here.

[0179] In the embodiments of this application, the process of determining the configuration information of the first scenario mode described above is only an example. The electronic device may also determine the configuration information of the first scenario mode based on the first historical data and the preset configuration information of the first scenario mode in other more or fewer ways, and there is no limitation thereto.

[0180] In some implementations, the electronic device can execute the command after triggering the creation of the first scenario mode. Figure 1A The method flow shown can also be executed in real time. Figure 1AThe method flow shown is that execution is not based on triggering the creation of the first scenario mode. Figure 1A The method flow is shown.

[0181] Electronic devices can be based on Figure 1A The method shown obtains the configuration information for various preset scenario modes.

[0182] Implement the above Figure 1A The method shown allows electronic devices to determine scenario configuration information based on historical data. This results in subsequently created scenario modes that are more tailored to the user, leading to a better user experience.

[0183] Figure 1B An exemplary embodiment of this application illustrates a method flow for creating configuration information for a scenario mode. Figure 1B The following is an example of how to display the configuration information for the first scenario mode.

[0184] S201, The electronic device triggers the creation of the first scenario mode.

[0185] In some implementations, the electronic device can receive a user operation to trigger the creation of a first scenario mode. The user operation may include one or more of the following: touch operation, click operation, gesture operation, voice operation, and eye-tracking operation. In this embodiment, the operation that triggers the creation of the first scenario mode is not limited. Specifically, triggering the creation of the first scenario mode can be divided into two cases: Case 1, the first scenario mode is a preset scenario mode; Case 2, the first scenario mode is a custom scenario mode.

[0186] In some implementations, electronic devices have multiple preset scenario modes. The scenario modes provided in this application embodiment are designed to offer different functional settings for users to better utilize electronic devices in different scenarios. Electronic devices can have various scenario modes preset based on various scenarios. For example, preset scenario modes include one or more of the following: Do Not Disturb mode, Sleep mode, Study mode, Work mode, Sports mode, Game mode, Audio-visual mode, Driving mode, Consumption mode, etc. In this application embodiment, the above-mentioned preset scenario modes are only illustrative examples, and other more preset scenario modes may be included, which are not limited thereto.

[0187] In scenario 1, before executing S201, the electronic device displays the names of multiple preset scenario modes and the creation controls corresponding to each preset scenario mode. The preset scenario modes include a first scenario mode. The electronic device can respond to an operation applied to the creation control corresponding to the first scenario mode, triggering the creation of the first scenario mode. Optionally, the electronic device can access a scenario mode application through settings. In this embodiment, the scenario mode application is a system application used to implement functions related to scenario modes. In this embodiment, the names of the scenario mode applications are merely illustrative, and the names of the applications used to implement functions related to scenario modes are not limited.

[0188] Figures 2A-2C An example is shown of a user interface that triggers the creation of a first scenario mode in scenario 1. The example will use the first scenario mode as a preset learning mode.

[0189] Figure 2A An exemplary illustration shows a user interface 210 of a settings application provided in an embodiment of this application. The user interface 210 includes multiple system function options. For example, the user interface 210 includes a profile mode option 211. The electronic device can enter the profile mode application in response to a click operation on the profile mode option 211, i.e., display... Figure 2B The user interface 220 shown.

[0190] User interface 220 is a user interface provided by an electronic device for displaying configuration information for a do-not-disturb scenario. For example, user interface 220 is the default user interface displayed after entering a scenario mode application. In this embodiment, the default user interface displayed after entering a scenario mode application is not limited. For a detailed description of the user interface used to display configuration information for the scenario mode, please refer to the following detailed description of user interfaces 330 and 340; it will not be repeated here.

[0191] User interface 220 includes an add mode control 221. The electronic device displays a click operation on the add mode control 221. Figure 2C The user interface 230 is shown. User interface 230 includes the names of multiple preset scenario modes and corresponding creation controls for each preset scenario mode. For example, user interface 230 includes the name of a learning mode and a corresponding creation control 231. The electronic device responds to a click operation on the creation control 231, triggering the creation of the first scenario mode, i.e., the learning mode.

[0192] In scenario 2, the electronic device can respond to the operation of the creation control applied to the custom mode, enter the name of the first scenario mode, and trigger the creation of the first scenario mode.

[0193] Figures 2D-2E An example is shown of the user interface that triggers the creation of the first scenario mode in scenario 2. For example, a custom scenario mode is used as the first scenario mode for illustration.

[0194] Figure 2D An exemplary embodiment of the user interface 230 provided in this application is shown. The electronic device responds to actions... Figure 2B The click operation of the added modal control 221 displays the user interface 230. For example... Figure 2D As shown, the user interface 230 also includes a creation control 232 corresponding to the custom mode. The electronic device responds to a click operation applied to the creation control 232 and displays... Figure 2E The user interface 240 is shown. User interface 240 is used to edit the name and icon of a custom mode. User interface 240 includes an input box 241, a color box 242, an icon box 243, and a creation control 244. The electronic device can respond to the operation of entering the text "Learning Mode" in the input box 241 to edit the name of the first scenario mode to "Learning Mode". The electronic device can respond to the operation of the orange option 242A in the color box 242 to edit the icon color of the first scenario mode to orange. The electronic device can also respond to the operation of the icon option 243A in the icon box 243 to edit the icon style of the first scenario mode to the style corresponding to icon option 243A. The electronic device responds to the click operation of the creation control 244 to trigger the creation of the first scenario mode named "Learning Mode".

[0195] In this application embodiment, the user interface that triggers the creation of the first scenario mode in the above two situations is only illustrative. Figures 2A-2E The user interface shown may include more or less content, without limitation.

[0196] In some implementations, electronic devices not only have multiple preset scenario modes, but can also associate these preset scenario modes with specific scenarios. That is, there is a correspondence between preset scenario modes and scenarios. For example, a learning mode is associated with a learning scenario, a work mode with a work scenario, a sports mode with a sports scenario, a game mode with a game scenario, an audio-visual mode with an audio-visual scenario, and a driving mode with a driving scenario, etc. In the embodiments of this application, the above-mentioned correspondence between preset scenario modes and scenarios is only illustrative and may include many other correspondences between preset scenario modes and scenarios, which are not limited thereto.

[0197] For example, when the first scenario mode belongs to a preset scenario mode, such as a learning mode, the electronic device can determine the first scenario corresponding to the first scenario mode to be created as a learning scenario based on the learning mode associating with the learning scenario.

[0198] In one possible implementation, the electronic device can also associate a custom scenario with a scene. Specifically, the electronic device can determine the similarity between the name of the custom scenario and the names of multiple preset scenarios, and identify the scene corresponding to the custom scenario as the scene corresponding to the preset scenario with the highest similarity to the name of the custom scenario.

[0199] For example, when the first scenario mode is a custom scenario mode, such as a scenario mode named "Learning Mode", the electronic device can determine the preset scenario mode with the highest similarity to the custom scenario mode name "Learning Mode" as the learning mode. Then, based on the learning mode associating with the learning scenario, the first scenario corresponding to the first scenario mode to be created is determined as the learning scenario. That is, the name of the first scenario mode input by the user is semantically the same as or similar to the first scenario.

[0200] In this embodiment of the application, the method of confirming that the scenario corresponding to the first scenario mode to be created is the first scenario is only an example. Other methods may also be used to determine the first scenario, and no limitation is made thereto.

[0201] S202, The electronic device obtains the configuration information of the first scenario mode.

[0202] The configuration information for the first scenario mode mentioned above can be based on the above. Figure 1A The method shown is used to obtain the result. Specifically, the electronic device can perform the above-described procedure in S202. Figure 1A The method flow shown can also be executed before S201. Figure 1A The method flow is shown, and then the electronic device reads the configuration information of the first scenario mode.

[0203] In one possible implementation, if the first scenario mode is a custom scenario mode and the information obtained from the first historical data is sufficient, the configuration information of the first scenario mode is determined based on the above method 1.

[0204] In one possible implementation, when the first scenario mode is a custom scenario mode, the configuration information of the first scenario mode is the configuration information of the preset scenario mode that has the highest name similarity to the first scenario mode. For example, if the first scenario mode is a custom scenario mode, such as a learning mode, the electronic device first determines that the preset scenario mode with the highest similarity to the learning mode is the learning mode, and then sets the configuration information of the first scenario mode to the configuration information of the learning mode. Optionally, if there is no preset scenario mode with the highest name similarity to the first scenario mode, then the configuration information of the first scenario mode is set to the configuration information of the custom mode.

[0205] S203. The electronic device displays all or part of the configuration information of the first scenario mode.

[0206] In some implementations, after obtaining the configuration information of the first scenario mode, the electronic device has the function of enabling or disabling the first scenario mode. In the embodiments of this application, the electronic device starting to have the function of enabling or disabling the first scenario mode can be understood as the electronic device completing the creation of the first scenario mode. That is, the moment when the electronic device switches from not having the function of enabling or disabling the first scenario mode to having the function of enabling or disabling the first scenario mode is the moment when the first scenario mode is completed.

[0207] After the creation of the first scenario mode is completed, the electronic device can display all or part of the configuration information of the first scenario mode. The first scenario mode can be divided into scenario 1 and scenario 2, which can be referred to in the relevant description of S201 above, and will not be repeated here.

[0208] Figure 2F An example is shown of a user interface that displays configuration information for a first scenario mode in scenario 1.

[0209] For example, the electronic device responds to the above-mentioned Figure 2C The click operation of the creation control 231 in the middle displays Figure 2F The user interface 250 shown is a user interface provided by an electronic device for displaying configuration information of a learning mode. For example, the user interface 250 includes: option box 251 and option box 252. Option box 251 contains information about the activation conditions in the learning mode configuration information. Option box 252 contains the following information: allowed notification applications and allowed callers for the learning mode. For more information on the user interface for displaying configuration information of a scenario mode, please refer to the following... Figures 3A to 5 A detailed introduction will not be provided here. The electronic device can respond to an upward swipe gesture on the user interface 250 to view more configuration information for the learning mode.

[0210] Figure 2G An example is shown of a user interface that displays configuration information for the first scenario mode in scenario 2.

[0211] For example, the electronic device responds to the above-mentioned Figure 2C The click operation of the creation control 231 in the middle displays Figure 2G The user interface 260 shown is shown. The preset scenario mode that is most similar to the custom scenario mode name "Learning Mode" is the Learning Mode. Therefore, the configuration information for the Learning Mode is the same as the configuration information for the Learning Mode itself.

[0212] User interface 260 is a user interface provided by an electronic device for displaying configuration information of a learning mode. For example, user interface 260 includes: option box 261 and option box 262. Option box 261 contains information about the activation conditions in the learning mode configuration information. Option box 262 contains the following information: allowed notification applications and allowed callers for the learning mode. For more information on user interfaces for displaying configuration information of scenario modes, please refer to the following... Figures 3A to 5 A detailed introduction will not be provided here.

[0213] The electronic device can respond to an upward swipe action on the user interface 260 to view other configuration information for the learning mode.

[0214] In one possible implementation, after the electronic device completes the creation of the first scenario mode, it may directly execute S203, or it may first jump to the default user interface displayed by the scenario mode application, and then execute S203 after receiving user input. This is not limited in the embodiments of this application.

[0215] Optionally, S204, the electronic device activates the first scenario mode.

[0216] The electronic device can execute S204 after executing S203.

[0217] In some implementations, the electronic device can activate the first scenario mode after it has been created. At this point, the electronic device can configure corresponding functions based on the configuration information of the first scenario mode. During the activation of the first scenario mode, the electronic device allows incoming calls from contact A2 and notifications from application A3.

[0218] Specifically, the electronic device can activate the first scenario mode when it detects that the activation condition A1 is met, or it can activate the first scenario mode in response to the user's operation to activate the first scenario mode.

[0219] Under normal circumstances, electronic devices can only activate one scenario mode at a time.

[0220] Optionally, S205, the electronic device turns off the first scenario mode.

[0221] The electronic device can execute S205 after executing S204.

[0222] In some implementations, the electronic device can turn off the first scenario mode after it has been activated. Specifically, the electronic device can turn off the first scenario mode if it detects that the activation condition A1 is not met, or it can turn off the first scenario mode in response to a user's action to turn it off.

[0223] Optionally, the electronic device may close the first scenario mode and open other scenario modes if it detects that the conditions for opening other scenario modes are met during the process of opening the first scenario mode, or it may close the first scenario mode and open other scenario modes in response to the user's operation to open other scenario modes.

[0224] Optionally, in step S206, the electronic device updates the configuration information of the first scenario mode based on the operating data in the first scenario mode.

[0225] The electronic device can execute S206 after executing S203.

[0226] In some implementations, since the electronic device acquires historical data in real time, it can cluster and segment the operating data in the first scenario mode from the historical data. Then, the electronic device can update the configuration information of the first scenario mode based on the operating data in the first scenario mode. The specific update method can be referred to Method 1 shown in S102 above, and will not be elaborated here.

[0227] Optionally, S207, the electronic device modifies the configuration information of the first scenario mode.

[0228] The electronic device can execute S207 after executing S203.

[0229] In some implementations, after creating a first scenario mode, the electronic device can modify the configuration information of that first scenario mode. The relevant user interface for modifying the configuration information of the first scenario mode can be found below. Figures 3C to 4C Related information.

[0230] Implement the above Figure 1B The method shown allows for setting different scenario modes for different situations, eliminating the need for users to manually configure information when creating each scenario mode. This reduces user steps and avoids a complicated experience during scenario mode creation. Furthermore, the configuration information can be determined based on the user's electronic device usage habits, resulting in scenario modes that are more tailored to the user and provide a better user experience.

[0231] In this embodiment, the first scenario mode can be created by the user or by the electronic device by default. For example, the electronic device can create a sleep mode and a do-not-disturb mode by default. In this embodiment, the first scenario mode created by default is only illustrative; the electronic device can also create other, more, or fewer scenario modes by default, and this is not limited.

[0232] In some implementations, whether it's the first scene mode created by default on the electronic device, or the above-mentioned... Figure 1A The process shown creates a first scenario mode, and users can view, modify, and delete the configuration information of the first scenario mode.

[0233] The following describes the relevant user interface provided by the electronic device after the creation of the first scenario mode, as provided in the embodiments of this application, with reference to the user interface.

[0234] Figures 3A-3D Several user interfaces for displaying configuration information for scenario modes are illustrated as examples.

[0235] Figure 3A The user interface 310 shown is a user interface used to display configuration information for the Do Not Disturb mode. The electronic device can respond to an upward swipe operation on the user interface 310 to view more configuration information for the Do Not Disturb mode. Figure 3B The user interface 320 shown is a user interface used to display configuration information for the sleep mode. The electronic device can respond to an upward swipe operation on the user interface 320 to view more configuration information for the sleep mode. Figure 3C The user interface 330 shown is a user interface used to display configuration information for the learning mode. The electronic device can display the user interface 310 in response to a leftward swipe operation performed on the user interface 320.

[0236] Understandable, Figures 3A-3C This example illustrates the use of electronic devices to create a Do Not Disturb mode and a sleep mode by default, as well as a learning mode based on user operation. In this embodiment, electronic devices may also create other scenario modes by default or based on user operation, without limitation.

[0237] The following section uses the first scenario mode as an example to introduce the relevant user interface for viewing and modifying the configuration information of the first scenario mode.

[0238] refer to Figure 3C (a) User interface 330 is a user interface used to display configuration information for the learning mode. After the learning mode is created, the electronic device can immediately display user interface 330, or it can enter the user interface 310 of the scenario mode application from the settings application and then switch to display user interface 330. The method of displaying user interface 330 is not limited. It is understood that the configuration information of the learning mode presented by user interface 330 is based on the above. Figure 1A The method shown is used to obtain the result.

[0239] In one alternative approach, the electronic device can also... Figure 3CUser interface 260 in (b) allows viewing and modifying the configuration information for the children's mode. For details, please refer to the section on viewing and modifying the configuration information for the learning mode; it will not be elaborated here. User interface 330 includes: option box 331 and option box 332.

[0240] Option box 331 indicates the activation conditions in the configuration information of the learning mode.

[0241] For example, option box 331 includes condition 331A and condition 331B. For instance, conditions 331A and 331B are time-based activation conditions. Condition 331A contains the text "8:00 AM - 12:00 PM on weekdays," and condition 331B contains the text "2:00 PM - 6:00 PM on weekdays." This indicates that the electronic device can automatically activate learning mode during the time periods "8:00 AM - 12:00 PM on weekdays" and "2:00 PM - 6:00 PM on weekdays," and automatically deactivate learning mode during other time periods. Condition 331A also includes text 331A1. Text 331A1 is used to indicate whether condition 331A is active or inactive. For example, in user interface 330, text 331A1 displays "Activated," indicating that condition 331A is active. If text 331A1 displays "Off", it indicates that condition 331A is invalid. When an activation condition is invalid, the electronic device will not activate or deactivate the corresponding scenario mode based on that activation condition. Similarly, condition 331B1 also includes text 331B1. Text 331B1 is used to indicate whether condition 331B is active or inactive.

[0242] In this embodiment, the conditions included in the option box 331 are merely illustrative and not intended to limit the scope. Option box 331 also includes an add condition control 331C. The electronic device can respond to the operation applied to the add condition control 331C by modifying the configuration information of the learning mode, that is, adding new activation conditions to the configuration information of the learning mode. Specifically, please refer to the following... Figures 4A-4D The user interface will not be described in detail here.

[0243] Option box 332 indicates the allowed contacts for incoming calls and the allowed applications for notifications in the learning mode configuration information. Option box 332 includes: Option 332A and Option 332B.

[0244] Option 332A indicates the applications that are allowed to send notifications. In one possible implementation, option 332A indicates the applications and meta-services that are allowed to send notifications. For example, option 332A contains the text "4 selected", which means that notifications from the 4 selected applications are allowed during the activation of learning mode.

[0245] Option 332B indicates which contacts are allowed to receive calls. For example, option 332B contains the text "Allow only favorite contacts," which means that calls from favorite contacts are allowed while learning mode is enabled.

[0246] Electronic devices can also modify the learning mode configuration information, such as allowed applications for notifications and allowed contacts for incoming calls. See below for details. Figures 3E-3F The user interface will not be described in detail here.

[0247] Optionally, the user interface 330 may also include one or more of the following: cards 333, indicators 334, add mode controls 335, controls 336, and prompt messages 337.

[0248] Card 333 is used to indicate the scenario mode to which the configuration information displayed in the current user interface belongs, such as learning mode. For example, card 333 includes: name 333A, icon 333B, and launch control 333C.

[0249] The electronic device can respond to a click operation on the start control 333C to initiate learning mode. After initiating learning mode, the start control 333C will be replaced by a close control. The electronic device can also respond to a click operation on the close control to deactivate learning mode.

[0250] Indicator 334 is used to indicate the number of created scenario modes and the order in which the scenario mode indicated by the current user interface is arranged among the multiple created scenario modes. For example, indicator 334 indicates that three scenario modes have been created, and the scenario mode to which the configuration information displayed by the current user interface belongs is the third scenario mode among the multiple created scenario modes.

[0251] The Add Mode control 335 is used to create new scene modes. Electronic devices can respond to clicks on the Add Mode control 335 to create new scene modes. The specific process for creating a new scene mode can be found above. Figures 2A to 2E The user interface shown will not be described in detail here.

[0252] Control 336 is used to set whether to allow the configuration information of created scenarios to be sent to other electronic devices. Electronic devices can respond to click operations on control 336 and choose whether to allow the configuration information of created scenarios to be synchronously sent to other electronic devices logged into the same account as the electronic device.

[0253] The prompt message 337 is used to indicate the function of the scenario mode. For example, prompt message 337 includes the text "Adjust system functions, fully immerse yourself in the scenario, and improve focus." The prompt message 337 is not limited to the text content described above; it may also include other text content, and there is no limitation thereto.

[0254] In the embodiments of this application, the optional content included in the user interface 330 is only for illustrative purposes and is not intended to limit the scope of the application.

[0255] In addition to the partial configuration information of the learning mode displayed in user interface 330, users can also view other additional configuration information for the learning mode. For example, the electronic device can display [the information] in response to an upward swipe operation on user interface 330. Figure 3D The user interface 340 shown is also a user interface used to display configuration information for the learning mode.

[0256] The user interface 340 includes not only option boxes 331 and 332, but also option box 341, smart experience control 342, and delete control 343.

[0257] Option box 341 includes the association between the learning mode and other various modes. For example, option box 341 includes: option 341A, option 341B, and option 341C.

[0258] Option 341A indicates the association between Learning Mode and Dark Mode. Option 341B indicates the association between Learning Mode and Eye Comfort Mode. Option 341C indicates the association between Learning Mode and Power Saving Mode. In user interface 340, Option 341A displays the text "Not Associated," indicating that the activation of Learning Mode is unrelated to the activation of Dark Mode. Option 341B displays the text "Associated," indicating that the activation of Learning Mode is related to the activation of Eye Comfort Mode. Option 341C displays the text "Not Associated," indicating that the activation of Learning Mode is unrelated to the activation of Power Saving Mode.

[0259] The smart experience control 342 is used to turn the smart experience on or off. In the user interface 340, the smart experience control 342 is in the off state.

[0260] The delete control 343 is used to delete the learning mode. The electronic device can delete the learning mode in response to a click operation on the delete control 343.

[0261] In the embodiments of this application, the user interface 330 and user interface 340 described above are only illustrative examples. The user interface for displaying configuration information may also include more or less content, and there is no limitation thereto.

[0262] Figure 3E An example is shown of an electronic device's user interface for viewing and modifying allowed notifications.

[0263] Electronic devices can act on Figure 3E The user interface 340 shown in (a) allows you to click on option 332A to view the allowed notifications in the learning mode configuration information and display the settings. Figure 3E User interface 350 is shown in (b).

[0264] User interface 350 is used to view and edit applications that allow notifications. User interface 350 includes a search box 351, a completion control 352, a close control 353, and the application selection status. The search box 351 is used to search for applications installed on the electronic device. The completion control 352 is used to save the application and meta-service selection status. The close control 353 is used to cancel the current changes to the application and meta-service selection status.

[0265] In user interface 350, application option 354 is selected, and user interface 350 displays the selected applications. Optionally, the electronic device can respond to a click operation on meta-service option 355, displaying the selected meta-services.

[0266] The electronic device can respond to an up or down swipe operation on the user interface 350 to view the selection status of more applications. A selection prompt message, such as "Selected (4)", indicates that the number of applications allowed to send notifications is 4. That is, the applications allowed to send notifications include: application B, application E, application G, and application H. It is understood that the aforementioned applications B, E, G, and H can be accessed through the above... Figure 1A The method determined in S102 is one, two, or three.

[0267] The electronic device can also modify the application that allows notifications in the user interface 350.

[0268] For example, an electronic device can receive a click operation on the checkbox 356 corresponding to application B, deselecting application B, and then receive a click operation on the checkbox 357 corresponding to application C, selecting application C. At this time, applications C, E, G, and H are selected. Then, the electronic device responds to a click operation on the completion control 352, saving the modified application selection status. That is, the modified applications that allow notifications include: applications C, E, G, and H.

[0269] Figure 3F An example is shown of an electronic device's user interface for viewing and modifying allowed contacts for incoming calls.

[0270] Electronic devices can act on Figure 3F The click operation of option 332B on user interface 340 shown in (a) allows viewing the allowed contacts in the learning mode configuration information and displaying... Figure 3F The user interface shown in (b) is 360.

[0271] User interface 360 ​​is used to view and edit allowed contacts. User interface 360 ​​includes options 361, 362, 363, 364, 365, 366, and control 367. For example, option 361 includes the text "Block all," option 362 includes the text "Allow all," option 363 includes the text "Allow only existing contacts," option 364 includes the text "Allow only favorited contacts," option 365 includes the text "Allow only specified contacts," and option 366 includes "Block only specified contacts." Control 367 is used to add or delete specific contacts within a specified contact list.

[0272] In user interface 360, option 364 is selected, which means that incoming calls can be made to contacts who are set as favorite contacts.

[0273] It is understandable that the above-mentioned allowed contacts are based on the above. Figure 1A The contact A2 is determined by method one, method two, or method three in S102. For example, if the contact A2 determined based on any of the methods for determining the configuration information of the first scenario mode described in S102 happens to be a favorite contact, then the electronic device can display option 364 as selected in the user interface 360.

[0274] Optionally, if the determined contact A2 is neither a favorite contact nor an existing contact, the electronic device can display option 365 as selected and designate contact A2 as the contact. In this embodiment, the way the user interface 360 ​​presents the contacts allowed to call is only illustrative. The user interface 360 ​​can also present the contacts allowed to call in other ways, such as displaying the contacts and their checkmark status, without limitation.

[0275] The electronic device can modify the allowed contacts for incoming calls within user interface 360. For example, the electronic device can receive a click action on option 362 to change the allowed contacts to all contacts. As another example, the electronic device can also change the allowed contacts via control 367 when option 365 is selected. Specifically, the electronic device can respond to a click action on control 367 by displaying a user interface showcasing the specified contacts. Specific contacts can be added or deleted within this user interface.

[0276] Optionally, the user interface 360 ​​also includes controls 368 and 369. Control 368 is used to turn the repeat call ringing function on or off. Control 369 is used to turn the smart call answering function on or off. In the user interface 360, controls 368 and 369 are in an on state, which indicates that repeat calls are allowed and smart call answering is enabled. The electronic device can also modify the settings regarding repeat call response and smart call answering functions in response to user actions. For example, the electronic device turns off the repeat call ringing function in response to a click action on control 368.

[0277] It is understandable that the above settings of allowing repeated calls and allowing smart call answering are based on the preset configuration information of the learning mode, such as those determined in Tables 1-1 and 1-2 above.

[0278] Figure 4A An exemplary embodiment of this application provides a user interface for adding activation conditions to an electronic device.

[0279] Electronic device response to Figure 3D The click operation of the add condition control 331C in the user interface 340 shown displays... Figure 4A User interface 410 is shown in (a). User interface 410 is used to select the dimension of the added activation condition. User interface 410 includes options 411, 412, and 413. Option 411 is used to add an activation condition for the time dimension. Option 412 is used to add an activation condition for the application dimension. Option 413 is used to add an activation condition for the location dimension. For example, option 411 includes the text content "Timed", option 412 includes the text content "When application is started", and option 413 includes the text content "When near location".

[0280] The electronic device responds to the click action of option 411, selects the condition for adding a time dimension, and displays it. Figure 4A User interface 420 is shown in (b). User interface 420 is used to set the activation conditions for the time dimension. User interface 420 includes options 421, 422, and 423. Option 421 is used to set the frequency of the activation condition, option 422 is used to set the start time of the activation condition, and option 423 is used to set the end time of the activation condition. The contents of options 421, 422, and 423 displayed in user interface 420 can be the default settings.

[0281] The electronic device can respond to operations applied to options 421, 422, and 423, adjusting the frequency, start time, and end time of the activation conditions and displaying them. Figure 4AUser interface 430 is shown in (c). User interface 430 also includes options 431, 432, and 433. Option 431 is used to set the frequency, option 432 is used to set the start time, and option 433 is used to set the end time. In user interface 430, the frequency of the activation condition is "weekdays", the start time of the activation condition is "7:00 PM", and the end time of the activation condition is "10:00 PM".

[0282] The electronic device responds to a click operation on the control 434 in the user interface 430, saves the activation conditions in the time dimension, and displays... Figure 4A User interface 440 is shown in (d). Similarly, user interface 440 is a user interface used to display configuration information for the learning mode. User interface 440 includes condition 441 and add condition control 442. Compared with the content shown in user interface 330 above, the configuration information displayed in user interface 440 adds a new condition 441 "7:00 PM to 10:00 PM on weekdays", that is, the electronic device adds a time-dimensional activation condition to the configuration information of the learning mode.

[0283] Figure 4B An exemplary embodiment of this application illustrates another user interface for adding activation conditions to an electronic device.

[0284] Electronic device response to Figure 4A The click operation of the add condition control 442 in the user interface 440 shown in (d) displays Figure 4B User interface 450 is shown in (a). User interface 410 is used to select the dimension of the added activation condition. User interface 450 includes options 451, 452, and 453. For descriptions of options 451, 452, and 453, please refer to the descriptions of options 411, 412, and 413 above, which will not be repeated here.

[0285] The electronic device responds to the click action of option 452, selects the conditions for adding application dimensions, and displays them. Figure 4B User interface 460 is shown in (b). User interface 460 is used to set the conditions for enabling application dimensions. User interface 460 includes a search box 461, a completion control 462, a close control 463, and the application selection status. The search box 461 is used to search for applications installed on the electronic device. The completion control 462 is used to save the application selection status. The close control 463 is used to cancel the current modification of the application selection status. In user interface 460, no application corresponding check control is selected, which indicates that the current learning mode configuration information does not include the conditions for enabling application dimensions.

[0286] The user interface 460 also includes a checkbox 464 corresponding to the application G. The electronic device can respond to a click operation on the checkbox 464, selecting the application G and displaying it. Figure 4B User interface 470 is shown in (c). User interface 470 is also used to set the activation conditions for the application dimension. In user interface 470, the checkbox corresponding to application G is selected.

[0287] The electronic device responds to the click operation of the control 471 in the user interface 470, saves the opening conditions of the application dimension, and displays it. Figure 4B User interface 480 is shown in (d). Similarly, user interface 480 is a user interface used to display configuration information for the learning mode. User interface 480 includes condition 481 and an add-condition control 482. Compared to the content shown in user interface 440 above, the configuration information displayed in user interface 480 adds a new condition 481, "when an application is running." In other words, the electronic device adds an application-level activation condition to the configuration information of the learning mode. Condition 481 can be understood as: when the electronic device runs application G, the learning mode can be automatically activated; when the electronic device stops running application G, the learning mode can be automatically deactivated.

[0288] Figure 4C An exemplary embodiment of the present application provides a user interface for adding activation conditions to an electronic device.

[0289] Electronic device response to Figure 4B The click operation of the add condition control 482 in the user interface 480 shown in (d) displays Figure 4C User interface 490 is shown in (a). User interface 410 is used to select the dimension of the added activation condition. User interface 490 includes options 491, 492, and 493. For descriptions of options 491, 492, and 493, please refer to the descriptions of options 411, 412, and 413 above, which will not be repeated here.

[0290] The electronic device responds to the click action of option 493, selecting the conditions for adding the location dimension and displaying them. Figure 4C User interface 510 is shown in (b). User interface 510 is used to set the conditions for enabling the location dimension. User interface 510 includes a search box 511, a completion control 512, and a close control 513. The search box 511 is used to search for locations. The completion control 512 is used to save the conditions for enabling the location dimension. The close control 513 is used to cancel the conditions set in this instance. In user interface 510, the selected location is "AA Province AA City AA District AA Street AAA Community". Optionally, the electronic device can also receive other locations entered in the search box 511 and select other locations.

[0291] The electronic device responds to the click operation of the control 512 in the user interface 510, saves the activation conditions of the location dimension, and displays it. Figure 4C User interface 520 is shown in (c). Similarly, user interface 520 is a user interface used to display configuration information for the learning mode. User interface 520 includes conditions 521, 522, and 523. Compared to the content shown in user interface 480 above, the configuration information displayed in user interface 520 includes an additional condition 523, "when a location is nearby." In other words, the electronic device adds a location-based activation condition to the learning mode configuration information. Condition 523 can be understood as follows: when the electronic device is near the location "AA Province AA City AA District AA Street AAA Community," the learning mode can be automatically activated; when the electronic device is far from the location "AA Province AA City AA District AA Street AAA Community," the learning mode can be automatically deactivated. For example, "near a location" could mean the electronic device is within 300 meters of the location, and "far from a location" could mean the electronic device is not within 300 meters of the location.

[0292] Figures 4D-4F The present application provides exemplary user interfaces for modifying and deleting activation conditions in several electronic devices.

[0293] Electronic device response to Figure 4C The click operation of condition 521 in the user interface 520 shown in (c) displays Figure 4D The user interface 560 is shown. User interface 560 is used to edit condition 521. User interface 560 includes: control 561, completion control 562, close control 563, delete control 564, option 565, option 566, and option 567. Control 561 is used to enable or disable condition 521. In user interface 560, control 561 is in an "on" state, indicating that condition 521 is enabled. The electronic device can disable condition 521 by clicking control 561.

[0294] The electronic device can modify condition 521 using options 565, 566, and 567. Descriptions of options 565, 566, and 567 can be found in the descriptions of options 421, 422, and 423 above, and will not be repeated here. The completion control 562 saves condition 521. The close control 563 cancels the current modification to condition 521. The electronic device can delete condition 521 in response to a click operation on the delete control 564.

[0295] Electronic device response to Figure 4C The click operation of condition 522 in the user interface 520 shown in (c) displays Figure 4E The user interface 570 is shown. User interface 570 is used to edit condition 522. User interface 570 includes: control 571, completion control 572, close control 573, delete control 574, and application checkbox. Control 571 is used to enable or disable condition 522. In user interface 570, control 571 is in an "on" state, indicating that condition 522 is enabled. A click operation on control 571 can disable condition 522. The electronic device can modify condition 522 by changing the application checkbox. Completion control 572 is used to save condition 522. Close control 573 is used to cancel the current modification to condition 522. The electronic device can delete condition 522 in response to a click operation on delete control 574.

[0296] Electronic device response to Figure 4C The click operation of condition 523 in the user interface 520 shown in (c) displays Figure 4F The user interface 530 shown is used to edit condition 523. User interface 530 includes: a control 531, a search box 532, a completion control 533, a close control 534, and a delete control 535. Control 531 is used to enable or disable condition 523. In user interface 530, control 531 is in an "on" state, indicating that condition 523 is enabled. A click operation on control 531 can disable condition 521. The search box 532 is used to modify the location information in condition 521. The completion control 533 is used to save condition 523. The close control 534 is used to cancel the current modification to condition 523. The electronic device can delete condition 523 in response to a click operation on delete control 535.

[0297] Figure 4G An exemplary embodiment of this application provides a user interface for modifying the associated system functions of an electronic device.

[0298] Electronic device response to Figure 4G The click operation of option 341A of the user interface 340 shown in (a) displays Figure 4G User interface 540 is shown in (b). User interface 540 is used to modify the association between learning mode and dark mode in the configuration information. User interface 540 includes options 541 and 542. Option 541 is used to change the association between learning mode and dark mode to non-association. Option 542 is used to change the association between learning mode and dark mode to association. The electronic device can respond to the user's click operation on option 542 to set the association between learning mode and dark mode to association.

[0299] Figure 5An exemplary embodiment of the present application illustrates a user interface for deleting a scenario mode on an electronic device.

[0300] Electronic device response to Figure 5 (a) shows the user interface 330 where the card 333 can be operated upwards, downwards, or long-pressed, displaying... Figure 5 User interface 550 is shown in (b). User interface 550 is similar to user interface 330, except that card 551 in user interface 550 contains a delete control 551A. The electronic device can delete the learning mode in response to a click operation on the delete control 551A.

[0301] In the embodiments of this application, the content included in each of the above-mentioned user interfaces is only illustrative and may include more or less content. The electronic device can implement the corresponding functions in each of the above-mentioned user interfaces, such as viewing configuration information, modifying configuration information, etc., and there is no limitation thereto.

[0302] Since the configuration information for different scenario modes contains the same information type, the content of the information may differ. For user interfaces related to viewing and modifying the configuration information for other scenario modes, please refer to the categories described above. Figures 3C-5 The user interface is not described in detail here.

[0303] In some implementations, after an electronic device creates a first scenario mode, it can delete the first scenario mode. The electronic device can then recreate the first scenario mode. Specifically, after triggering the recreation of the first scenario mode, the electronic device can determine the configuration information E of the first scenario mode. This configuration information E is determined based on the operating data of the electronic device while in the first scenario mode. The operating data of the electronic device while in the first scenario mode can be determined based on the time periods when the electronic device turns the first scenario mode on and off, and then the electronic device obtains the operating data within the time period of the first scenario mode.

[0304] Optionally, the configuration information E is determined based on the operating data of the electronic device in the first scenario mode and the historical data F. The historical data F includes the operating data of the electronic device when it was in the first scenario but not in the first scenario mode before receiving the operation to recreate the first scenario mode. Similarly, the specific determination method can refer to methods one to three shown in S102 above, and will not be elaborated here.

[0305] It is understandable that the configuration information of the first scenario mode after re-creation may be the same as or different from the configuration information of the first scenario mode created previously.

[0306] Figure 6 An exemplary flowchart of a method for creating a scenario pattern provided in an embodiment of this application is shown.

[0307] The method includes:

[0308] S701. Obtain first historical data related to the first scenario. The first historical data includes the operating data of the electronic device in the first scenario.

[0309] S702. Determine at least one configuration information of a first scenario mode of an electronic device, wherein the at least one configuration information of the first scenario mode includes first configuration information, the first configuration information indicating a first function of the electronic device in the first scenario mode, and the first configuration information is determined based on first historical data.

[0310] S703, Display the first configuration information.

[0311] The aforementioned first configuration information may include the following: the activation condition A1 for the first scenario mode, the contacts allowed to receive calls A2, and the applications allowed to send notifications A3. For details, please refer to the relevant description in S102 above, which will not be repeated here.

[0312] In one possible implementation, before executing S703, the electronic device may also receive and respond to an operation to create a first scenario mode. In some implementations, the electronic device may receive a user operation that triggers the creation of the first scenario mode. The aforementioned user operation may include one or more of the following: touch operation, click operation, gesture operation, voice operation, and eye-tracking operation.

[0313] In one possible implementation, at least one configuration information further includes second configuration information, and the electronic device may also display the second configuration information, which indicates a second function of the electronic device in a first scenario mode, and the second configuration information is determined based on first historical data.

[0314] In one possible implementation, the electronic device may also enable a first scenario mode, and the electronic device sets corresponding functions based on at least one configuration information of the first scenario mode.

[0315] In one possible implementation, the first configuration information is determined based on first preset configuration information and first historical data. The first preset configuration information indicates a preset function of the electronic device in a first scenario mode. For specific details, refer to the methods for obtaining the configuration information of the first scenario mode shown in S102 above.

[0316] In one possible implementation, the electronic device acquiring the first historical data related to the first scenario specifically includes: the electronic device determining the application related to the first scenario based on the application type; and the electronic device acquiring the first historical data related to the first scenario based on the runtime data of the application related to the first scenario.

[0317] In one possible implementation, the runtime data of the application related to the first scenario includes the first application. Based on the runtime data of the application related to the first scenario, obtaining the first historical data related to the first scenario specifically includes: obtaining the first time period in which the first application runs; obtaining one or more of the following within the first time period: incoming call information, notification information, and location information.

[0318] In one possible implementation, the first configuration information is used to indicate the application that allows the first scenario mode to output notifications. Determining at least one configuration information of the first scenario mode of the electronic device includes: determining the first configuration information based on notification messages acquired within a first time period. The first configuration information includes a second application.

[0319] In one possible implementation, the first notification message includes: the number of times a notification from the second application has been opened exceeds a first threshold.

[0320] In one possible implementation, the first configuration information is used to indicate the contacts that the first scenario mode allows to receive calls. Determining at least one configuration information of the first scenario mode of the electronic device includes: determining the first configuration information based on incoming call information obtained within a first time period, wherein the configuration information includes the first contact.

[0321] In one possible implementation, the first incoming call information includes: the number of calls from the first contact exceeds a second threshold, and / or, the duration of the calls from the first contact exceeds a third threshold.

[0322] In one possible implementation, the first configuration information is used to indicate that a first scenario mode is activated when a first condition is met. The first configuration information for determining the first scenario mode of the electronic device includes: determining the first configuration information based on a first time period and / or a first location.

[0323] In one possible implementation, the first condition includes: being within a first time period and / or within a first location, where the first location information includes: the duration of being within the first location exceeds a fourth threshold.

[0324] In one possible implementation, the electronic device may also update the first configuration information based on the operating data of the electronic device in the first scenario mode, and / or update the first configuration information according to the user's modification of the first configuration information.

[0325] In one possible implementation, after executing S703, the electronic device may further receive and respond to an operation to create a second scenario mode, displaying first configuration information, wherein the second scenario mode is related to the first scenario mode. For example, the second scenario mode may be a custom scenario mode that is most similar to the first scenario mode.

[0326] In one possible implementation, after executing S703, the electronic device may further delete the created first scenario mode. The electronic device may also receive an operation to create a third scenario mode, which is related to the first scenario mode. For example, the third scenario mode may be a custom scenario mode that has the greatest similarity to the first scenario mode. At least one configuration piece of information for the third scenario mode is determined, based on the operating data of the electronic device in the first scenario mode, and / or the configuration information of the first scenario mode.

[0327] In one possible implementation, after executing S703, the electronic device can also acquire second historical data related to the second scenario, the second historical data including the operating data of the electronic device in the second scenario; determine at least one configuration information corresponding to the fourth scenario mode of the electronic device, the at least one configuration information of the fourth scenario mode including third configuration information, the third configuration information indicating the first function of the electronic device in the fourth scenario mode, the third configuration information being determined based on the second historical data; and display the third configuration information, wherein the second scenario mode is different from the first scenario mode, and the first configuration information is different from the third configuration information.

[0328] about Figure 6 The method flow shown can be referred to the above-mentioned procedures. Figure 1A and Figure 1B Detailed explanation.

[0329] Implementation Figure 6 The illustrated process allows for the setting of different scenario modes for various situations, eliminating the need for users to manually configure information when creating each scenario mode. This reduces user steps and avoids a complex experience during scenario mode creation. Furthermore, the configuration information can be determined based on the user's electronic device usage habits, resulting in scenario modes that are more tailored to the user and provide a better user experience.

[0330] The internal functional modules of the electronic device provided in the embodiments of this application are described below.

[0331] For example, Figure 7 A schematic diagram of the internal modules of an electronic device provided in an embodiment of this application is shown.

[0332] refer to Figure 7The functional modules of the electronic device may include a scenario mode UI 610, a management module 620, and a database 630. Among them, the scenario mode application is located at the application layer, and the scenario mode UI 610 is located in the scenario mode application, used to display the scenario mode configuration information and receive various user operations.

[0333] The management module 620, located in the application framework layer or service layer, manages the configuration information for various scenario modes, such as generating, deleting, and updating configuration information. The management module 620 can also interact with functional modules of other system apps, enabling electronic devices to configure corresponding functions according to the configuration information of a specific scenario mode when that mode is enabled.

[0334] Database 630 resides in the application framework layer or service layer and is used to store configuration information for various scenario modes. Database 630 can also be used to retrieve various historical data from other applications in the application layer. Database 630 can also be used to update configuration information based on instructions sent by the management module 620. Database 630 can also be used to store preset configuration information for various preset scenario modes. Optionally, database 630 can also be used to store historical data.

[0335] For example, after the scenario mode UI 610 receives the user's operation to create a first scenario mode, it can send the message to the management module 620. The management module 620 determines the configuration information of the first scenario mode and completes the creation of the first scenario mode. The specific determination method can refer to methods one to three shown in S102 above, and will not be elaborated here. The management module 620 sends an instruction to the database 630, instructing the database 630 to store the configuration information of the first scenario mode. The scenario mode UI 610 is also used to read the configuration information of the first scenario mode stored in the database 630 and display all or part of the configuration information of the first scenario mode.

[0336] After the scenario mode UI 610 receives an operation from the user to modify the configuration information of the first scenario mode, it sends the message indicating the modification to the configuration information to the management module 620. The management module 620 determines the modified configuration information of the first scenario mode based on the user's operation. The management module 620 sends an instruction to the database 630, instructing the database 630 to store the modified configuration information of the first scenario mode. The scenario mode UI 610 also reads the modified configuration information of the first scenario mode stored in the database 630 and displays all or part of the modified configuration information.

[0337] After the scenario mode UI 610 receives the user's operation to delete the first scenario mode, it sends the message of deleting the first scenario mode to the management module 620. The management module 620 then sends an instruction to the database 630, instructing the database 630 to delete all configuration information for the first scenario mode.

[0338] After creating the first scenario mode, the management module 620 is also used to update the configuration information of the first scenario mode based on the operating data of the electronic device in the first scenario mode. The management module 620 is used to send instructions to the database 630, instructing the database 630 to store the updated configuration information of the first scenario mode. The scenario mode UI 610 is also used to read the updated configuration information of the first scenario mode stored in the database 630 and display all or part of the updated configuration information of the first scenario mode.

[0339] In the embodiments of this application, Figure 7 The functional modules shown are for illustrative purposes only, and may include more or fewer other modules, without limitation.

[0340] Figure 8 An exemplary schematic diagram of the hardware structure of electronic device 100 is shown.

[0341] The following description uses electronic device 100 as an example to illustrate the embodiment. It should be understood that... Figure 8 The electronic device 100 shown is merely an example, and the electronic device 100 may have more than Figure 7 The more or fewer components shown can be combined into two or more components, or they can have different component configurations. The various components shown in the figure can be implemented in hardware, software, or a combination of hardware and software, including one or more signal processing and / or application-specific integrated circuits.

[0342] For example, electronic device 100 may be a mobile phone, tablet computer, desktop computer, laptop computer, handheld computer, notebook computer, ultra-mobile personal computer (UMPC), netbook, as well as cellular phone, personal digital assistant (PDA), augmented reality (AR) device, virtual reality (VR) device, artificial intelligence (AI) device, wearable device, in-vehicle device, smart home device and / or smart city device. This application embodiment does not impose any special restrictions on the specific type of electronic device 100.

[0343] 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, audio module 170, speaker 170A, receiver 170B, microphone 170C, headphone jack 170D, sensor module 180, button 190, motor 191, indicator 192, camera 193, display screen 194, and subscriber identification module (SIM) card interface 195, etc. The sensor module 180 may include a pressure sensor 180A, a gyroscope sensor 180B, a barometric pressure sensor 180C, a magnetic sensor 180D, an accelerometer sensor 180E, a distance sensor 180F, a proximity sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, an ambient light sensor 180L, a bone conduction sensor 180M, etc.

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

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

[0346] In this embodiment, processor 110 is used to execute the method for creating a scenario mode provided in this application. Specifically, processor 110 is used to acquire historical data. Processor 110 is used to trigger the creation of a first scenario mode. Processor 110 is used to determine the scenario related to the scenario mode as the first scenario. Processor 110 is used to extract first historical data related to the first scenario from the historical data. Processor 110 is used to determine the time when the M-type application is started and stopped, so as to determine the time period M1 during which the M-type application is running, that is, the electronic device is in the first scenario during the time period M1. Processor 110 is used to base on Figure 1A The three methods mentioned in S102 determine the configuration information of the first scenario mode corresponding to the first scenario mode. The processor 110 is also used to modify the configuration information of the first scenario mode. The processor 110 is also used to update the configuration information of the first scenario mode based on the running data in the first scenario mode. After starting the first scenario mode, the processor 110 is also used to set the corresponding functions based on the configuration information of the first scenario mode.

[0347] The controller can be the nerve center and command center of the electronic device 100. The controller can generate operation control signals according to the instruction opcode and timing signals to complete the control of fetching and executing instructions.

[0348] The processor 110 may also include a memory for storing instructions and data. In some embodiments, the memory in the processor 110 is a cache memory. This memory can store instructions or data that the processor 110 has just used or that are used repeatedly. If the processor 110 needs to use the instruction or data again, it can directly retrieve it from the memory. This avoids repeated accesses, reduces the waiting time of the processor 110, and thus improves the efficiency of the system. In some embodiments, the processor 110 may include one or more interfaces. Interfaces may include an inter-integrated circuit (I2C) interface, an inter-integrated circuit sound (I2S) interface, a pulse code modulation (PCM) interface, a universal asynchronous receiver / transmitter (UART) interface, a mobile industry processor interface (MIPI), a general-purpose input / output (GPIO) interface, a subscriber identity module (SIM) interface, and / or a universal serial bus (USB) interface, etc.

[0349] The charging management module 140 is used to receive charging input from the charger. The charger can be a wireless charger or a wired charger.

[0350] 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 to power the processor 110, internal memory 121, external memory, display 194, camera 193, and wireless communication module 160, etc.

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

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

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

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

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

[0356] 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, enabling electronic device 100 to communicate with networks and other devices via wireless communication technology. The wireless communication technology may include Global System for Mobile Communications (GSM), General Packet Radio Service (GPRS), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), Time-Division Code Division Multiple Access (TD-CDMA), Long Term Evolution (LTE), BT, GNSS, WLAN, NFC, FM, and / or IR technologies, etc. The GNSS may include the Global Positioning System (GPS), the Global Navigation Satellite System (GLONASS), the BeiDou Navigation Satellite System (BDS), the Quasi-Zenith Satellite System (QZSS), and / or satellite-based augmentation systems (SBAS).

[0357] In this embodiment, the mobile communication module 150 or the wireless communication module 160 is also used to receive historical data sent by other electronic devices or servers, and to send configuration information of the created scenario mode to other electronic devices.

[0358] Electronic device 100 implements display functions through a GPU, a display screen 194, and an application processor. The GPU is a microprocessor for image processing, connected to the display screen 194 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.

[0359] Display screen 194 is used to display images, videos, etc. Display screen 194 includes a display panel. The display panel can be a liquid crystal display (LCD). The display panel can also be manufactured using organic light-emitting diodes (OLEDs), active-matrix organic light-emitting diodes (AMOLEDs), flexible light-emitting diodes (FLEDs), miniled, microled, micro-OLEDs, quantum dot light-emitting diodes (QLEDs), etc. In some embodiments, electronic device 100 may include one or N displays 194, where N is a positive integer greater than 1.

[0360] In this embodiment, the display screen 194 is used to display the user interface related to the scenario mode provided in this application, such as those described above. Figures 2A-5 The user interface shown.

[0361] Electronic device 100 can perform shooting functions through ISP, camera 193, video codec, GPU, display 194 and application processor.

[0362] The ISP (Image Signal Processor) is used to process data fed back from the camera 193. For example, when taking a picture, the shutter is opened, and light is transmitted through the lens to the camera's photosensitive element. The light signal is converted into an electrical signal, and the camera's photosensitive element transmits the electrical signal to the ISP for processing, transforming it into an image visible to the naked eye. The ISP can also perform algorithmic optimizations on image noise, brightness, etc. The ISP can also optimize parameters such as exposure and color temperature of the shooting scene. In some embodiments, the ISP can be set in the camera 193.

[0363] Camera 193 is used to capture still images or videos. An object is projected onto a photosensitive element by generating an optical image through the lens. The photosensitive element can be a charge-coupled device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor. The photosensitive element converts the light signal into an electrical signal, which is then passed to an ISP for conversion into a digital image signal. The ISP outputs the digital image signal to a DSP for processing. The DSP converts the digital image signal into image signals in standard RGB, YUV, or other formats. In some embodiments, the electronic device 100 may include one or N cameras 193, where N is a positive integer greater than 1.

[0364] Digital signal processors (DSPs) are used to process digital signals. Besides digital image signals, they can also process other digital signals. For example, when electronic device 100 selects a frequency, the DSP can perform Fourier transforms on the frequency energy.

[0365] Video codecs are used to compress or decompress digital video. Electronic device 100 may support one or more video codecs. Thus, electronic device 100 can play or record videos in various encoding formats, such as Moving Picture Experts Group (MPEG) 1, MPEG2, MPEG3, MPEG4, etc.

[0366] An NPU (Neural Processing Unit) is a computational processor for neural networks (NNs). By borrowing the structure of biological neural networks, such as the transmission patterns between neurons in the human brain, it can rapidly process input information and continuously learn on its own. NPUs enable intelligent cognitive applications in electronic devices, such as image recognition, facial recognition, speech recognition, and text understanding.

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

[0368] 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, etc.), etc. The data storage area may store data created during the use of electronic device 100 (such as audio data, phonebook, etc.). Furthermore, internal memory 121 may include high-speed random access memory and may also include non-volatile memory, such as at least one disk storage device, flash memory device, universal flash storage (UFS), etc.

[0369] In this embodiment, the memory can be used to store preset configuration information for various preset scenario modes, such as Tables 1-1 and 1-2 above. The memory is also used to store historical data. Furthermore, the memory is used to store configuration information for created scenario modes.

[0370] Electronic device 100 can implement audio functions, such as music playback and recording, through audio module 170, speaker 170A, receiver 170B, microphone 170C, headphone jack 170D, and application processor.

[0371] In this embodiment of the application, the audio module 170 is used to output the notification of application A3 in the form of an audio signal and the incoming call of contact A2 in the form of an audio signal after the first scene mode is started.

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

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

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

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

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

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

[0378] The gyroscope sensor 180B can be used to determine the motion attitude of the electronic device 100. In some embodiments, the gyroscope sensor 180B can determine the angular velocity of the electronic device 100 about three axes (i.e., the x, y, and z axes). The gyroscope sensor 180B can be used for image stabilization. For example, when the shutter is pressed, the gyroscope sensor 180B detects the angle of the shake of the electronic device 100, calculates the distance that the lens module needs to compensate based on the angle, and allows the lens to counteract the shake of the electronic device 100 by moving in the opposite direction, thus achieving image stabilization. The gyroscope sensor 180B can also be used in navigation and motion-sensing game scenarios.

[0379] In this embodiment of the application, the gyroscope is used as sensor 180B to determine the position of the electronic device.

[0380] The barometric pressure sensor 180C is used to measure air pressure. In some embodiments, the electronic device 100 calculates altitude using the air pressure value measured by the barometric pressure sensor 180C to assist in positioning and navigation.

[0381] The magnetic sensor 180D includes a Hall sensor. The electronic device 100 can use the magnetic sensor 180D to detect the opening and closing of the flip cover. In some embodiments, when the electronic device 100 is a flip phone, the electronic device 100 can detect the opening and closing of the flip cover using the magnetic sensor 180D. Then, based on the detected opening and closing state of the cover or the flip cover, features such as automatic flip unlocking can be set.

[0382] The 180E accelerometer can detect the magnitude of acceleration of electronic device 100 in various directions (typically three axes). When electronic device 100 is stationary, it can detect the magnitude and direction of gravity. It can also be used to identify the posture of electronic devices and applied to applications such as screen orientation switching and pedometers.

[0383] A distance sensor 180F is used to measure distance. Electronic device 100 can measure distance via infrared or laser. In some embodiments, during a shooting scene, electronic device 100 can utilize the distance sensor 180F to measure distance for rapid focusing.

[0384] The proximity light sensor 180G may include, for example, a light-emitting diode (LED) and a light detector, such as a photodiode. The LED may be an infrared LED. The electronic device 100 emits infrared light outward through the LED.

[0385] The ambient light sensor 180L is used to sense the brightness of ambient light. The electronic device 100 can adaptively adjust the brightness of the display screen 194 based on the sensed ambient light brightness. The ambient light sensor 180L can also be used to automatically adjust the white balance when taking pictures. The ambient light sensor 180L can also work with the proximity sensor 180G to detect whether the electronic device 100 is in a pocket to prevent accidental touches.

[0386] The fingerprint sensor 180H is used to collect fingerprints. The electronic device 100 can utilize the characteristics of the collected fingerprints to achieve fingerprint unlocking, accessing application locks, taking photos with fingerprints, answering calls with fingerprints, etc.

[0387] Temperature sensor 180J is used to detect temperature. In some embodiments, electronic device 100 uses the temperature detected by temperature sensor 180J to execute a temperature handling strategy. For example, when the temperature reported by temperature sensor 180J exceeds a threshold, electronic device 100 performs thermal protection by reducing the performance of a processor located near temperature sensor 180J to reduce power consumption. In other embodiments, when the temperature is below another threshold, electronic device 100 heats battery 142 to prevent abnormal shutdown of electronic device 100 due to low temperature. In still other embodiments, when the temperature is below yet another threshold, electronic device 100 boosts the output voltage of battery 142 to prevent abnormal shutdown due to low temperature.

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

[0389] In this embodiment, the pressure sensor 180A and the touch sensor 180K are used to receive configuration information of the user modifying or deleting the scene mode.

[0390] The bone conduction sensor 180M can acquire vibration signals. In some embodiments, the bone conduction sensor 180M can acquire vibration signals from the vibrating bone segments of the human vocal cords. The bone conduction sensor 180M can also contact the human pulse to receive blood pressure signals. In some embodiments, the bone conduction sensor 180M can also be incorporated into headphones to form bone conduction headphones. The audio module 170 can parse the voice signals from the vibrating bone segments of the vocal cords acquired by the bone conduction sensor 180M to realize voice functionality. The application processor can parse heart rate information from the blood pressure signals acquired by the bone conduction sensor 180M to realize heart rate detection functionality.

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

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

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

[0394] In this embodiment of the application, motor 191 and / or indicator 192 are used to output notifications from application A3 and incoming calls from contact A2 after the first scenario mode is activated.

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

[0396] In this embodiment of the application, the electronic device 100 can use a cellular communication network via a SIM card to receive calls from contact A2 after activating the first scenario mode.

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

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

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

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

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

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

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

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

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

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

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

[0408] In some possible implementations, the basic software service subsystem set may include the aforementioned Figure 7 The management module and database shown.

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

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

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

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

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

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

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

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

[0417] The application layer can include applications in electronic devices, including but not limited to: desktop, profiles, settings, SMS, phone, contacts, etc.

[0418] Electronic devices can implement the method for creating scenario modes provided in the embodiments of this application through the application layer, framework layer, system service layer, and kernel layer.

[0419] This application provides an electronic device, which includes a memory, a processor, and a computer program stored in the memory. The processor executes the computer program to implement the above-described method for creating a scenario mode.

[0420] This application also provides a computer-readable storage medium storing a computer program, which, when executed by a processor, can implement the steps in the above-described method embodiments.

[0421] This application also provides a computer program product, including a computing program, which, when run on a computer, enables the computer to perform the steps in the various method embodiments described above.

[0422] This application also provides a chip system, which includes a processing circuit interface circuit. The interface circuit receives code instructions and transmits them to the processing circuit. The processing circuit executes the code instructions to enable the chip system to implement the steps of any method embodiment of this application. The chip system can be a single chip or a chip module composed of multiple chips.

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

Claims

1. A method for creating scenario patterns, characterized in that, The method is applied to an electronic device, and the method includes: Acquire first historical data related to the first scenario, the first historical data including the operating data of the electronic device in the first scenario; Determine at least one configuration information of a first scenario mode of the electronic device, wherein the at least one configuration information of the first scenario mode includes first configuration information, the first configuration information indicating a first function of the electronic device in the first scenario mode, and the first configuration information is determined based on the first historical data; Display the first configuration information.

2. The method according to claim 1, characterized in that, Before displaying the first configuration information, the method further includes: Receive and respond to the operation of creating the first scenario mode.

3. The method according to claim 1 or 2, characterized in that, The at least one configuration information further includes second configuration information, and the method further includes: The second configuration information is displayed, which indicates the second function of the electronic device in the first scenario mode. The second configuration information is determined based on the first historical data.

4. The method according to any one of claims 1-3, characterized in that, The method further includes: When the first scenario mode is activated, the electronic device sets corresponding functions based on at least one configuration information of the first scenario mode.

5. The method according to any one of claims 1-4, characterized in that, The first configuration information is determined based on the first preset configuration information and the first historical data. The first preset configuration information indicates the first function of the electronic device in the first scenario mode.

6. The method according to any one of claims 1-5, characterized in that, The acquisition of the first historical data related to the first scenario specifically includes: Determine the applications related to the first scenario based on their types; Based on the operational data of the application related to the first scenario, obtain the first historical data related to the first scenario.

7. The method according to claim 6, characterized in that, The runtime data of the application related to the first scenario includes the first application, and the step of obtaining the first historical data related to the first scenario based on the runtime data of the application related to the first scenario specifically includes: Obtain the first time period during which the first application is running; Obtain one or more of the following within the first time period: incoming call information, notification information, and location information.

8. The method according to claim 7, characterized in that, The first configuration information is used to indicate the applications that allow the first scenario mode to output notifications, and the at least one configuration information for determining the first scenario mode of the electronic device includes: The first configuration information is determined based on the notification message obtained within the first time period, and the first configuration information includes the second application.

9. The method according to claim 8, characterized in that, The first notification message includes: the number of times a notification from the second application has been opened exceeds a first threshold.

10. The method according to claim 7, characterized in that, The first configuration information is used to indicate the contacts that the first scenario mode allows to receive calls, and the at least one configuration information for determining the first scenario mode of the electronic device includes: The first configuration information is determined based on the incoming call information obtained within the first time period, and the configuration information includes a first contact person.

11. The method according to claim 10, characterized in that, The first incoming call information includes: the number of calls from the first contact exceeds a second threshold, and / or the duration of the calls from the first contact exceeds a third threshold.

12. The method according to claim 7, characterized in that, The first configuration information is used to indicate that the first scenario mode is activated when a first condition is met, wherein at least one configuration information for determining the first scenario mode of the electronic device includes: The first configuration information is determined based on the first time period and / or the first location information.

13. The method according to claim 12, characterized in that, The first condition includes: being within the first time period and / or within the first location range, wherein the first location information includes: the duration of being within the first location range exceeds a fourth threshold.

14. The method according to any one of claims 1-13, characterized in that, The method further includes: Update the first configuration information based on the operating data of the electronic device in the first scenario mode, and / or, Update the first configuration information based on the user's modifications to the first configuration information.

15. The method according to any one of claims 1-14, characterized in that, After displaying the first configuration information, the method further includes: The electronic device receives and responds to an operation to create a second scenario mode, and displays the first configuration information, wherein the second scenario mode is associated with the first scenario mode.

16. The method according to any one of claims 1-14, characterized in that, After displaying the first configuration information, the method further includes: Delete the first scenario mode that was created; Received an operation to create the third scenario mode, which is related to the first scenario mode; Determine at least one configuration information of the third scenario mode, the at least one configuration information of the third scenario mode being determined based on the operating data of the electronic device in the first scenario mode, and / or the configuration information of the first scenario mode.

17. The method according to any one of claims 1-16, characterized in that, After displaying the first configuration information, the method further includes: Acquire second historical data related to the second scenario, the second historical data including the operating data of the electronic device in the second scenario; Determine at least one configuration information corresponding to a fourth scenario mode of the electronic device, wherein the at least one configuration information of the fourth scenario mode includes third configuration information, wherein the third configuration information indicates the first function of the electronic device in the fourth scenario mode, and the third configuration information is determined based on the second historical data; The third configuration information is displayed, wherein the second scenario mode is different from the first scenario mode, and the first configuration information is different from the third configuration information.

18. An electronic device, characterized in that, The electronic device includes a memory, a processor, and computer instructions stored in the memory, wherein the processor executes the computer program to implement the method of any one of claims 1-17.

19. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, implements the method of any one of claims 1-17.

20. A computer program product, characterized in that, The computer program product includes computer instructions that, when executed by a processor, implement the method of any one of claims 1-17.

Images