Personalized reminding method and electronic equipment

Abstract

The invention provides a personalized reminding method and electronic equipment, and relates to the technical field of electronic equipment, and the method comprises the steps that the electronic equipment responds to an identified target scene, and a first creation instruction is displayed on an interface of the electronic equipment; the target scene is a scene associated with a to-be-reminded item, and the first creation instruction is generated according to the to-be-reminded item; the electronic device creates a first reminding event associated with the target scene in response to a first operation on the first creation instruction; the first reminding event is used for reminding the user to execute the to-be-reminded item associated with the target scene. The method can simplify the process of creating the reminding event by the electronic equipment.

Description

Technical Field

[0001] This application relates to the field of electronic device technology, and more particularly to a personalized reminder method and electronic device. Background Technology

[0002] Currently, when creating personal reminder events such as calendars, alarms, reminders, and shortcuts on electronic devices, the electronic device first needs to respond to the user's operation of opening the application and enter the interface of the various applications. Then, the electronic device can only create the personal reminder event by receiving different operations of the user's reminder settings. The process of creating personal reminder events is relatively cumbersome. Summary of the Invention

[0003] This application provides a personalized reminder method and electronic device to solve the problem that the process of creating personal reminder events is relatively cumbersome.

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

[0005] Firstly, a personalized reminder method is provided, applied to an electronic device. The method includes: the electronic device, in response to recognizing a target scene, displaying a first creation instruction on its interface. The target scene is a scene associated with a reminder item, and the first creation instruction is generated based on the reminder item. The electronic device can, in response to a first operation on the first creation instruction, create a first reminder event associated with the target scene. The first reminder event is used to remind the user to perform the reminder item associated with the target scene.

[0006] By adopting the above technical solution, electronic devices can proactively identify target scenes and display creation instructions, thereby guiding users to create reminder events associated with the target scene. This eliminates the need for electronic devices to respond to user operations and enter the application interface. Instead, reminder events are created step by step by the user through the application interface, simplifying the process of creating reminder events on electronic devices.

[0007] In one possible implementation of the first aspect, the target scenario includes a user browsing the application interface of a first application, the reminder being an item associated with a reservation service provided by the first application, and the application interface of the first application being associated with the browsing interface corresponding to the reservation service. Here, the first application can be a third-party service application.

[0008] Here, the user is browsing the ticket reservation and booking service page associated with the first application. This could mean the user is currently browsing the ticket reservation and booking service page or has already browsed it a while ago.

[0009] Alternatively, the target scenario could be that the user has opened the interface of the first application but hasn't started browsing yet.

[0010] In one possible implementation of the first aspect, in response to the electronic device recognizing the target scene, displaying a first creation instruction on the interface of the electronic device includes: in response to the electronic device recognizing that the user is browsing the application interface of the first application, displaying the first creation instruction on the application interface of the first application.

[0011] In one possible implementation of the first aspect, the application interface displays a global navigation bar control; in response to the electronic device recognizing that the user is browsing the application interface of the first application, a first creation instruction is displayed on the application interface of the first application, including: in response to the electronic device recognizing that the user is browsing the application interface of the first application, flashing the global navigation bar control on the application interface. The flashing of the global navigation bar control can indicate that the mobile phone has recognized that the current user is browsing the application interface of the first application, serving as a prompt to the user whether a reminder event needs to be created. Then, in response to a press operation on the global navigation bar control, the electronic device can display a dialogue input box for the voice assistant on the application interface; the first creation instruction is displayed in the dialogue input box.

[0012] The first creation instruction mentioned above is automatically generated by the mobile phone based on the user's page recognition results. It can be either an interrogative sentence or an affirmative sentence.

[0013] In one possible implementation of the first aspect, the method further includes: displaying at least one first control on the application interface, the first control displaying related recommended words, the related recommended words being words associated with the reminder, the first control being used to trigger the electronic device to jump from the application interface displaying the first application to the interface displaying the related recommended words in response to the user's first selection operation.

[0014] The interface displaying the related recommended terms could be a search application interface, where the related recommended terms are displayed in the search box, allowing users to directly view relevant information about the related recommended terms. Since the related recommended terms are associated with the reminders, it also helps users quickly learn more about the reminders.

[0015] Related recommended words are usually displayed in the area above the voice assistant's dialogue input box.

[0016] A reminder can have multiple related keywords. Not all of them will be displayed on the current page. You can swipe left or right to switch between displaying different related keywords.

[0017] In one possible implementation of the first aspect, the dialog input box includes a send control, which, in response to a first operation on a first creation instruction, creates a first reminder event associated with the target scene, including: the electronic device, in response to a touch operation on the send control, sends a first creation instruction to a voice assistant (also referred to as a voice assistant), triggering the voice assistant of the electronic device to respond to the first creation instruction and create a first reminder event associated with the target scene.

[0018] The first operation here can refer to sending the first creation command in the dialog input box, that is, a touch operation on the send control. The touch operation here can be a single click, double click, press, etc., and there are no restrictions here.

[0019] Therefore, since the creation command is directly displayed in the dialog input box, the phone only needs to respond to the touch operation of the send control to create the reminder event related to the creation command. The steps are relatively simple, which improves the user's experience of creating reminders on electronic devices.

[0020] In one possible implementation of the first aspect, the method further includes: the electronic device displaying a dialogue interface of the voice assistant in response to a touch operation on the dialogue input box; the dialogue interface displays a first creation instruction. In the dialogue interface, the electronic device can respond to the user's editing operation on the creation instruction by sending an edited creation instruction, so that the electronic device creates a related reminder event according to the edited creation instruction.

[0021] In one possible implementation of the first aspect, the dialogue interface also displays a second creation instruction, which is used to guide the voice assistant to create a second reminder event associated with the first reminder event. The method further includes: in response to a second selection operation on the second creation instruction, sending the second creation instruction to the voice assistant to trigger the voice assistant to create a second reminder event based on the second creation instruction.

[0022] Therefore, electronic devices can generate multiple creation instructions based on the reminders to be created. After creating one reminder event, more related reminder events can be created quickly, saving steps in creating reminders and improving the user experience of creating reminders on electronic devices.

[0023] In one possible implementation of the first aspect, the target scenario includes a second application in an electronic device containing reminders; the second application includes at least SMS, gallery, memo, calendar, and notes; the gallery includes images related to the reminders. The second application here includes system applications.

[0024] Therefore, electronic devices can proactively identify reminders within system applications and generate creation instructions. Furthermore, if a phone detects that a user is browsing a system application containing reminders, it can also proactively perform page recognition and generate creation instructions. For example, if a phone detects that a user is browsing a successful appointment SMS, a screenshot of an appointment, or a ticket purchase email, it can prompt the user whether to generate a reminder event and generate creation instructions based on the page recognition results, saving the steps of creating a reminder.

[0025] In one possible implementation of the first aspect, in response to the electronic device recognizing the target scene, a first creation instruction is displayed on the interface of the electronic device, including: in response to the electronic device recognizing that a second application contains a reminder, displaying a dialogue interface of the electronic device's voice assistant on the desktop of the electronic device, wherein the dialogue interface displays the first creation instruction.

[0026] Therefore, the electronic device can generate a first creation instruction based on the relevant information of the reminder to be reminded in the second application, thereby saving the steps of creating the reminder.

[0027] In one possible implementation of the first aspect, before the first creation instruction is displayed on the interface of the electronic device, the method further includes: displaying a desktop card associated with the voice assistant of the electronic device, the desktop card displaying prompt information, the prompt information being used to prompt whether to create a first reminder event associated with the target scene; displaying the first creation instruction includes: displaying the first creation instruction in response to a second operation of the electronic device on the desktop card associated with the voice assistant.

[0028] In one possible implementation of the first aspect, the target scenario includes a user browsing the application interface of a third application, wherein the application interface of the third application is an application interface that satisfies at least one of the following page features: the application interface of the third application includes a calendar control; the application interface of the third application includes a reservation control; the application interface of the third application includes date-related recommendation information; the application interface of the third application includes location-related recommendation information; and the application interface of the third application includes a query message for asking the user whether to create a first reminder event.

[0029] Therefore, after recognizing the aforementioned page features, the electronic device can clearly understand the user's need to create a reminder event, and can then directly generate a creation command or ask whether a reminder event needs to be created. Furthermore, the electronic device can generate a creation command based on relevant information in the page features. For example, if the third-party application's interface includes a reservation control, it indicates that the user is likely to make a reservation for that event. In this case, the electronic device can directly generate and display a creation command based on the recognized information, guiding the user to create the corresponding reminder event.

[0030] In one possible implementation of the first aspect, the target scenario includes obtaining a user's behavioral profile and displaying a first creation instruction, including: in response to the behavioral profile obtained by the electronic device learning the user's habitual characteristics, displaying the first creation instruction on the interface of the electronic device; the first creation instruction is generated based on the user's behavioral profile.

[0031] In other words, electronic devices can learn the various things that users frequently need to create reminders for and proactively generate relevant creation instructions. As a result, users do not need to actively browse relevant pages or manually enter creation instructions; they can generate corresponding reminder events based on the creation instructions displayed by the electronic device, saving steps and improving the user's experience in creating reminder events.

[0032] In one possible implementation of the first aspect, the electronic device can display a dialogue input box for the voice assistant on the current interface in response to a user actively waking up the voice assistant. The electronic device then responds to the user's input in the dialogue input box by inputting a creation command, which is used to create a reminder event for the item to be reminded. The electronic device can then respond to the user's sending of the reminder command by creating a reminder event corresponding to the reminder command. Wherein, if the input operation is a manual input operation by the user, the sending operation can refer to the user's touch operation on the send control in the dialogue input box.

[0033] Alternatively, the input operation can also be the user's voice input operation, and there are no restrictions here.

[0034] In one possible implementation of the first aspect, after creating the first reminder event associated with the target scene, the method further includes: the electronic device outputting the first reminder event in a preset reminder mode; wherein the reminder mode includes at least displaying the reminder information corresponding to the first reminder event on a desktop card, displaying the reminder information corresponding to the first reminder event in a capsule mode, pushing the reminder information corresponding to the first reminder event to the user in a notification message, notifying the user of the reminder information corresponding to the first reminder event in an alarm mode, and notifying the user of the reminder information corresponding to the first reminder event in a countdown mode.

[0035] The above-mentioned reminder methods can be combined. Therefore, electronic devices can notify users in more ways, preventing users from missing reminders.

[0036] The electronic device will set a default reach level for each type of reminder event, which is also the default reminder method. The electronic device can modify the reminder method for each type of reminder event in response to user operations.

[0037] In one possible implementation of the first aspect, the method further includes: identifying the target scenario, determining the reminder time and reminder content of the item to be reminded; and generating a first creation instruction based on the reminder time and reminder content.

[0038] In summary, electronic devices can identify users' creation needs in different scenarios and provide guidance services, namely generating creation instructions to guide users in creating related reminder events. Alternatively, users can also proactively create related reminder events via their mobile phones based on their creation needs in different scenarios. Compared to conventional reminder creation methods, the steps are simpler. Furthermore, different reminder events can correspond to different reminder methods, making it easier to better remind users.

[0039] In a second aspect, this application provides an electronic device comprising: a processor, a memory, and one or more processors; the processor, the memory, and the processor being coupled together; wherein the memory stores computer program code, the computer program code including computer instructions, which, when executed by the processor, cause the electronic device to perform the method described in any one of the first aspects above.

[0040] Thirdly, this application provides a computer-readable storage medium storing instructions that, when executed on a computer, enable the computer to perform the method described in any one of the first aspects above.

[0041] Fourthly, this application provides a computer program product containing instructions that, when run on a computer, enable the computer to perform the method described in any one of the first aspects above.

[0042] It is understood that the electronic device described in the second aspect, the computer-readable storage medium described in the third aspect, and the computer program product described in the fourth aspect are all used to perform the corresponding methods provided above. Therefore, the beneficial effects they can achieve can be referred to the beneficial effects in the corresponding methods provided above, and will not be repeated here. Attached Figure Description

[0043] Figure 1 A schematic diagram of a mobile phone interface provided in an embodiment of this application;

[0044] Figure 2 This is a schematic diagram of an existing reminder delivery method provided in an embodiment of this application;

[0045] Figure 3 This application provides a schematic diagram of an interface for enabling intelligent recommendation services.

[0046] Figure 4 A schematic diagram of a mobile phone interface provided in an embodiment of this application;

[0047] Figure 5 A schematic diagram of an interface for creating a reminder event associated with a scenic spot reservation, provided as an embodiment of this application;

[0048] Figure 6 A schematic diagram of an interface for creating a notification event associated with a concert reservation and ticket-grabbing service, provided as an embodiment of this application;

[0049] Figure 7 A schematic diagram of an interface for creating a notification event associated with a train ticket reservation service, provided as an embodiment of this application;

[0050] Figure 8 A schematic diagram of the interface for creating a reminder event for a medical appointment registration service provided in this application embodiment;

[0051] Figure 9 A schematic diagram of a travel reminder interface provided in an embodiment of this application;

[0052] Figure 10 A schematic diagram of a travel reminder interface provided in an embodiment of this application;

[0053] Figure 11 A schematic diagram of an interface for guiding the creation of travel reminders is provided as an embodiment of this application;

[0054] Figure 12 A schematic diagram of an interface for guiding users to create a continuous monthly / yearly subscription cancellation reminder, provided as an embodiment of this application;

[0055] Figure 13 A schematic diagram of an interface for identifying associated events and guiding the creation of reminders, provided as an embodiment of this application;

[0056] Figure 14 A schematic diagram of an interface for identifying weather information and guiding the creation of reminders, provided as an embodiment of this application;

[0057] Figure 15 A schematic diagram of an interface for creating a reminder, provided as an embodiment of this application;

[0058] Figure 16 A schematic diagram of an interface for proactively creating reminders through a personalized assistant, provided as an embodiment of this application;

[0059] Figure 17 A schematic diagram of a dialog interface for creating a reminder, provided as an embodiment of this application;

[0060] Figure 18 A schematic diagram of an interface for proactively creating a reminder event, provided as an embodiment of this application;

[0061] Figure 19 A schematic diagram of a dialogue interface for a mobile phone's voice assistant provided in an embodiment of this application;

[0062] Figure 20A schematic diagram of a dialogue interface for a mobile phone's voice assistant provided in an embodiment of this application;

[0063] Figure 21 A schematic diagram of a card specification provided for an embodiment of this application;

[0064] Figure 22 A schematic diagram of an interface for editing cards provided in an embodiment of this application;

[0065] Figure 23 This is a schematic diagram of an editing reminder method provided in an embodiment of this application;

[0066] Figure 24 A schematic diagram of a deletion reminder interface provided in an embodiment of this application;

[0067] Figure 25 A schematic diagram of an interface for deleting reminder card content provided in an embodiment of this application;

[0068] Figure 26 A schematic diagram of an instant reminder interface provided for an embodiment of this application;

[0069] Figure 27 A schematic diagram of a personal center interface provided in an embodiment of this application;

[0070] Figure 28 A schematic diagram of an interface for viewing reminders provided in an embodiment of this application;

[0071] Figure 29 A schematic diagram of an interface for synchronizing reminder content to a calendar, provided as an embodiment of this application;

[0072] Figure 30 A schematic diagram of a mobile phone interface for an editing reminder method provided in an embodiment of this application;

[0073] Figure 31 A schematic diagram of a dialogue interface for a voice assistant provided in an embodiment of this application;

[0074] Figure 32 A schematic diagram of a mobile phone interface provided in an embodiment of this application;

[0075] Figure 33 A schematic diagram of the software structure of an electronic device provided in an embodiment of this application;

[0076] Figure 34 A schematic diagram of the hardware structure of an electronic device provided in an embodiment of this application;

[0077] Figure 35 This is a schematic diagram of a chip system provided in an embodiment of this application. Detailed Implementation

[0078] The technical solutions of the embodiments of this application will now be described with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of them. All other embodiments obtained by those skilled in the art based on the embodiments of this application without creative effort should fall within the scope of protection of this application.

[0079] It should be noted that the terms "first," "second," etc., used below are for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Therefore, a feature defined with "first," "second," etc., may explicitly or implicitly include one or more of that feature. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or apparatus that includes a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units not listed, or may optionally include other steps or units inherent to these processes, methods, products, or apparatuses.

[0080] References to "one embodiment" or "some embodiments" as described 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, phrases such as "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.

[0081] In the embodiments of this application, the terms "exemplary" or "for example" are used to indicate that something is an example, illustration, or description. Any embodiment or design that is described as "exemplary" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or designs. Specifically, the use of the terms "exemplary" or "for example" is intended to present the relevant concepts in a specific manner.

[0082] Personal reminder events (or simply reminder events) on electronic devices (such as mobile phones) can cover many aspects of a user's life, helping them remember important matters, optimize time management, and reduce omissions. Currently, when creating personal reminder events such as calendars, alarms, to-do lists, and shortcuts on electronic devices, the device first needs to respond to the user's opening of the application and enter the interface of the various applications. Then, the electronic device can only create the personal reminder event by receiving different reminder settings from the user. The process of creating personal reminder events is relatively cumbersome.

[0083] Taking a mobile phone as an example, where the phone manually creates a schedule reminder in response to the user's actions, please refer to [link to relevant documentation]. Figure 1 The image shows a schematic diagram of a mobile phone interface. Figure 1 As shown, in response to the user's operation, the phone opens the calendar application 102 on the phone's home screen 101, displaying the main interface 103 of the calendar application 102. Then, in response to the user's selection of the add schedule control 104, the phone enters the schedule settings page 105 of the calendar application 102. Finally, in response to the user's settings of the schedule reminder-related parameters in the schedule settings page 105, the phone creates a reminder event for that schedule. These related parameters include the specific date and time of the schedule reminder event, the reminder time, and the reminder content, etc.

[0084] Therefore, in the above process, each time a reminder event is set for the schedule, it is necessary to first enter the application interface and then enter the settings page for that event, which involves many steps and is quite cumbersome.

[0085] Furthermore, the various scenarios supported by the aforementioned personal reminder events have relatively limited settings. For example, the alarm app does not support setting recurring patterns for odd and even weeks, and the items to carry cannot be set based on the user's travel schedule.

[0086] Furthermore, existing notification entry points based on system access are prone to delays in notification delivery, making it easy for users to miss them. For example, some notifications are only displayed on the desktop or lock screen and cannot be displayed on top of any application. If the set reminder time is short, users are likely to miss notifications displayed on the desktop or lock screen. Figure 2 As shown in (a), the existing ticket purchase reminder 201 is only displayed on the phone's lock screen 202. Figure 2 As shown in (b), concert ticket reservation reminders are sent to users via app message push notifications, which are typically displayed on the lock screen.

[0087] This application provides a method and electronic device for personal information reminders. The electronic device can identify a target scene, display a creation instruction associated with the target scene, and create a reminder event associated with the target scene based on the creation instruction. The reminder event is used to remind users of pending reminders in the target scene. Thus, the electronic device can proactively identify the target scene and display the creation instruction, thereby guiding the user to create a reminder event associated with the target scene. This eliminates the need for the electronic device to respond to user operations by entering an application interface; instead, the reminder event is created through the user's step-by-step operations on the application interface, simplifying the process of creating reminder events.

[0088] In this application, the target scenario refers to a scenario where there are reminders for events in the future. Examples include ticket browsing scenarios (such as airline tickets, train tickets, concert tickets, etc.), travel scenarios, meeting scheduling scenarios, birthday celebration scenarios, and daily task scenarios. For example, in a ticket browsing scenario, when a user browses airline tickets or concert tickets, the electronic device automatically identifies and prompts whether to set travel or event reminders. In a travel scenario, after a user successfully books tickets for a scenic spot, the electronic device automatically identifies the travel need and prompts whether to set travel reminders. In a meeting scheduling scenario, when a user receives a meeting invitation email or SMS, the electronic device automatically identifies and prompts whether to set meeting reminders and automatically fills in the meeting information. In a birthday celebration scenario, when the electronic device identifies that a user's friend or family member's birthday is approaching through the calendar or social media, it automatically prompts whether to set birthday greetings. In a daily task scenario, when the electronic device detects that the weather forecast predicts light rain, it automatically prompts whether to bring an umbrella.

[0089] In this application, the creation of reminder events by electronic devices may include: the electronic device automatically filling in basic information about the reminder event, such as time, location, and specific reminder content. Furthermore, users can modify or supplement the basic information as needed.

[0090] In this application, the creation instructions can be in the form of text, images, voice, or video, among other things. These instructions help users understand and create reminder events associated with the target scenario. For example, in a ticket browsing scenario, such as a flight ticket browsing scenario, the creation instructions could include "Do you need to set a reminder for my flight on XX day?" or "Remind me to buy tickets at 9 AM on XX day." In a concert ticket browsing scenario, the creation instructions could include "Do you want to remind me to attend the YY concert on XX day?" or "Remind me to grab concert tickets at 2 PM on XX day."

[0091] Furthermore, after an electronic device establishes a reminder event using the above method, it can display the reminder event in a preset reminder mode. The reminder mode can be set to a one-time reminder or a periodic reminder, and can include, but is not limited to, vibration, ringtone, pop-up window, etc., simultaneously displaying the reminder event to the user. The methods of displaying the reminder event to the user include, but are not limited to, displaying a desktop card on the desktop, displaying a capsule on top of the application interface, notifications within the capsule, notifications, always-on display, and displaying on associated wearable devices, etc., to provide personalized reminder methods, making the reminder event more eye-catching and ensuring timely and effective reminder delivery.

[0092] Furthermore, the creation instruction typically consists of a reminder time, a reminder event, and a fixed word. For example, the creation instruction for a ticket booking scenario could be "Remind me to book tickets at 2 PM on XX day," where the reminder time is "2 PM on XX day," the reminder event is "book tickets," and the fixed word is "remind me." Thus, the language of the creation instruction is relatively natural and concise.

[0093] It should be understood that in this application, the electronic device may enable the reminder function (or reminder event creation function or reminder creation function) before creating a reminder event.

[0094] In this embodiment, the electronic device enables its own reminder function by activating the intelligent recommendation service in the smart assistant application. Please refer to [link to relevant documentation]. Figure 3 , Figure 3 This is a schematic diagram of an interface for enabling intelligent recommendation services, provided as an embodiment of this application. Figure 3 As shown, taking a mobile phone as an example, the mobile phone has a smart assistant application installed. Figure 3 As shown in (a), the mobile phone can respond to the user's selection operation on the control 302 corresponding to the Smart Assistant application in the settings interface 301, and display as shown in (a). Figure 3 The smart assistant application interface 303 shown in (b) is shown.

[0095] The smart assistant application interface 303 also includes a smart recommendation service control 304. The mobile phone can respond to the user's selection operation on the smart recommendation service control 304 and display, as shown below. Figure 3 The intelligent recommendation service interface 305 is shown in (c). The intelligent recommendation service interface 305 includes a control 306 corresponding to the voice assistant. At this time, the voice assistant function is enabled, and the control 306 corresponding to the voice assistant displays the message "Enabled". The mobile phone can respond to the user's selection operation on the control 306 corresponding to the voice assistant and display the following... Figure 3 The service management interface 307 for the voice assistant is shown in (d).

[0096] The voice assistant's service management interface 307 includes a switch control 308 corresponding to the voice assistant, which is currently in the "on" state. The mobile phone can respond to the user's on / off operation of the switch control 308 to turn the voice assistant function on or off. The voice assistant's service management interface 307 also includes a service provision method 309.

[0097] Service delivery methods refer to the way reminder events are notified to users, also known as reminder methods. The service delivery methods mentioned above include desktop card sets, capsules, and notifications. These are just examples; other methods may include negative one screen cards, always-on display (AOD), and multi-device synchronization. Multiple devices in multi-device synchronization include wearable devices, in-vehicle devices, etc. Wearable devices can be smart headphones and smartwatches. It is understood that wearable devices can also be other electronic devices that communicate with mobile phones.

[0098] In this embodiment, if the voice assistant function is not manually enabled in advance in the voice assistant service management interface, it can be enabled again during subsequent use. For example, the phone can wake up the voice assistant in response to the user pressing the power button, or the phone can wake up the voice assistant in response to the user long-pressing the global navigation key. If the voice assistant is not enabled, a prompt message will be displayed on the phone screen, indicating that the voice assistant function is not enabled on the phone and needs to be manually enabled.

[0099] Specifically, the phone screen can display a path to enable the voice assistant function, allowing users to find the service management interface for the voice assistant and then activate the voice assistant function in response to the user's action. Alternatively, the phone screen can display a shortcut, allowing the phone to navigate to the voice assistant function's service management interface upon clicking the shortcut, and then activate the voice assistant function in response to the user's action.

[0100] In this application, the future time period in the reminder for a future time period can include, but is not limited to, a specific time, a time associated with a location, or a time associated with an event. The specific time includes, but is not limited to, a time associated with a particular time, an important date, or an expected time. For example, taking the reminder for a future time period as taking medication... Figure 4 As shown in (a), in the voice assistant's dialogue interface 401, the user sends a command 402 associated with a reminder: "Remind me to take my medicine tomorrow." The phone creates a reminder event "Remember to take your medicine at 8 a.m. tomorrow" based on the command associated with the reminder. At this time, the dialogue interface 401 will reply with a card 403 corresponding to the reminder event, which displays the basic information of the reminder event, including the specific time: 8 a.m. tomorrow, and the specific reminder content: take medicine.

[0101] The time associated with the location can include, but is not limited to, the time associated with the arrival location, departure location, etc. For example, taking the reminder as an airplane arrival reminder... Figure 4As shown in (b), in the personalized assistant's dialogue interface 404, the user enters the instruction associated with the reminder in the input box 405: "Remind me to reply to the email after the plane lands." The phone creates a reminder event "Remember to reply to the email after the plane lands" based on the instruction associated with the reminder. The user can also reply with a card corresponding to the reminder event in the dialogue interface. The card displays the basic information of the reminder event, including the time associated with the arrival location: after the plane lands, and the specific reminder content: reply to the email.

[0102] The time associated with the event can include at least one of the following: the time associated with an order event, the time associated with an environmental event, and the time associated with a system event. For example, an order event could be a baggage reminder for flight travel; an environmental event could be a weather change reminder to bring rain gear; and a system event could be a missed call reminder.

[0103] Taking the reminders for baggage on flights as an example, such as... Figure 4 As shown in (c), the desktop card 406 corresponding to the voice assistant displays basic information about the reminder event: remind me to bring my ID card before the business trip. This basic information includes the time "before the business trip" which is associated with the business trip, and the specific reminder content is to bring my ID card.

[0104] Taking the reminder about weather changes and rain gear as an example, such as... Figure 4 As shown in (d), the desktop card 407 corresponding to the voice assistant displays basic information about the reminder event: If it rains tomorrow, remember to remind me to bring an umbrella. This basic information includes the time "tomorrow" which is associated with rain, and the specific reminder content is to bring an umbrella.

[0105] Taking a missed call reminder as an example, such as... Figure 4 As shown in (e), after the phone activates the voice assistant on the desktop, the voice assistant's input box 408 can display the instruction associated with the reminder: "Remind me immediately if I missed a call from Contact 1." The phone can create a reminder event "Remind me immediately if I missed a call from Contact 1" based on the instruction associated with the reminder.

[0106] In this application, the scenarios for setting reminder events can include, but are not limited to, various life scenarios, such as new movie / TV show releases, live-stream shopping sprees, ordering takeout, paying bills, game activity reminders, concert / exhibition reminders; travel scenarios, such as carrying items, departure reminders, and arrival reminders; commuting scenarios, such as bringing an umbrella in abnormal weather, checking traffic conditions, and departure reminders; office scenarios, such as meeting reminders, deadline reminders, lists of things to be reminded, and team collaboration reminders; sports and health scenarios, such as medication reminders, hydration reminders, exercise plan reminders, and sleep monitoring reminders; scheduling scenarios, such as birthday reminders and anniversary reminders; learning scenarios, such as class time reminders, exam review reminders, and book reading reminders; financial management scenarios, such as bill payment reminders, budget reminders, and investment plan reminders; and daily habit scenarios, such as meditation / yoga reminders, early rising / early bedtime reminders, and skincare / beauty reminders.

[0107] In this embodiment, reminder events can be divided into at least three categories: First, reminders for appointment services, such as ticket purchases, appointment registration, scenic spot reservations, and travel reminders. Second, reminders for items to bring, such as reminding users to bring essential items based on their travel schedule. Third, reminders for tasks to be done, such as reminders for early morning check-ins, exercise and health, and safe electricity use.

[0108] Table 1 below illustrates the three types of alert events and provides examples, as detailed below:

[0109] Table 1

[0110]

[0111]

[0112] In this embodiment, the first and second types of reminder events mentioned above are typically those where the electronic device can proactively identify the user's different needs in different scenarios and provide guidance services, i.e., displaying a creation command and guiding the user to create a reminder event associated with the creation command. The third type of reminder event mentioned above is usually created by the user actively inputting a command for the reminder item through their mobile phone, or it can be created automatically by the electronic device learning the user's habitual characteristics and other information, guiding the user to create a reminder event associated with the creation command.

[0113] In this embodiment, taking a mobile phone as an example, we will first introduce how the mobile phone generates creation instructions based on different identified scenarios to guide the user in creating related reminder events.

[0114] As mentioned above, reservation service reminders can include ticket booking reminders and / or travel reminders. It should be understood that a reservation service reminder can be understood as a reminder event associated with a reservation service. The process of creating ticket booking reminders and travel reminders is described below.

[0115] I. Reminder for Booking Tickets in Advance

[0116] As described in Table 1 above, ticket booking reminders (or ticket booking reminder events) can include, but are not limited to, different types of reminder events such as: medical appointment registration, train ticket booking, concert ticket booking, scenic spot reservations, etc. They can also include reminder events associated with other applications that provide ticket booking services, without any restrictions.

[0117] Optionally, the mobile phone can detect whether the user is browsing a reservation ticketing service page associated with the first application. In response to the user browsing the reservation ticketing service page associated with the first application (or in other words, in response to the user browsing the ticketing service), the phone can identify the content of the reservation ticketing service page, generate a creation instruction based on the identification result, and actively guide the user to create a reminder event associated with the first application (or a reservation ticketing reminder event / reservation ticketing reminder).

[0118] The aforementioned user browsing the ticket reservation and booking service page associated with the first application could mean that the user is currently browsing the ticket reservation and booking service page, or that the user has already browsed the ticket reservation and booking service page a while ago.

[0119] In addition to users browsing the ticket booking service page, if the phone detects that a user has opened the ticket booking service page associated with the first application, it can also respond to the user opening the ticket booking service page associated with the first application, identify the content of the ticket booking service page, generate a creation instruction based on the identification result, and actively guide the user to create a reminder event associated with the first application.

[0120] The first application's associated ticket booking service page includes control features, such as booking controls. If the phone detects that the user's browsing page contains booking controls, it can generate a creation command based on the page recognition results.

[0121] The first application can be an application associated with a reservation and ticket-grabbing service, such as a train ticket purchase app, a scenic spot's official app, a concert ticket grabbing app, or a medical appointment booking app.

[0122] The mobile phone can recognize the content of the ticket reservation and booking service page, identifying the type of reservation and booking reminder event and the start time of the booking process. By recognizing the type of the reservation and booking reminder event, the phone can determine the corresponding notification method. By recognizing the start time of the booking process, the phone can determine the reminder time, which is earlier than the start time of the booking process.

[0123] Therefore, the mobile phone can determine the type of the ticket reservation reminder event and the corresponding delivery method, and then display the ticket reservation reminder event (or reminder event) to the user in the corresponding delivery method. Here, the delivery method refers to the behavior of delivering information to the user through various channels or means, that is, the service delivery method or reminder method mentioned above.

[0124] Different types of reminder events can have different service provision methods. In one example, the phone may have default configurations for the service provision methods corresponding to different types of reminder events. In another example, the phone can display a settings interface for the service provision method associated with the reminder event when it is created, allowing the user to modify the associated service provision method. For instance, the phone could prompt the user to open the service management interface of the phone's voice assistant, allowing the user to modify the service provision method corresponding to the reminder event through checkboxes on that interface.

[0125] The following, with reference to the attached diagrams, will introduce the creation process of several types of reminder events, including scenic spot visit reservations, concert ticket scalping, train ticket scalping, and medical appointment registration:

[0126] 1.1 Scenic Area Visit Reservation

[0127] Figure 5 This is a schematic diagram of an interface for creating a reminder event associated with a scenic spot reservation, provided as an embodiment of this application. Please refer to [link / reference]. Figure 5 As shown in (a), in response to a user opening the scenic area's app, the app's homepage 501 displays a visit reservation control 502. Please refer to... Figure 5 As shown in (b), in response to the user's selection of the visit reservation control 502, the visit requirements page 503 of the scenic area is entered.

[0128] When the mobile phone recognizes that the user has opened or browsed the visit requirements page 503 of the scenic spot, the global navigation bar 504 at the bottom of the visit requirements page 503 may flash to indicate that the mobile phone can activate the voice assistant, which will then generate a creation command for the user and guide the creation of the corresponding reminder event.

[0129] The scenic area's visit requirements page is part of the aforementioned reservation and ticket-grabbing service page, which may also include a visit date selection page, etc. In other words, the global navigation bar at the bottom of the current page may flash when a user opens or browses either the scenic area's visit requirements page or the visit date selection page.

[0130] The "ticket reservation and booking service page" can refer to a page that includes reservation controls, such as a page showing the visit requirements of a scenic spot that includes reservation controls.

[0131] The global navigation bar refers to the short horizontal line at the bottom of the screen. It can be used to respond to user presses to activate the voice assistant, to respond to user swipes up from the bottom edge of the screen to return to the desktop, and to respond to user swipes inward from the left or right edge of the screen to return to the previous level.

[0132] At this point, if the phone responds to the user's press operation on the global navigation bar 504, the phone will activate the voice assistant, such as... Figure 5 As shown in (c), the mobile phone can display an input box 505 at the bottom of the visitor request page 503, and the input box 505 displays a creation instruction 506. The creation instruction 506 is generated by the mobile phone based on the page recognition result of the visitor request page 503.

[0133] In some examples, the phone can have various pre-set creation commands. Specifically, a creation command can consist of time + event + fixed word, and the statement is relatively natural and simple. For example, a creation command could be: "Remind me to grab tickets tomorrow night at 7 pm." Here, the time is "tomorrow night at 7 pm," the event is "grab tickets," and the fixed word is "remind me." The fixed word is the default setting on the phone, but it can also be modified to "remind me," "please remind me," etc., and this application does not restrict this. The time and event in the creation command are obtained based on the page recognition results.

[0134] exist Figure 5 In the example, the mobile phone determines the ticket-grabbing start time based on the page recognition results of the scenic spot visit requirements page. Then, it composes a creation instruction based on the ticket-grabbing start time and the ticket-grabbing event. For example, if the ticket-grabbing start time is 7 pm every day, and the ticket-grabbing time for today has already passed by then, then the default ticket-grabbing time is tomorrow. The composed creation instruction could be something like this: Figure 5 (c) shows: "Remind me to make an appointment to visit the xx Museum at 7 pm tomorrow."

[0135] The mobile phone does not necessarily only recognize the current page; it can also retrieve and recognize all pages related to the reservation and ticket grabbing to obtain relevant information that can generate creation instructions.

[0136] like Figure 5 As shown in (c), a send control 507 and a keyboard control 508 are also displayed at the location of input box 505. The mobile phone can send the creation command in response to the user's selection of send control 507. Alternatively, the mobile phone can pull up the keyboard in response to the user's selection of keyboard control 508 to modify the creation command entered in input box 505.

[0137] On the visitor requirements page 503, related recommended terms 509 can also be displayed. For example, related recommended terms 509 are displayed above the input box 505. These related recommended terms are those relevant to the current scenario. The mobile phone can respond to the user's selection of a related recommended term by redirecting to the search interface corresponding to that term. In other words, the related recommended terms function as a shortcut control, allowing users to access more information related to the scenario.

[0138] like Figure 5 The related recommended keywords shown in (c) can be: xx museum, parking lot. Due to the size limitations of the visit requirement page 503 and the character limit of the related recommended keywords, the current page can only display a set number of related recommended keywords in full. When there are many related recommended keywords, the mobile phone can respond to the user's swipe operation on the display position of the related recommended keywords and switch to display other related recommended keywords on the visit requirement page 503.

[0139] After sending the creation command, the voice assistant's dialogue interface 510 is displayed on the scenic spot visit requirements page 503 of the mobile phone, such as... Figure 5 As shown in (d). In the dialog interface 510, after sending the creation command, the mobile phone creates a reminder event associated with the creation command and then replies with a reply message for the creation command.

[0140] The response information in the chat interface mainly consists of three parts. The first part is the reminder creation information, which notifies the user that the phone has created a corresponding reminder event according to the creation command. The second part is the card corresponding to the reminder, which contains all the information about the reminder event, including the reminder time and content. The third part is the associated creation command, that is, the command corresponding to the reminder event associated with this reminder event.

[0141] At this point, the phone has created a reminder event for the scenic area's reservation service. The phone can display the created reminder event via a desktop card, or it can display it through other service providers. For example, the phone can also display the reminder event as a card within the phone's capsule.

[0142] The service delivery method can also correspond to different types. For example, in-capsule notifications can correspond to alarm clock, timer, and schedule types. Furthermore, a single service delivery method can correspond to multiple types. For instance, a timer type can be combined with an alarm clock type. Suppose the in-capsule notification corresponds to a timer type, and the alarm rings when the timer reaches a preset time.

[0143] Assuming the notification service is provided via in-capsule notifications, and these in-capsule notifications correspond to a timer type, then upon reaching the set time, the in-capsule notification for the timer will be displayed at the top of any screen on the phone. The in-capsule notification will display the timer's duration, which decreases over time. This "any screen" can include the home screen, application screens, notification center screens, multitasking screens, lock screens, etc.

[0144] In some embodiments, the above-mentioned type can also be used together with the service provision method as a notification method. The service provision method corresponding to the notification event can be modified in the phone settings, while the type can be the phone's default setting. Alternatively, the phone can provide an entry point to modify the type corresponding to different notification events.

[0145] like Figure 5 As shown in (e), an in-capsule notification 512 is displayed at the top of the photo album application interface 511. The in-capsule notification 512 is a timer type and also displays appointment reminder information 513, such as: "Book a visit to xx museum." Furthermore, the in-capsule notification 512 also displays a details view control 514.

[0146] In this scenario, clicking the "View Details" control 514 on the mobile phone will directly take you to the reservation interface 515. The reservation interface 515 displays reservation-related information, including the visit date, entry time, and personal information. Within this interface 515, users can easily access basic personal information and social relationships. Basic personal information includes name, gender, date of birth, and ID number, while social relationships include basic information about the user's parents, children, spouse, etc. For example, after entering a name, the user can instantly retrieve the corresponding ID number.

[0147] like Figure 5 As shown in (f), after all the information of the visitors is entered, the mobile phone responds to the user's selection operation on the confirm control 516 and the user's selection operation on the submit reservation control 517, and completes the submission of the reservation information.

[0148] Understandably, the reservation interface 515 can be accessed at any time through the details view control 514, or directly through the reservation system. However, reservations cannot be successfully made until the timer reaches 0.

[0149] For this reminder event, the type of notification within the capsule can be switched. Besides the timer type mentioned above, it can also be an alarm type, or simply display the appointment information on a card within the capsule. Alternatively, two or more types can be combined, such as a countdown timer combined with an alarm type. The countdown timer is set to 5 minutes, but this can be changed to 8 minutes, 10 minutes, etc.

[0150] In this embodiment, the mobile phone can set the service provision method type according to the type of reminder event. For example, if the reminder event is related to booking tickets in advance, the service provision method corresponding to the reminder event can be set to the timer type; if it is a medication reminder, the service provision method corresponding to the reminder event can be set to the alarm type. For example, if the service provision method corresponding to the reminder event related to booking tickets in advance is a capsule, then the capsule is set to the timer type.

[0151] After successful booking, the following will be displayed: Figure 5 The reservation success screen shown in (g) is 518.

[0152] Therefore, when the mobile phone detects that a user is browsing the ticket reservation service page, it can display the corresponding creation instructions for ticket reservation on the page, guiding the user to create a reminder event associated with ticket reservation according to the creation instructions, so as to make the creation of reminder events faster.

[0153] 1.2 Concert Ticket Booking and Reservation

[0154] Figure 6 Please refer to the following diagram illustrating an interface for creating a notification event associated with a concert reservation and ticket-grabbing service, as provided in this application embodiment. Figure 6 ,like Figure 6 As shown in (a), when the mobile phone detects that the user is browsing the concert ticket reservation page 601, the global navigation bar 602 at the bottom of the reservation page 601 can flash to indicate that the mobile phone can activate the voice assistant to provide reminders and guidance services to the user. The aforementioned reservation page can refer to all pages related to concert ticket reservations, such as the concert's performance introduction page, the concert date and ticket selection page, etc. Figure 6 In (a), the reservation and ticket-grabbing page 601 refers to the concert performance page.

[0155] At this time, if the phone responds to the user's press operation on the global navigation bar 602, then as follows: Figure 6As shown in (b), the mobile phone can display an input box 603 at the bottom of the ticket reservation page 601, and the input box 603 displays a creation instruction 604. The creation instruction 604 is obtained by the mobile phone based on the page recognition result of the ticket reservation page.

[0156] exist Figure 6 In the example, the mobile phone determines the ticket-buying start time based on the page recognition results of the concert's performance introduction page. Then, it composes a creation command based on the ticket-buying start time and the ticket-buying event. For example, if the ticket-buying start time is 8:00 AM on July 1st, the composed creation command can be... Figure 6 As shown in (b): "Remind me to grab concert tickets at 8:00 on December 1st".

[0157] The input field 603 also displays a send control 605 and a keyboard control 606. The phone can send the creation command in response to the user's selection of the send control 605. Alternatively, the phone can pull up the keyboard in response to the user's selection of the keyboard control 606, modifying the creation command entered in the input field 603.

[0158] After sending the creation command, the voice assistant's dialogue interface 607 is displayed on the mobile phone's reservation and ticket-grabbing page 601, such as... Figure 6 As shown in (c). In the dialog interface 607, after sending the creation command, the mobile phone creates a reminder event associated with the creation command and then replies with a response message for the creation command.

[0159] At this point, the phone has created a reminder event for the concert ticket-grabbing service. The phone can display this reminder event as a desktop card, or it can be displayed through other service providers. For example, the phone can also display the reminder event as a card within a capsule.

[0160] Assuming the service delivery method for this reminder event includes in-capsule notifications, and the in-capsule notifications correspond to a timer type, then after the timer's set time is reached, the in-capsule notification corresponding to the timer can be displayed in the top area of ​​any screen on the phone. The in-capsule notification displays the timer's duration, and the timer's duration decreases as time progresses.

[0161] like Figure 6 As shown in (d), an in-capsule notification 609 is displayed at the top of the interface 608 of a certain application (camera app). The in-capsule notification 609 is a timer type and also displays a ticket-grabbing prompt 610, such as: "Grab tickets for xx concert." Furthermore, the in-capsule notification 609 also displays a details view control 611.

[0162] In this scenario, the mobile phone responds to a click on the details view control 611, directly entering the ticket reservation interface 612. The ticket reservation interface 612 displays information related to ticket reservations, including concert show times and ticket tiers. Within this reservation interface 612, users can obtain basic personal information and social connections with a single click.

[0163] like Figure 6 As shown in (e), after selecting various concert information, the mobile phone responds to the user's selection operation on the submit ticket reservation control 613 and completes the submission of ticket reservation information.

[0164] Understandably, before the timer reaches 0, the ticket reservation interface can be accessed at any time via the details viewer (611) or by directly accessing the concert reservation system to complete the reservation. After the ticket-buying start time arrives, i.e., when the timer reaches 0, the submitted reservation information can be retrieved directly, and the ticket-buying process can begin.

[0165] Therefore, when the mobile phone detects that a user is browsing the ticket reservation service page, it can display the corresponding creation instructions for ticket reservation on the page, guiding the user to create a reminder event associated with ticket reservation according to the creation instructions, so as to make the creation of reminder events faster.

[0166] It's important to note that for scenic spot reservations, when the timer reaches 0, it signifies the start time for ticket reservations. For concert ticket scalping, however, when the timer reaches 0, it signifies the start time for ticket scalping. Submitting reservation information before the start time is to increase your chances of being able to participate in the ticket scalping process faster. However, it's not always necessary to submit reservation information before the start time; the timer's purpose is to remind users that the ticket scalping period is approaching and to prepare accordingly.

[0167] 1.3 Train ticket booking and reservation

[0168] Figure 7 Please refer to the schematic diagram of an interface for creating a reminder event associated with a train ticket booking service, provided in an embodiment of this application. Figure 7 ,like Figure 7 As shown in (a), when the mobile phone detects that the user is browsing the train ticket grabbing page 701, the global navigation bar 702 at the bottom of the train ticket grabbing page 701 may flash to indicate that the mobile phone can activate the voice assistant to provide reminder and guidance services to the user. The aforementioned train ticket grabbing page may include a train number selection page, a train ticket date selection page, etc.

[0169] At this time, if the phone responds to the user's press operation on the global navigation bar 702, then as follows Figure 7As shown in (b), the mobile phone can display an input box 703 at the bottom of the train ticket grabbing page 701, and the input box 703 displays a creation instruction 704. The creation instruction 704 is obtained by the mobile phone based on the page recognition result of the train ticket grabbing page.

[0170] exist Figure 7 In the example, the mobile phone determines the start time of ticket grabbing for the train based on the page recognition results of the train ticket grabbing page. Then, it composes a creation command based on the ticket grabbing start time and the train ticket grabbing event. For example, if the ticket grabbing time for the train is 9:00 AM on July 1st, the composed creation command can be... Figure 7 As shown in (b): "Remind me to grab train tickets at 9:00 on July 1st".

[0171] The input field 703 also displays a send control 705 and a keyboard control 706. The phone can send the creation command in response to the user's selection of the send control 705. Alternatively, the phone can pull up the keyboard in response to the user's selection of the keyboard control 706, modifying the creation command entered in the input field 703.

[0172] After sending the creation command, the voice assistant's dialogue interface 707 is displayed on the train ticket grabbing page 701 of the mobile phone, such as... Figure 7 As shown in (c). In the dialog interface 707, after sending the creation command, the mobile phone creates a reminder event associated with the creation command and then replies with a response message for the creation command.

[0173] At this point, the phone has created a notification event for the train ticket booking service. The phone can display this notification event via a home screen card or through other service providers. For example, the phone can also display the notification event via a card within the phone's capsule.

[0174] Assuming the service delivery method for the train ticket booking-related reminder event includes in-capsule notifications, and these in-capsule notifications correspond to a timer type, then after the timer's set time is reached, the in-capsule notification corresponding to the timer will be displayed at the top area of ​​any screen on the phone. The in-capsule notification will show the timer's duration, and the timer's duration will decrease over time. Figure 7 As shown in (d), an in-capsule notification 709 is displayed at the top of the interface 708 of a certain application (camera app). The in-capsule notification 709 is a timer type and also displays a ticket-grabbing prompt message 710, such as: "Grab train tickets." Furthermore, the in-capsule notification 709 also displays a details view control 711.

[0175] In this scenario, when a mobile phone clicks on the "View Details" control 711, it can directly access the ticket purchase interface 712 for a specific train ticket. The ticket purchase interface 712 displays ticket-related information, including the seat type of the train ticket.

[0176] like Figure 7 As shown in (e), after filling in various information for train ticket purchase, the mobile phone responds to the user's selection operation on the reservation control 713 and completes the submission of the ticket purchase information.

[0177] Understandably, before the timer reaches 0, the ticket purchase interface can be accessed at any time through the details view control 711, or directly through the train ticket purchase system. However, train tickets cannot be successfully booked before the timer reaches 0.

[0178] Therefore, when the mobile phone detects that a user is browsing the ticket reservation service page, it can display the corresponding creation instructions for ticket reservation on the page, guiding the user to create a reminder event associated with ticket reservation according to the creation instructions, so as to make the creation of reminder events faster.

[0179] 1.4 Appointment Booking for Medical Consultation

[0180] Figure 8 Please refer to the schematic diagram of the interface for creating reminder events for the appointment booking service provided in this application embodiment. Figure 8 ,like Figure 8 As shown in (a), when the mobile phone detects that the user is browsing the registration page 801, the global navigation bar 802 at the bottom of the registration page 801 can flash to indicate that the mobile phone can activate the voice assistant to provide reminder and guidance services to the user. Here, the registration page refers to the registration page for a specific disease type within a specific department, or the registration page for a specific doctor within a specific department. In other words, in order to generate and display more accurate creation instructions, the mobile phone will only flash the global navigation bar at the bottom of the page after recognizing relatively specific relevant information. Figure 8 The registration page 801 shown in (a) refers to the registration page of a certain doctor A in a certain department.

[0181] At this time, if the phone responds to the user's press operation on the global navigation bar 802, then as follows: Figure 8 As shown in (b), the mobile phone can display an input box 803 at the bottom of the registration page 801, and the input box 803 displays a creation instruction 804. The creation instruction 804 is obtained by the mobile phone based on the page recognition result of the registration page.

[0182] exist Figure 8In the example, the mobile phone determines the start time for booking an appointment with a doctor based on the page recognition results of the registration page. Then, it composes a creation instruction based on the start time of booking and the appointment booking event. For example, if the start time for booking an appointment is 7:00 AM tomorrow, the composed creation instruction can be... Figure 8 (b) shows: "Remind me to grab a number at 7 am tomorrow".

[0183] The input box 803 also displays a send control 805 and a keyboard control 806. The phone can respond to the user's selection of the send control 805 by sending the creation command. Alternatively, the phone can respond to the user's selection of the keyboard control 806 by pulling up the phone's keyboard and modifying the creation command entered in the input box 803. For example, the department's appointment release time may differ from a doctor's appointment release time. If the phone generates the creation command based on the department's appointment release time, then the phone can modify the creation command in response to the user's input.

[0184] After sending the creation command, the voice assistant's dialogue interface 807 is displayed on the phone's registration page 801, such as... Figure 8 As shown in (c). In the dialog interface 807, after sending the creation command, the mobile phone creates a reminder event associated with the creation command and then replies with a response message for the creation command.

[0185] At this point, the phone has created a reminder event for the appointment booking service. The phone can display the created reminder event via a home screen card, or it can display it through other service providers. For example, the phone can also display the reminder event via a card within the phone's capsule.

[0186] Assuming the service delivery method for the reminder event associated with this medical appointment registration includes in-capsule notifications, and these in-capsule notifications correspond to a timer type, then after the timer's set time is reached, the in-capsule notification corresponding to the timer can be displayed in the top area of ​​any screen on the phone. The in-capsule notification displays the timer's duration, and the timer's duration decreases as time progresses. For example... Figure 8 As shown in (d), an in-capsule notification 809 is displayed at the top of the interface 808 of a certain application. The in-capsule notification 809 is a timer type and also displays registration prompt information 810, such as: "Register for a doctor's appointment." Furthermore, the in-capsule notification 809 also displays a details view control 811.

[0187] In response to a click on the details view control 811, the mobile phone can directly access Doctor A's registration interface 801. This registration interface 801 displays registration-related information, including the registration date and registration time period.

[0188] like Figure 8As shown in (e), after filling in the various registration information, the mobile phone responds to the user's selection operation on the confirmation control 812 and completes the submission of the registration information.

[0189] Understandably, before the timer reaches 0, the registration interface 801 can be accessed at any time through the details view control 811, or directly through the appointment registration system. However, registration cannot be completed successfully before the timer reaches 0.

[0190] Therefore, when the mobile phone detects that a user is browsing the reservation and number-grabbing service page, it can display the corresponding creation instructions for the reservation and number-grabbing service on the page, guiding the user to create a reminder event associated with the reservation and number-grabbing service according to the creation instructions, so as to make the creation of reminder events faster.

[0191] In this embodiment, after the aforementioned reservation service is completed, there will generally be a corresponding travel scenario. For example, after securing concert tickets, there will be a concert travel event; after securing a doctor's appointment, there will be a doctor's appointment event; after securing train tickets, there will be a train travel event; and after securing scenic spot tickets, there will be a scenic spot travel event. At this time, the mobile phone can create a travel-related reminder event based on the reservation event.

[0192] After the aforementioned booking service is completed, the phone will typically receive a text message or push notification from an application, or the user may manually record the trip in a memo or similar file. The phone can then read information from text messages, photo galleries, memos, emails, etc., to identify travel-related information and generate corresponding travel reminders.

[0193] Taking a medical appointment booking scenario as an example, if the booking is successful, the phone will create a corresponding travel reminder upon recognizing the successful booking. Please refer to [link / reference]. Figure 9 , Figure 9 This is a schematic diagram of a travel reminder interface provided in an embodiment of this application. If the SMS message contains travel information, such as a message indicating successful hospital registration, the mobile phone can recognize the information in the SMS message, such as... Figure 9 As shown in (a), the desktop card 901 corresponding to the phone's voice assistant displays the creation command 902: "Do you need me to create a text message appointment reminder?". The creation command could also be, for example: "A schedule has been detected in the text message. Do you need me to create it?".

[0194] Understandably, the language used in the creation instructions should be concise and natural; this application does not impose any restrictions on the specific content.

[0195] The phone responds to the user's touch operation on the desktop card 901, displaying on the desktop 903 as follows: Figure 9The dialog interface 904 corresponding to the personalized assistant (also known as a personal reminder assistant) shown in (b) is as follows. In the dialog interface 904, the personalized assistant first provides a creation instruction, as well as the specific content of the identified text message. Then, several associated creation instructions 905 are displayed below the specific content of the text message. For example, if the specific content of the text message is a reminder for an appointment for a physical examination at a certain hospital, then the associated creation instructions corresponding to this creation instruction could include: create a schedule reminder for me; remind me to fast on that day; more information about the hospital.

[0196] The phone can respond to the user's touch operation on the desktop card corresponding to the voice assistant to enter the voice assistant's dialogue interface, or it can directly enter the dialogue interface of the personalized assistant in the voice assistant.

[0197] Then, in response to the user's selection of a certain association creation command, the phone will... Figure 9 As shown in (c), the association creation command is sent directly in the dialog interface 904. The phone's personal assistant then responds to the content of the association creation command and creates a related reminder. For example, if the user selects the association creation command as: "Create a schedule reminder for me," the phone's personal assistant will create a schedule reminder related to a physical examination appointment based on the association creation command and reply as follows: Figure 9 The feedback statement shown in (c) is 906.

[0198] In the feedback statement 906, there is also a corresponding schedule card 907 for the created reminder. Card 907 displays appointment information, such as: Wednesday; Annual physical examination scheduled at xx hospital, 8:30-9:00.

[0199] Under card 907, the corresponding association creation instruction 908 is also displayed. For example: Remind me to book a car before departure; help me create an early morning alarm for the day.

[0200] It's understandable that the type of card displayed in the chat interface depends on the type of reminder created. For example, if a calendar reminder was created, the response would be a calendar card. If the reminder didn't specify a type, the response would also be a card corresponding to the service delivery method for that reminder event, such as... Figure 9 As shown in (d), the creation command sent in dialog interface 904 is: Create a reminder for me. Assuming the service provided by this reminder is desktop notification, the response will be notification card 909.

[0201] Therefore, when a mobile phone recognizes a travel event, it can proactively create a corresponding creation command to guide the user to create a reminder for the travel event, making reminder creation faster.

[0202] In this embodiment, for the scenario where the mobile phone identifies travel events in the photo library and guides the creation of reminders, please refer to [reference needed]. Figure 10 The image shown is a schematic diagram of a travel reminder interface. Taking visiting a certain organization as an example, if the phone has an invitation letter from that organization stored in its photo library, the phone can recognize the information in the photo library, such as... Figure 10 As shown in (a), the desktop card 1001 corresponding to the voice assistant on the mobile phone can display the creation instruction 1002: "Do you need me to create a picture calendar reminder for you?". The creation instruction 1001 can also be, for example: "A calendar has been detected in the gallery. Do you need me to create one for you?".

[0203] The phone responds to the user's touch operation on the desktop card 1001, displaying the following on the desktop 1003: Figure 10 The personalized assistant's dialogue interface 1004 is shown in (b). In dialogue interface 1004, the personalized assistant first provides a creation instruction, as well as the specific content of a recognized image from the gallery. Then, several associated creation instructions 1005 are displayed below the image. For example, if the image content is an invitation from a certain organization, then the associated creation instructions could include: "Create a schedule reminder for me"; "Introduction to the surrounding area of ​​this organization's address".

[0204] Then, in response to the user's selection of a certain association creation command, the phone will... Figure 10 As shown in (c), the association creation command is sent directly in the dialog interface 1004. The phone's personalized assistant then responds to the content of the association creation command and creates a related reminder. For example, if the user selects the association creation command as: "Create a schedule reminder for me," the phone's personalized assistant will create a schedule reminder related to visiting a company based on the association creation command and reply as follows: Figure 10 The feedback statement shown in (c) is 1006.

[0205] In addition to the feedback statement 1006, there is also a schedule card 1007 corresponding to the created reminder. The schedule card 1007 displays appointment information, such as: Wednesday; visiting unit x, unit address; 8:30-9:00.

[0206] Under card 1007, the corresponding association creation instruction 1008 is also displayed. For example: remind me to book a car before departure; remind me to bring contract documents before departure.

[0207] Therefore, when a mobile phone recognizes a travel event, it can proactively create a corresponding creation command to guide the user to create a reminder for the travel event, making reminder creation faster.

[0208] In this embodiment, the mobile phone can also respond to the user's pressing operation on the global navigation bar at the bottom of the application interface, actively wake up the voice assistant, and then trigger the voice assistant to recognize the screen and guide the creation of related reminder events.

[0209] Please see Figure 11 , Figure 11 This is a schematic diagram of an interface for guiding the creation of travel reminders, provided as an embodiment of this application. Figure 11 As shown in (a), the phone responds to the user's press operation on the global navigation bar 1102 at the bottom of the SMS interface 1101, activating the voice assistant. Figure 11 As shown in (b), the bottom of the SMS interface 1101 displays the voice assistant's input box 1103. At this time, the voice assistant recognizes the SMS content on the current page and displays the generated creation command in the input box 1103. For example, if the phone recognizes that the SMS content on the current page is a physical examination appointment information, and the physical examination appointment information includes the physical examination time of January 7, then the creation command generated based on time and event can be: "Remind me to have a physical examination on January 7".

[0210] Then, the phone can respond to the user's sending of the creation command by creating a reminder event.

[0211] Therefore, the phone identifies the content on the current page at the application layer and generates a creation instruction based on the page recognition result, guiding the user to create a reminder event.

[0212] In this embodiment, in addition to recognizing travel events, the mobile phone can also proactively generate corresponding creation instructions after recognizing certain events that require further action. Examples include cancellation reminders for continuous annual / monthly subscriptions and automatic renewal cancellation reminders.

[0213] If the phone detects a user's payment confirmation for a continuous monthly subscription to a video streaming service, it can guide the user to create a cancellation reminder. For example, ... Figure 12 As shown in (a), the mobile phone recognizes that the current page is a payment confirmation interface 1201 for a continuous monthly subscription. At this time, the global navigation bar 1202 at the bottom of the payment confirmation interface 1201 flashes. Figure 12 As shown in (b), after the phone responds to the press operation on the global navigation bar 1202, the voice assistant input box 1203 is displayed on the payment confirmation interface 1201. The input box 1203 displays the creation instruction 1204: "Remind me to cancel the day before the renewal".

[0214] If the phone recognizes a user's payment confirmation for a continuous annual subscription to a video streaming service, the phone can guide the user to create a cancellation reminder for the continuous subscription. For example, if... Figure 12As shown in (c), the mobile phone recognizes that the current page is the payment confirmation interface 1205 for a continuous annual subscription. At this time, the global navigation bar 1206 at the bottom of the payment confirmation interface 1205 flashes. Figure 12 As shown in (d), after the phone responds to the press operation on the global navigation bar 1206, the voice assistant input box 1207 is displayed on the payment confirmation interface 1205. The input box 1207 displays the creation instruction 1208: "Remind me to cancel the day before the renewal".

[0215] Then, in response to the sending of the creation command, the phone creates the corresponding notification event. After the notification event is created, such as... Figure 12 As shown in (e), the basic information of the reminder event can be displayed on the mobile phone's desktop card 1209: remind me to cancel the continuous annual / monthly subscription one day before the renewal.

[0216] Generally speaking, when traveling, you need to carry certain items to complete the trip. For example, when visiting a scenic spot, you need to carry your ID card; when traveling for business, you need to carry contracts and other documents; when visiting a hospital, you need to carry your ID card or social security card, etc.

[0217] Therefore, this application can collectively refer to the aforementioned situations as "travel-related item carrying scenarios." For these scenarios, there are corresponding item carrying reminders.

[0218] The following section details the method for creating the aforementioned item reminder in this solution.

[0219] II. Items to Bring Reminder

[0220] First, regarding the scenarios of carrying items while traveling, they can be divided into two categories: traveling to other places and traveling locally, which will be introduced separately below.

[0221] For scenarios involving carrying luggage while traveling to different locations, mobile phones can recommend items that may be needed based on the user's flight, train, or other ticket orders, combined with the user's basic personal information (such as gender and age), and generate creation instructions to guide the user to create a reminder for carrying items.

[0222] Please see Figure 13 , Figure 13 This is a schematic diagram of an interface for identifying associated events and guiding the creation of reminders, provided as an embodiment of this application. For example... Figure 13 As shown in (a), the mobile phone desktop display includes two cards. One card 1301 displays flight information, and the other card corresponds to the voice assistant card 1302, which displays the creation command 1303 generated by the mobile phone based on the flight information: "Remind me to bring my ID card before the business trip".

[0223] The mobile phone can respond to the user's selection of card 1302 by the voice assistant and display, as shown below. Figure 13 The voice assistant's dialogue interface 1304 is shown in (b). The creation command 1303 is directly displayed in the input box of the dialogue interface. In response to the user's selection operation on the send control 1305, the mobile phone directly sends the creation command 1303 from the input box.

[0224] At this point, after the voice assistant creates the corresponding reminder, such as Figure 13 As shown in (c), the voice assistant responds with feedback statement 1306 and the corresponding card 1307 for the created reminder. The voice assistant also responds with associated creation instructions 1308. For example: reminding me to book a car before departure; reminding me to reply to emails after landing.

[0225] Thus, by recognizing related events, the mobile phone generates creation instructions to guide users in creating relevant reminders, ultimately achieving reminders for personal items carried.

[0226] For local travel scenarios, mobile phones can also guide users to create associated reminders based on the recognized travel events. For example, if the phone recognizes a trip to a park, it can guide the user to create associated reminders, such as recommended items to bring for the park trip. If the phone recognizes a commute to work, it can guide the user to create reminders about items to bring for the commute.

[0227] Taking commuting to work as an example, a mobile phone can identify the day's weather information and then generate a reminder, such as: "Remember to bring an umbrella before leaving for work," guiding the user to create a corresponding reminder. Figure 14 As shown in (a), the phone recognizes that it is a weekday and that it will rain that afternoon. Therefore, the phone's voice assistant's corresponding desktop card 1401 can display the aforementioned creation command 1402: "Remember to bring an umbrella before leaving for work." Then, as... Figure 14 As shown in (b), in response to the user's touch operation on the desktop card 1401, the mobile phone displays the voice assistant's dialogue interface 1403. The aforementioned creation command 1402 is directly displayed in the input box 1404 of the dialogue interface 1403. In response to the user's selection operation on the send control 1405, the mobile phone sends the creation command 1402. At this time, the mobile phone's voice assistant creates the corresponding reminder according to the creation command.

[0228] In summary, in the method provided by the embodiments of this application, the mobile phone can actively identify the target scene, display the creation instruction, thereby guiding the user to create a reminder event associated with the target scene, and can display the reminder event in the mobile phone in a specified manner.

[0229] In the scenarios described above, besides the phone's background self-checking and proactively identifying reminders in system applications and generating creation instructions, if the phone identifies reminders in system applications browsed by the user, it will also proactively perform page recognition and generate creation instructions. For example, if the phone recognizes that the user has viewed a successful appointment SMS, a screenshot of an appointment visit, or a ticket purchase email, it will prompt the user whether to generate a reminder event and can generate creation instructions based on the page recognition results.

[0230] Understandably, users are unaware of the process of creating the self-check system application.

[0231] In this embodiment, we will now describe how the mobile phone responds to user actions and creates associated reminder events based on the creation requirements of different scenarios.

[0232] The phone can activate the voice assistant in response to user actions. For example, the phone can activate the voice assistant by pressing the power button or by pressing the global navigation bar. After activating the voice assistant, the phone can display the voice assistant's input box on the current page.

[0233] like Figure 15 As shown in (a), after the phone wakes up the voice assistant, the voice assistant's input box 1501 is displayed at the bottom of the phone's desktop. The phone can input the creation command through the user's voice input or manual keyboard input. Then, in response to the user's touch operation on the send control 1502, the phone sends the creation command and creates the reminder corresponding to the creation command.

[0234] For example, if the input box says, "Remind me to bring my contract before my business trip," then the phone will create a reminder event and notify the user using the appropriate reminder method based on the event type. For instance, the "bring contract" reminder event could correspond to a desktop card, in-capsule notification, or a capsule notification. Furthermore, reminder methods also have corresponding reminder types. For example, the "bring contract" reminder event might correspond to an alarm-type in-capsule notification, meaning that the reminder will be sent to the user via both an in-capsule notification and an alarm.

[0235] It should be noted that in this embodiment, the instructions actively generated by the mobile phone are called creation instructions, and the instructions actively entered by the user are also called creation instructions. In fact, the content of creation instructions can be the same as that of creation instructions described above.

[0236] In this embodiment, in response to a user's touch operation on the input box, the mobile phone can display a voice assistant dialogue interface 1503 on the desktop. The dialogue interface displays pagination tabs 1504. The mobile phone can enter different interfaces in response to the user's selection of pagination tabs 1504. For example, ... Figure 15 As shown in (b), in response to the user's selection of the "Conversation" tab, the mobile phone displays the interface corresponding to that tab. The detailed page corresponding to "Conversation" displays various agent options. When the user selects a specific agent option, the mobile phone can enter the conversation interface corresponding to that agent and interact with that agent.

[0237] The voice assistant can be equipped with various intelligent agents, each employing different technologies and algorithms to accurately grasp and quickly respond to user needs. For example, the intelligent agents within a voice assistant could include a personalized assistant, a "My Time Capsule" assistant, a smart travel assistant, a sports and health assistant, a user assistant, a news and information assistant, and a smart office assistant.

[0238] Generally, in this embodiment, the creation of reminder events is initiated through a dialogue with the personalized assistant.

[0239] Please see Figure 16 , Figure 16 This is a schematic diagram of an interface for proactively creating reminders through a personalized assistant, provided as an embodiment of this application. For example... Figure 16 As shown in (a), the mobile phone responds to the user's selection of the personalized assistant in the corresponding interface 1601 of the dialogue, and enters as follows Figure 16 The personalized assistant's dialogue interface 1602 is shown in (b). In the dialogue interface 1602, introductory information 1603 is displayed, indicating the creation command to be entered by the user, so that the creation command can meet the conditions for creating a reminder on the mobile phone. The introductory information 1603 may be, for example: "You can ask me to remind you of things you need to remember based on time, location, etc."

[0240] The phone can respond to the user's voice or text input in input field 1604, creating a reminder event based on the sent creation command. Alternatively, the phone can also respond to the user's direct selection of the associated creation command 1605 ("Remind me to reply to the email after landing"), such as... Figure 16 As shown in (c), the association creation instruction 1605 is directly displayed in the input box 1604. The mobile phone can respond to the user's sending operation on the sending control 1606, and after sending the association creation instruction 1605, create a notification event.

[0241] In this embodiment, the user-input creation command can also be divided into single-task commands and complex-task commands. A single-task command means that the reminder created based on the command is singular, while a complex-task command means that more than one reminder is created based on the command. Please refer to [link / reference]. Figure 17 , Figure 17 This is a schematic diagram of a dialog interface for creating a reminder, provided as an embodiment of this application. Figure 17 As shown in (a), the user sends a single creation instruction 1701: "Remind me to order a cake the day before my mother's birthday." In this case, the phone only needs to create a single reminder and reply with the card 1702 corresponding to the cake-ordering reminder at the bottom of the chat interface. For example... Figure 17 As shown in (b), the user's creation instruction 1703 is a complex instruction, specifically: "Remind me to bring the contract documents and medicine the night before my business trip, and help me book a car." At this time, the phone needs to create two reminders and reply with two cards at the bottom of the chat interface, including card 1704 corresponding to the reminder to bring the contract documents and medicine, and card 1705 corresponding to the reminder to book a car.

[0242] Therefore, this application can also create corresponding reminder events for complex scenarios through simple creation commands.

[0243] III. Task Reminders

[0244] In this embodiment, for routine task to-do scenarios, the mobile phone typically proactively creates a reminder event in response to the user's actions. Routine task to-do scenarios can be categorized into four types: alarm clock scenarios, home security scenarios, medical and health scenarios, and missed call scenarios.

[0245] Missed calls can include missed video calls, missed voice calls, and missed incoming mobile calls.

[0246] Taking a missed video call as an example, this section illustrates the interface diagram of a mobile phone proactively creating a reminder event in response to a user's action. For example... Figure 18 As shown in (a), after the phone activates the voice assistant on the desktop, the phone can respond to the user's input by entering a creation command 1802 in the voice assistant's input box 1801: "Remind me if I miss a video call from contact 1." Then, the phone can create a reminder event based on this creation command 1802. Subsequently, if a video call from contact 1 is missed, the user can be notified of the missed call using the reminder method corresponding to this event. For example, as... Figure 18 As shown in (b), contact 1 sent a video call request, as Figure 18As shown in (c), the phone recognizes that a video call from contact 1 was missed. Therefore, the phone can display a reminder event on the desktop card 1803, with basic information 1804 stating: "Missed video call from contact 1," as shown below. Figure 18 As shown in (d).

[0247] In this embodiment, the mobile phone can also generate corresponding creation instructions based on the user's behavioral habits after learning these habits. For example, in the scenario of missed calls, the phone can recognize that the user will call back each time they miss a call from contact 1. The phone can pre-set a preset number of times for the behavior; once the preset number of times a behavior is detected, the phone creates a corresponding reminder event for that behavior. For example, if the phone recognizes that the user has missed three consecutive calls from contact 1 and will call back each time, then after activating the voice assistant, the phone can display the generated creation instruction in the input box: "Remind me to call back contact 1 after missing a call."

[0248] The aforementioned user behavior information also includes frequently created reminder events. For example, a user might frequently visit the ticket booking page for a concert by celebrity X, and the electronic device would recognize this scenario and display a creation command to generate a corresponding reminder event for that concert's ticket booking. The phone can then periodically obtain information about the concert. If it detects that ticket booking is about to begin, it can proactively display a creation command on the home screen card: "A concert by celebrity X has been detected on October 1st. Do you want to be reminded to book tickets?"

[0249] For example, if a user proactively creates a reminder to go to the library at the beginning of each month, then after the phone learns this behavioral habit, it can subsequently display a reminder on the home screen card at the end of each month: "Remind you to go to the library at the beginning of the month".

[0250] Understandably, once a user's behavior reaches a set number of times, it can be stored as habit information on the phone, allowing the phone to learn these habits. For example, the user may have attended a concert by celebrity X twice, or proactively created a reminder to go to the library at the beginning of the month three times. This application does not impose a limit on the number of times this behavior can be set.

[0251] In this embodiment, if the user's input creation command has a problem, the phone cannot create the corresponding reminder event based on the input creation command. For example, if the user's input creation command includes a reference to a frequently used address, the phone may not be able to obtain the specific address, resulting in the inability to successfully create the reminder event. Alternatively, if the user's input creation command includes a vague address, the phone will also be unable to support creating reminder events for vague addresses. Or, if the user's input creation command includes a vague time, the phone will create the reminder event based on the phone's default time setting.

[0252] Please see Figure 19 , Figure 19 This is a schematic diagram of a dialogue interface for a mobile phone's voice assistant, provided as an embodiment of this application. Figure 19 As shown in (a), in the voice assistant's dialogue interface 1901, the currently entered creation command 1902 is: "Remind me to clock in when I'm near the company." If the phone fails to obtain the company address, or if obtaining the company address is slow, the voice assistant can guide the user to manually add or voice-input the company address.

[0253] The voice assistant can also respond to the personal information entry link 1903, guiding users to complete their personal information so that the phone can directly recognize frequently used addresses in the future.

[0254] It should be noted that the phone will only prompt the user to manually add or voice-enter frequently used addresses if it has not yet obtained the home, office, or other frequently used addresses.

[0255] like Figure 19 As shown in (b), the creation instruction 1905 displayed in the input box 1904 at the bottom of the phone is: Remind me to buy breakfast at the subway station. The phone responds to the user's touch operation on the input box 1904 by displaying the following... Figure 19 The dialogue interface 1906 of the voice assistant is shown in (c). At this time, the creation command is sent in the dialogue interface 1906. Because the entered address is ambiguous, the phone cannot recognize it, and the voice assistant can intelligently respond accordingly. Additionally, the voice assistant replies with guidance information 1907 to prompt the user on how to correctly input the statement. The phone can proactively generate and display the associated creation command 1908 based on the guidance information.

[0256] like Figure 19 As shown in (d), the creation instruction 1910 displayed in the input field 1909 at the bottom of the phone is: Remind me to take my medicine tomorrow. The phone responds to the user's touch operation on the input field 1909 by displaying the following... Figure 19The voice assistant's dialogue interface 1911 is shown in (e). At this time, the creation command is sent in dialogue interface 1911. Since the input is a vague time, the phone can generate a corresponding reminder based on the default set time, such as 8:00 AM. The reminder content in the card 1912 that the voice assistant replies is: "Remind me to take my medicine at 8:00 AM tomorrow." Below the card 1912 corresponding to the reminder, two additional association creation commands 1913 are also displayed, such as: "Remind me to take my medicine after dinner tomorrow" and "Remind me to take my medicine before bed tomorrow." Thus, the phone can also respond to the user's selection of association creation commands and create reminder events.

[0257] In this embodiment, if the location in the user-input notification event is vague, the voice assistant can obtain the specific address through continuous dialogue. For example, after receiving a vague address, the voice assistant can ask follow-up questions about the location. Figure 20 As shown in (a), the creation command 2002 displayed in the input box 2001 at the bottom of the phone is: Remind me to buy breakfast when I get to the subway station. In response to the touch operation on the input box 2001, the phone displays the voice assistant's dialogue interface 2003, as follows... Figure 20 As shown in (b), the voice assistant further inquires about the specific subway station. Alternatively, if the phone's personal information stores subway stations as frequently used addresses, then, as... Figure 20 As shown in (c), the voice assistant further inquires whether it is a frequently visited subway station 1. Or, as... Figure 20 As shown in (d), the user further inputs a creation instruction 2004 based on the detailed location of the subway station, and the mobile phone can accurately locate and match based on this detailed address.

[0258] In this embodiment, the voice assistant will respond to each sent reminder statement. If the phone recognizes that the reminder statement meets the creation conditions, the phone will successfully create the reminder, and the voice assistant will reply that the reminder has been created, along with the card information generated by the reminder. If the phone recognizes that the reminder statement does not meet the creation conditions, the phone will not create the reminder, the voice assistant will reply that creation is not supported, and will prompt the user on how to create a reminder.

[0259] In this embodiment, after a reminder is successfully created, the mobile phone generates a corresponding card. The content displayed on the card may include a card title, a condition description, a reminder content, and a reminder event. The condition description includes time, location, and weather. For example, the card title could be "Personalized Assistant," the condition description could be "About to leave, remember to bring your things," the reminder content could be a contract document, and the reminder event could be "Tomorrow at 8:00 AM."

[0260] Cards can be divided into desktop cards and cards used for replies within the voice assistant's dialogue interface. Single desktop cards can be 2x2, 2x1, or 4x2 in size. Card specifications usually refer to the card's dimensions; for example, a 2x1 card means its width is twice that of a certain unit (such as centimeters or pixels), and its height is once that of a certain unit. Figure 21 As shown in (a), the 2*2 desktop card 2101 includes a card title (Smart Task), a condition description ("Leaving soon, remember to bring your things"), reminder content (contract documents and medicine), and reminder event (8:00 AM tomorrow). The 2*1 desktop card 2102 includes a condition description ("Leaving soon, remember to bring your things") and reminder content (contract documents and medicine). The 4*2 desktop card 2103 includes a card title (Smart Task), a condition description ("Leaving the day after tomorrow, remember to bring your things"), reminder content (contract documents and medicine), and reminder event (8:00 AM tomorrow).

[0261] like Figure 21 As shown in (b), the specifications of a single card in the voice assistant can be 3*2. The 4*2 desktop card 2104 includes a card title (Smart Task), a condition description ("Arriving near the supermarket, remember to buy"), a reminder content (batteries and green onions), and a reminder event (tomorrow at 8:00).

[0262] In this embodiment, the mobile phone can also edit the pre-created cards replied to by the voice assistant in response to the user's operation. For example... Figure 22 As shown in (a), in the voice assistant's dialogue interface 2201, an editing control 2203 is displayed for the pre-created card 2202 that the voice assistant replies with. The mobile phone can respond to the user's touch operation on the editing control 2203 in the card, entering the card's editing mode, i.e., displaying... Figure 22 The editing page 2204 is shown in (b). Alternatively, the mobile phone can trigger the card's editing mode in response to a user's touch operation on any area of ​​the card 2202.

[0263] like Figure 22 As shown in (b), the currently edited card 2205 is displayed on the card editing page 2204. The reminder content of the created reminder event displayed in the currently edited card 2205 is: You are about to go on a business trip. Please bring your ID card.

[0264] The card editing page 2204 also displays an input box 2206, which shows the creation instructions corresponding to the aforementioned created reminder events, namely: Remind me to bring my ID card before my business trip. Among them, "Remind me" is a fixed input word and cannot be edited; "before my business trip" and "bring my ID card" are editable words.

[0265] The phone responds to the user's editing actions, such as Figure 22As shown in (c), the text "Bring ID card" in the input box has now been edited to "Bring medicine" 2207. Therefore, the original reminder content in card 2205 can be struck out. Then, in response to the user's sending operation on the send control 2208, the mobile phone changes the reminder content to the content sent from the input box.

[0266] like Figure 22 As shown in (d), the edited creation instruction 2209 displayed on the card's editing page 2204 is: Remind me to bring my medication before my business trip. Therefore, the reminder content in card 2210 is modified to: I am about to go on a business trip; please remember to bring your medication.

[0267] The mobile phone can also respond to the user's operation on the instruction editing control 2211 to edit and create instructions 2209.

[0268] like Figure 22 As shown in (d), the card editing page 2204 also displays a control 2212 for deleting the reminder and a control 2213 for saving the edit. The mobile phone can respond to the user's selection operation of the control 2212 for deleting the reminder to delete the reminder, or respond to the user's selection operation of the control 2213 for saving the edit to save the current edit.

[0269] If the phone responds to the selection operation of the cancel control 2214, then the following will be displayed: Figure 22 Page 2215 is shown in (e). Page 2215 includes a reminder message 2216: Have you saved the currently edited content?, as well as an exit control 2217 and a save control 2218. The phone can directly exit the editing mode in response to the user's selection of the exit control 2217. Alternatively, the phone can save and exit the editing mode in response to the user's selection of the save control 2218. After exiting the editing mode, the voice assistant will refresh the currently created reminders.

[0270] like Figure 22 As shown in (f), after saving the card edited this time, the voice assistant's dialogue interface 2201 refreshes to display the newly edited card 2219.

[0271] In this embodiment, in addition to modifying the overall service provision method in the service management interface of the voice assistant, the service provision method (reminder method) of a single card can also be modified in the card editing mode of the voice assistant's dialogue interface.

[0272] like Figure 23As shown in (a), an expansion control 2301 for reminder methods is displayed in the card editing mode. The default reminder methods include notifications, desktop cards, and capsules. In response to the user's touch operation on the expansion control 2301, the phone expands to display icons for various reminder methods and selection controls for each method.

[0273] like Figure 23 As shown in (b), the selection controls 2302 corresponding to notifications, desktop cards, and capsules are all selected. The mobile phone can respond to the check or decheck operation of the selection operation and select the corresponding reminder method.

[0274] The phone can also respond to the user's swipe gestures by displaying options for more notification methods, such as... Figure 23 As shown in (c), there is a switch control 2303 for the important reminder and an option control 2304 for repeat. Here, "repeat" indicates the repeating method for the reminder event. In this case, the option for repeat is "do not repeat," meaning the reminder created this time will not be repeated. The mobile phone responds to the user's touch operation on the option control 2304 for repeat, as follows... Figure 23 As shown in (d), several optional repetition modes 2305 are displayed. Among them, the repetition mode can include no repetition, daily, weekly, monthly, yearly, lunar yearly, and custom.

[0275] The phone can respond to the user's selection of different repeat modes using the corresponding selection controls, switching the repeat mode accordingly. Alternatively, the phone can also respond to the user's selection of the cancel control, canceling the editing of the repeat mode.

[0276] The phone can also respond to user manual actions to delete created notifications. For example... Figure 24 As shown in (a), the dialog interface 2401 displays multiple cards corresponding to created reminders, which are in a collapsed state. In response to the user's swipe operation on the first card 2402, the phone displays the delete interface 2403. As... Figure 24 As shown in (b), the prompt message 2404 displayed on the deletion interface 2403 is: "Delete this reminder?", along with a cancel control 2405 and a confirm delete control 2406. Thus, the mobile phone can delete the reminder in response to the user's selection of the confirm delete control 2406.

[0277] like Figure 24 As shown in (c), in response to the user's press operation on the first card 2402, the mobile phone displays the delete control 2407. The mobile phone can also respond to the user's selection operation on the delete control 2307, displaying... Figure 24The deletion interface 2408 is shown in (d). The coral-colored interface 2404 displays the same content as the deletion interface 2408; similarly, the phone can delete this notification in response to the user's selection of the confirmation deletion control.

[0278] After you confirm the deletion of the reminder, the voice assistant will refresh the display of currently created reminders. For example... Figure 24 As shown in (e), the card displayed in the voice assistant's dialogue interface 2401 is the card 2409 following the first card 2402.

[0279] In this embodiment, the mobile phone can also edit created reminders by conversing with a voice assistant. For example... Figure 25 As shown in (a), the creation command 2502 sent in the personalized assistant's dialogue interface 2501 is: "Remind me to bring my ID card before my business trip." The phone creates a reminder event based on this creation command and replies with the card 2503 corresponding to the reminder event. At this time, as... Figure 25 As shown in (b), the mobile phone can respond to the user-sent creation command 2504: change the reminder to include contract documents, and modify the reminder content in the reminder event. Figure 25 As shown in (c), at this point, the reminder in card 2505 changes to: "Remind me to bring the contract before my business trip." And, as... Figure 25 As shown in (c), the phone can also respond to the user's input creation command 2506: Delete this reminder, delete the currently created reminder.

[0280] Therefore, the phone can respond to a user's single sentence and directly edit the reminder that has already been created.

[0281] If the user's entered reminder message is outside the allowed range, the phone will be unable to create the reminder. For example, ... Figure 25 As shown in (d), the user's input creation command 2507 is: "Change to remind me to buy groceries at the supermarket." Since the supermarket is a vague address, the phone cannot recognize it. Therefore, after receiving the above creation command from the user, the voice assistant will reply on the current dialogue interface with a reminder that this location is not supported, along with the conditions for creating a reminder, to help the user input a reminder statement that meets the conditions.

[0282] After a notification event is created, the mobile phone provides an immediate notification based on the service delivery method corresponding to that event. For example, ... Figure 26 As shown in (a), taking the reminder content as "I am about to go on a business trip, please bring your ID card" as an example, after the mobile phone creates the corresponding reminder event, the content of the reminder event can be displayed in the form of desktop card 2601 to remind the user in an instant.

[0283] Or, such as Figure 26As shown in (b), the phone displays a brief description of the notification event above the photo app interface in capsule form (2602). Generally, when a notification is sent in capsule form, the strings within the capsule are displayed in a carousel, creating a scrolling effect. For example... Figure 26 As shown in (b), capsule 2602 may include a task name (Voice Assistant Accompanying You on Your Trip) and a reminder (Reminder to Bring Your ID Card). The positions of "Voice Assistant" and "Reminder" correspond and are displayed in a loop at the same location, as do the positions of "Accompanying You on Your Trip" and "Reminder to Bring Your ID Card."

[0284] The mobile phone can respond to the user's touch operation on the capsule 2602, displaying, for example... Figure 26 (c) shows an enlarged capsule 2603. The enlarged capsule 2603 displays the specific details of the notification event. The content displayed in the enlarged capsule 2603 may be the same as the content displayed on the desktop card.

[0285] Different types of notification events correspond to different reach levels, and different reach levels correspond to different reach methods. The higher the reach level, the more types of reach methods are available. Here, reach method refers to the service delivery method.

[0286] For example, if the reach level of a train ticket purchase reminder is high, the corresponding service delivery methods could be desktop cards, capsules, in-capsule notifications, general notifications, or lock screen notifications. If the reach level of a reminder to bring water to a scenic spot is low, the corresponding service delivery methods could be limited to desktop cards and in-capsule notifications.

[0287] The phone has a default reach level, or default reach method, for each type of notification event. The phone can modify the reach method for each type of notification event in response to user actions.

[0288] In this embodiment, as Figure 27 As shown in (a), the voice assistant's dialogue interface also includes a more control 2701. In response to the user's selection of the more control 2701, the phone displays as shown... Figure 27 The control 2702 corresponding to the personal center shown in (b) is displayed on the mobile phone in response to the user's selection operation on the control 2702 corresponding to the personal center. Figure 27 The personal center page 2703 is shown in (c). The personal center page 2703 includes personal smart reminders and memory information. The phone responds to the user's touch operation on the viewing control 2704 corresponding to the personal smart reminder, and enters... Figure 27The personalized assistant's dialogue interface 2705, shown in (d), allows users to view cards for all created reminder events. These cards are typically in a collapsed state, meaning only the reminder content from one card is displayed, with the rest folded away. The phone can respond to the user's action on the collapse control 2706 at the bottom of the first card, directly unfolding all cards to display them. The cards can be sorted according to the time of the upcoming event.

[0289] Additionally, the user center page (page 2703) also displays cards for created reminder events. Due to limitations of the mobile interface, the user center page may not be able to display the content of all created reminder times. The phone can respond to the user's swipe gesture, allowing them to swipe to view more created reminders.

[0290] Among them, the personal center page 2703 can store personal information such as filled-in data and address in the memory information, which can be viewed and edited by users.

[0291] In this embodiment, the mobile phone can respond to the user's input operation and pre-fill personal information in the memory information so that it can be directly retrieved when the mobile phone creates a reminder later.

[0292] In this embodiment, in addition to viewing all created reminders from the personal center page, users can also interact with the voice assistant, for example, as shown below. Figure 28 As shown, the creation command 2802 sent in the voice assistant's dialogue interface 2801 is: What reminders do I have this week? The voice assistant will then reply with a list of reminders for this week.

[0293] In this embodiment, after creating a reminder, the phone can also sync the reminder content to the calendar. For example... Figure 29 As shown in (a), after the phone creates a reminder, the voice assistant's dialogue interface 2901 will reply with a card 2902 corresponding to the reminder, which includes the basic information of the reminder. This basic information includes the reminder content and reminder time; for example, the reminder content is "I have booked an annual physical examination at xx hospital," and the reminder time is 8:00 AM tomorrow. Below the card 2902, several association creation commands are also provided, such as: sync this reminder to my calendar; remind me to book a car before I leave; set an early alarm for me. In response to the user's selection of association creation command 2903 "sync this reminder to my calendar," the phone can send association creation command 2903 to the voice assistant, and the phone will then sync the reminder event to the calendar based on this command.

[0294] After syncing this reminder event to the calendar, as follows Figure 29As shown in (b), the voice assistant's dialogue interface will also reply with the calendar's corresponding schedule card 2904, which displays the content of this reminder event.

[0295] Therefore, the phone can determine whether to sync reminders to the calendar based on the user's choice, avoiding duplicate reminders caused by directly syncing the calendar.

[0296] In this embodiment, the reminder settings on the phone are linked to the settings in the voice assistant. If the service provision method setting is unchecked in the voice assistant's service management interface on the phone, the corresponding reminder setting in the card editing mode within the voice assistant will also be unchecked. Figure 30 As shown in (a), if the selection control 3001 corresponding to the desktop card set in the service management interface is unchecked, then as shown in (a), Figure 30 As shown in (b), the selection control 3002 corresponding to the desktop card set in the voice assistant reminder method editing will also be unchecked.

[0297] However, if a certain reminder method is unchecked in the voice assistant, it will not affect the selection of the corresponding service provision method in service management.

[0298] In this embodiment, after the phone creates a reminder, if it detects that the switch control corresponding to the voice assistant in the phone settings is turned off, it can display a jump entry to the settings interface in the voice assistant's dialogue interface. For example... Figure 30 As shown in (c), after the user touches the input box 3003 on the desktop to wake up the voice assistant, the phone responds to the user's touch operation on the input box 3001 and displays as shown in (c). Figure 30 The voice assistant's dialogue interface 3004 is shown in (d). At this time, after the phone creates a corresponding reminder based on the user's creation command 3005, it replies in the dialogue interface that a reminder has been created. Also, if the phone detects that the voice assistant's service switch is off, it replies in the dialogue interface that the service switch is off and prompts the user on how to turn the corresponding voice assistant service switch on. For example, as... Figure 30 As shown in (d), the voice assistant interface displays a jump entry 3006 to the corresponding service management interface (e.g., Smart Assistant Application - Intelligent Recommendation Service - Voice Assistant). In response to the user's touch operation on jump entry 3006, the phone directly jumps to the voice assistant's service management interface. At this time, the phone can also respond to the user's on / off operation of the corresponding switch control for the voice assistant, enabling the voice assistant's settings.

[0299] Similarly, if the phone recognizes that the user agreement for the voice assistant is closed after creating a reminder, it can display a jump entry to the user agreement interface within the voice assistant's dialogue interface, allowing the user to directly access the user agreement interface to perform related operations. For example... Figure 30 As shown in (e), after the phone creates the corresponding reminder based on the user's creation command 3005, it replies in the chat interface that the reminder has been created. After the phone recognizes that the user agreement has been unchecked by the voice assistant, the voice assistant replies that it has recognized the unchecked user agreement and displays a jump entry 3007 (e.g., Smart Assistant Application - Intelligent Recommendation Service - User Agreement) below. The phone responds to the user's touch operation on this jump entry and directly jumps to the user agreement interface. At this time, the phone can respond to the user's check operation on the corresponding selection control of the user agreement, allowing the user to agree to the voice assistant's user agreement.

[0300] In this embodiment, the mobile phone can also select different intelligent agents from the voice assistant for dialogue. If a creation command is sent to a third-party intelligent agent, the mobile phone cannot execute the command. Figure 31 As shown in (a), in the dialogue interface 3101 of the smart travel assistant, a creation command 3102 is sent: "Remind me to bring my ID card before my business trip." The smart travel assistant replies in the dialogue interface 3101 with a message indicating that the creation command cannot be executed. Additionally, the smart travel assistant provides a jump entry 3103 to the voice assistant's dialogue page within the dialogue interface.

[0301] The mobile phone can respond to the user's selection of the jump entry 3103 and directly enter such as Figure 31 The dialogue interface 3104 of the voice assistant is shown in (b). At this time, the personalized assistant in the voice assistant can respond to the creation command 3105 sent by the user and create a corresponding reminder event.

[0302] For voice assistants, different intelligent agents can also correspond to different functions.

[0303] For example, such as Figure 32 As shown in (a), after the trip, the desktop card 3201 corresponding to the voice assistant displays the command 3202 generated in "My Time Capsule": Today's My Time Summary. The phone responds to the user's touch operation on the desktop card 3201, entering... Figure 32 The dialogue interface 3203 of the voice assistant is shown in (b). This dialogue interface 3203 displays today's photo 3204 retrieved from the gallery, along with related inquiries about the content of today's photo.

[0304] For example, such as Figure 32 As shown in (c), if the phone detects a flight delay, the desktop card 3205 corresponding to the voice assistant displays the instruction 3206 generated by the smart travel assistant: Why is the flight delayed? The phone responds to the user's touch operation on the desktop card 3205, entering... Figure 32The voice assistant's dialogue interface 3207 is shown in (d). This dialogue interface 3207 displays specific information about the delayed flight, such as the corresponding card 3208 for the flight information and the reason for the delay 3209. The dialogue interface 3207 also displays related instructions 3210 concerning the flight delay. For example... Figure 32 As shown in (d), the aforementioned associated instruction 3210 may include: Is it too late to buy delay insurance now?; My annual flight report.

[0305] The mobile phone can also respond to the user's selection of the associated command 3211 "My Annual Flight Report" and send this command. For example... Figure 32 As shown in (e), due to the type of annual flight report, a dialogue with "My Time Capsule" is triggered. At this time, the photos related to the annual flight obtained from the gallery and the language description related to the annual flight continue to be displayed on the dialogue interface 3212.

[0306] In this embodiment, the electronic device can identify the user's creation needs in different scenarios and provide guidance services, namely, generating creation instructions to guide the user in creating related reminder events. Alternatively, the user can also proactively create related reminder events via their mobile phone based on their creation needs in different scenarios. Compared to conventional reminder creation methods, the steps are simpler. Furthermore, different reminder events can correspond to different reminder methods, making it easier to better remind the user.

[0307] like Figure 33 The diagram shows the internal software architecture of an electronic device. A layered architecture divides the software into several layers, each with a clear role and function. Layers communicate with each other through software interfaces. In some embodiments, the internal architecture of an electronic device can be divided into five layers, from top to bottom: the application layer, the application framework layer, the Android runtime (ART) and native C / C++ libraries, the hardware abstraction layer (HAL), and the kernel layer.

[0308] The application layer can include a series of application packages.

[0309] like Figure 33 As shown, the application package may include applications such as gallery, calendar, calling, maps, navigation, WLAN, Bluetooth, music, smart home, and SMS.

[0310] The application framework layer provides application programming interfaces (APIs) and a programming framework for applications in the application layer. The application framework layer includes some predefined functions.

[0311] like Figure 33 As shown, the application framework layer may include a window manager, content provider, view system, resource manager, notification manager, activity manager, input manager, etc.

[0312] A view system includes visual controls, such as controls for displaying text and controls for displaying images. View systems can be used to build applications. A display interface can consist of one or more views. For example, a display interface including a text notification icon could include views for displaying text and views for displaying images.

[0313] The notification manager allows applications to display notifications in the status bar. These notifications can be used to deliver informational messages and can disappear automatically after a short pause, requiring no user interaction. For example, the notification manager can be used to notify users of download completion or message alerts. The notification manager can also display notifications as icons or scrolling text in the top status bar, such as notifications from background applications, or as dialog boxes on the screen. Examples include displaying text messages in the status bar, emitting sounds, vibrating electronic devices, and flashing indicator lights.

[0314] The notification information in this application embodiment may include always-on display information, status bar notification information, capsule information, capsule in-capsule notification information, negative one screen card, and desktop card, etc.

[0315] The input manager can provide an input management service (IMS), which can be used to manage system inputs, such as touchscreen input, keypad input, and sensor input. IMS retrieves events from input device nodes and, through interaction with the WMS, distributes these events to the appropriate windows.

[0316] The Android runtime consists of the core libraries and the Android runtime itself. The Android runtime is responsible for converting source code into machine code. The Android runtime primarily employs ahead-of-time (AOT) compilation and just-in-time (JIT) compilation techniques.

[0317] The core library primarily provides basic Java class library functionalities, such as libraries for fundamental data structures, mathematics, I / O, tools, databases, and networking. It also provides APIs for users to develop Android applications.

[0318] Native C / C++ libraries can include multiple functional modules. Examples include: surface manager, media framework, libc, OpenGL ES, SQLite, Webkit, etc.

[0319] The Hardware Abstraction Layer (HAL) runs in user space, encapsulates kernel-level drivers, and provides calling interfaces to higher layers. The HAL includes at least a display module, an audio module, a camera module, and a sensor module.

[0320] The kernel layer is the layer between hardware and software. The kernel layer contains at least the display driver, camera driver, audio driver, and sensor driver.

[0321] Figure 34 This illustration shows a hardware structure diagram of an electronic device 100. The electronic device 100 may include at least one of the following: mobile phone, foldable electronic device, tablet computer, desktop computer, laptop computer, handheld computer, laptop, ultra-mobile personal computer (UMPC), netbook, 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, or smart city device. This application does not impose any special limitations on the specific type of the electronic device 100.

[0322] Electronic device 100 may include processor 110, external memory interface 120, internal memory 121, universal serial bus (USB) connector 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, receiver, microphone, headphone jack, sensor module 170, button 190, camera 191, display screen 192, motor, indicator, and subscriber identification module (SIM) card interface, etc.

[0323] The sensor module 170 may include pressure sensors, gyroscope sensors, barometric pressure sensors, magnetic sensors, accelerometers, distance sensors, proximity sensors, fingerprint sensors, temperature sensors, touch sensors, ambient light sensors, bone conduction sensors, position sensors, etc. The touch sensor can also collect user touch data.

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

[0325] Processor 110 may include one or more processing units, such as application processors (APs), modem processors, graphics processing units (GPUs), image signal processors (ISPs), controllers, video codecs, digital signal processors (DSPs), baseband processors, and / or neural network processing units (NPUs). These different processing units may be independent devices or integrated into one or more processors.

[0326] The processor can generate operation control signals based on the instruction opcode and timing signals to control the instruction fetching and execution.

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

[0328] In some embodiments, the processor 110 may include one or more interfaces. These 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. The processor 110 can connect to modules such as touch sensors, audio modules, wireless communication modules, displays, and cameras through at least one of these interfaces.

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

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

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

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

[0333] 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), Bluetooth Low Energy (BLE), ultra-wideband (UWB), 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.

[0334] 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 electronic devices via wireless communication technology. This wireless communication technology may include Global System for Mobile Communications (GSM), General Packet Radio Service (GPRS), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), Time Division Code Division Multiple Access (TD-SCDMA), Long Term Evolution (LTE), BT, GNSS, WLAN, NFC, FM, and / or IR technologies, 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).

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

[0336] Display screen 192 is used to display images, videos, etc. Display screen 192 includes a display panel. The display panel may be a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode (AMOLED), a flexible light-emitting diode (FLED), a miniature LED, a microLED, a quantum dot light-emitting diode (QLED), etc. In some embodiments, electronic device 100 may include one or more display screens 192.

[0337] In this embodiment, the display screen 192 can display creation instructions, desktop cards, capsules, etc.

[0338] The external storage interface 120 can be used to connect an external memory card, such as a MicroSD 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, it can save music, video, and other files to the external memory card, or transfer music, video, and other files from the electronic device to the external memory card.

[0339] Internal memory 121 can be used to store computer executable program code, including instructions. Internal memory 121 may include a program storage area and a data storage area. The program storage area may store the operating system, application programs required for at least one function (such as sound playback function, image playback function, etc.), etc. The data storage area may store data created during the use of electronic device 100 (such as audio data, phone book, etc.). In addition, 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. Processor 110 executes various functional methods or data processing of electronic device 100 by running instructions stored in internal memory 121 and / or instructions stored in memory disposed in the processor.

[0340] In this embodiment, the user's personal data, etc., can be stored in the internal memory.

[0341] The methods described in the foregoing embodiments can all be implemented in the electronic device 100 having the aforementioned hardware and software structures.

[0342] This application also provides a chip system, such as... Figure 35 As shown, the chip system 3500 includes at least one processor 3501 and at least one interface circuit 3502. The processor 3501 and the interface circuit 3502 are interconnected via lines. For example, the interface circuit 3502 can be used to receive signals from other devices (e.g., the memory of an electronic device). As another example, the interface circuit 3502 can be used to send signals to other devices (e.g., the processor 3501). Exemplarily, the interface circuit 3502 can read instructions stored in the memory and send those instructions to the processor 3501. When the instructions are executed by the processor 3501, the electronic device can perform the steps in the above embodiments. Of course, the chip system may also include other discrete devices, which are not specifically limited in this application embodiment.

[0343] This application also provides a computer storage medium that includes computer instructions. When the computer instructions are executed on the electronic device, the electronic device causes the electronic device to perform various functions or steps performed by the mobile phone in the above method embodiment.

[0344] This application also provides a computer program product that, when run on a computer, causes the computer to perform the various functions or steps performed by the mobile phone in the above method embodiments.

[0345] Through the above description of the embodiments, those skilled in the art can clearly understand that, for the sake of convenience and brevity, only the division of the above functional modules is used as an example. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above.

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

[0347] The units described as separate components may or may not be physically separate. A component shown as a unit can be one or more physical units; that is, it can be located in one place or distributed in multiple different locations. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0348] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

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

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

Claims

1. A personalized reminder method, characterized in that, Applied to electronic devices, including: In response to the electronic device recognizing a target scene, a first creation instruction is displayed on the interface of the electronic device; the target scene is a scene associated with a reminder item, and the first creation instruction is generated based on the reminder item; In response to a first operation on the first creation instruction, a first reminder event associated with the target scene is created; the first reminder event is used to remind the user to perform the reminder item associated with the target scene.

2. The method according to claim 1, characterized in that, The target scenario includes the user browsing the application interface of the first application, the reminder item being an item associated with the appointment service provided by the first application, and the application interface of the first application being associated with the browsing interface corresponding to the appointment service.

3. The method according to claim 2, characterized in that, In response to the electronic device recognizing the target scene, displaying a first creation instruction on the interface of the electronic device includes: In response to the electronic device recognizing that the user is browsing the application interface of the first application, the first creation instruction is displayed on the application interface of the first application.

4. The method according to claim 3, characterized in that, The application interface displays a global navigation bar control; in response to the electronic device recognizing that the user is browsing the application interface of the first application, the first creation instruction is displayed on the application interface of the first application, including: In response to the electronic device recognizing that the user is browsing the application interface of the first application, the global navigation bar control is flashed on the application interface. In response to a press operation on the global navigation bar control, a dialogue input box for the voice assistant is displayed on the application interface; the first creation instruction is displayed in the dialogue input box.

5. The method according to claim 4, characterized in that, The method further includes: The application interface displays at least one first control, on which related recommended words are displayed. The related recommended words are words associated with the reminder. The first control is used to trigger the electronic device to jump from the application interface displaying the first application to the interface displaying the related recommended words in response to the user's first selection operation.

6. The method according to claim 4 or 5, characterized in that, The dialog input box includes a send control, which, in response to a first operation on the first creation instruction, creates a first reminder event associated with the target scene, including: In response to a touch operation on the sending control, the first creation instruction is sent to the voice assistant, triggering the voice assistant of the electronic device to create a first reminder event associated with the target scene in response to the first creation instruction.

7. The method according to any one of claims 4-6, characterized in that, The method further includes: In response to a touch operation on the dialogue input box, the dialogue interface of the voice assistant is displayed; the dialogue interface displays the first creation instruction.

8. The method according to claim 7, characterized in that, The dialogue interface also displays a second creation instruction, which guides the voice assistant to create a second reminder event associated with the first reminder event. The method further includes: In response to a second selection operation on the second creation instruction, the second creation instruction is sent to the voice assistant, triggering the voice assistant to create the second reminder event based on the second creation instruction.

9. The method according to any one of claims 1-8, characterized in that, The target scenario includes a second application in the electronic device containing the reminder; the second application includes at least SMS, gallery, memo, calendar, and notes; the gallery includes pictures related to the appointment.

10. The method according to claim 9, characterized in that, In response to the electronic device recognizing the target scene, displaying a first creation instruction on the interface of the electronic device includes: In response to the electronic device recognizing that the second application contains the reminder, a dialogue interface of the electronic device's voice assistant is displayed on the desktop of the electronic device, and the dialogue interface displays the first creation instruction.

11. The method according to claim 9 or 10, characterized in that, Before the first creation instruction is displayed on the interface of the electronic device, the method further includes: The desktop card associated with the voice assistant of the electronic device is displayed. The desktop card displays a prompt message, which is used to prompt whether to create a first reminder event associated with the target scene. The display of the first creation instruction includes: In response to a second operation by the electronic device on the desktop card associated with the voice assistant, the first creation instruction is displayed.

12. The method according to claim 1, characterized in that, The target scenario includes a user browsing the application interface of a third application, wherein the application interface of the third application satisfies at least one of the following page characteristics: The application interface of the third application includes a calendar control; The third application's interface includes a reservation control; The third application's interface includes date-related recommendation information; The application interface of the third application includes location-related recommendation information; The application interface of the third application includes a query message, which is used to ask the user whether to create the first reminder event.

13. The method according to any one of claims 1-12, characterized in that, The target scenario includes obtaining the user's behavioral profile, and the display of the first creation instruction includes: In response to the behavioral profile obtained by the electronic device from learning the user's habitual characteristics, a first creation instruction is displayed on the interface of the electronic device; the first creation instruction is generated based on the user's behavioral profile.

14. The method according to any one of claims 1-13, characterized in that, After creating the first reminder event associated with the target scene, the method further includes: The electronic device outputs the first reminder event in a preset reminder method; wherein the reminder method includes at least displaying the reminder information corresponding to the first reminder event on a desktop card, displaying the reminder information corresponding to the first reminder event in a capsule manner, pushing the reminder information corresponding to the first reminder event to the user in a notification message, notifying the user of the reminder information corresponding to the first reminder event in an alarm manner, and notifying the user of the reminder information corresponding to the first reminder event in a countdown manner.

15. The method according to any one of claims 1-14, characterized in that, The method further includes: Identify the target scenario to determine the reminder time and content for the item to be reminded; The first creation instruction is generated based on the reminder time and the reminder content.

16. An electronic device, characterized in that, The electronic device includes: a communication module, a display screen, a memory, and one or more processors; the communication module, the display screen, the memory, and the processors are coupled; the memory is used to store computer program code, the computer program code including computer instructions, which, when executed by the electronic device, cause the electronic device to perform the method as described in any one of claims 1-15.

17. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores instructions that, when executed in an electronic device, cause the electronic device to perform the method as described in any one of claims 1 to 15.

18. A computer program product, characterized in that, The computer program product includes instructions that, when executed in a terminal device, cause the terminal device to perform the method as described in any one of claims 1 to 15.

Images