Intelligent reminding method and device, electronic equipment and readable storage medium

Abstract

The invention discloses an intelligent reminding method and device, electronic equipment and a readable storage medium, and belongs to the technical field of electronic equipment control. The method comprises the following steps: under the condition of displaying an alarm clock interface, receiving a first input; in response to the first input, creating a reminding event according to reminding trigger information corresponding to the first input; wherein the reminding trigger information comprises at least one of the following information: operation behavior information, geographical location information, associated equipment state information, equipment state information, application state information and associated task information.

Description

TECHNICAL FIELD

[0001] The present application belongs to the technical field of electronic devices, and particularly relates to an intelligent reminding method and device, an electronic device and a readable storage medium. BACKGROUND

[0002] In today's highly popular electronic devices, the alarm clock function has become a basic service in electronic devices. The alarm clock reminding function can effectively deal with most scenarios with explicit time constraints, helping users complete the reminding and execution of planned matters, and thus becomes an indispensable auxiliary tool in users' daily arrangements.

[0003] At present, the alarm clock reminding function still mainly relies on static time setting. In specific implementation, the user needs to pre-input a fixed trigger time, and supplement it with a text note to explain the specific event content. However, due to the volatility of actual travel and the uncertainty of user operation application time, it is difficult to dynamically respond to the actual behavior state of the user, reducing the effectiveness of the reminder.

[0004] Therefore, the existing alarm clock reminding function cannot meet the diversified needs of users in actual scenarios. SUMMARY

[0005] The purpose of the embodiments of the present application is to provide an intelligent reminding method and device, an electronic device and a readable storage medium, which can solve the problem that the existing alarm clock reminding function cannot meet the diversified needs of users in actual scenarios.

[0006] In a first aspect, the embodiments of the present application provide an intelligent reminding method, which comprises: receiving a first input in a case of displaying an alarm clock interface; creating a reminding event according to reminding trigger information corresponding to the first input in response to the first input; The reminding trigger information comprises at least one of the following: operation behavior information, geographical position information, associated device state information, device state information, application state information and associated task information.

[0007] In a second aspect, the embodiments of the present application provide an intelligent reminding device, which comprises: a receiving module configured to receive a first input in a case of displaying an alarm clock interface; a creating module configured to create a reminding event according to reminding trigger information corresponding to the first input in response to the first input; The reminding trigger information comprises at least one of the following: operation behavior information, geographical position information, associated device state information, device state information, application state information and associated task information.

[0008] In a third aspect, an electronic device is provided, which includes a processor and a memory. The memory stores programs or instructions executable by the processor. The programs or instructions, when executed by the processor, implement the steps of the method according to the first aspect.

[0009] In a fourth aspect, a readable storage medium is provided, which stores programs or instructions. The programs or instructions, when executed by a processor, implement the steps of the method according to the first aspect.

[0010] In a fifth aspect, a chip is provided, which includes a processor and a communication interface. The communication interface is coupled to the processor. The processor is configured to execute programs or instructions to implement the method according to the first aspect.

[0011] In a sixth aspect, a computer program product is provided, which is stored in a storage medium. The computer program product is executed by at least one processor to implement the method according to the first aspect.

[0012] In the embodiments of the present application, in the case of displaying the alarm clock interface, the first input is received, and in response to the first input, the reminder event is created according to the reminder trigger information corresponding to the first input, and the association relationship between the reminder trigger information and the reminder event is established. The reminder trigger information includes at least one of the following: operation behavior information, geographic location information, associated device state information, device state information, application state information, and associated task information. Since the operation behavior information provides a trigger dimension based on user interaction, the geographic location information supports the trigger judgment related to the spatial position, the device state information and the associated device state information realize the perception ability of the device environment state, the application state information provides the monitoring dimension of the application internal state, and the associated task information establishes the dependency relationship between tasks, the diversified reminder trigger information can cover the common reminder scene requirements. Therefore, creating the reminder event according to the diversified reminder trigger information can meet the diversified needs of users in actual scenes. BRIEF DESCRIPTION OF DRAWINGS

[0013] Figure 1 is a flowchart of a smart reminder method provided by the embodiments of the present application; Figure 2 is one of the schematic diagrams of an alarm clock setting interface provided by the embodiments of the present application; Figure 3 is another schematic diagram of an alarm clock setting interface provided by the embodiments of the present application; Figure 4 is a third schematic diagram of an alarm clock setting interface provided by the embodiments of the present application; Figure 5is a structural diagram of an intelligent reminding device provided by an embodiment of the present application; Figure 6 is a hardware structure schematic diagram of an electronic device of an embodiment of the present application; Figure 7 is a hardware structure schematic diagram of an electronic device of an embodiment of the present application. DETAILED DESCRIPTION

[0014] The technical solutions of the embodiments of the present application will be clearly described below with reference to the drawings of the embodiments of the present application. Obviously, the described embodiments are only some of the embodiments of the present application, rather than all the embodiments of the present application. Based on the embodiments of the present application, all other embodiments obtained by those of ordinary skill in the art belong to the scope of protection of the present application.

[0015] The terms "first", "second", and the like in the specification and claims of the present application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged under appropriate circumstances, so that the embodiments of the present application can be implemented in an order other than those illustrated or described herein, and the objects distinguished by "first", "second", etc. are generally of a kind and do not limit the number of objects, for example, the first object can be one or more. In addition, "and / or" in the specification and claims indicates at least one of the connected objects, and the character " / ", generally indicates that the front and rear associated objects are in an "or" relationship.

[0016] The embodiments of the present application can be applied to at least the following scenarios: Scenario one: users often set alarms for to-do items at specific locations. For example, a user plans to arrive at a company at 10 o'clock in the morning, and sets an alarm that rings at this time to remind himself to pick up a package. However, there are many uncertainties in the traffic during the commute, and when encountering road congestion, the 10 o'clock bell rings on time, but the user is still stuck on the road and has not yet arrived at the company. The reminder at this time not only fails to help the user complete the pickup task, but also loses its due value because of the disconnection between the reminder time and the actual situation.

[0017] Scenario two: users often need to perform related operations when using a specific application. For example, a user plans to use a shopping software to purchase shampoo at 8 o'clock in the evening, and accordingly sets an alarm to remind. However, in actual life, the user may have opened the shopping software to browse goods as early as 7 o'clock, at which time the scheduled alarm has not been triggered, and the shopping demand is easy to be ignored; on the contrary, if the user opens the software at 9 o'clock, the 8 o'clock alarm has already rung and cannot be traced back, which also leads to the omission of the purchase item. In either case, the user needs to adjust the alarm time or give up the setting, and these adjustments often come with the risk of eventually forgetting the target item.

[0018] Therefore, in daily life, reminders based on fixed times often fail to meet users' actual needs due to dynamic changes in real-world situations.

[0019] In response to the problems in related technologies, embodiments of this application provide an intelligent reminder method, device, electronic device, and readable storage medium, which can solve the problem that existing alarm clock reminder functions are difficult to meet the diverse needs of users in real-world scenarios.

[0020] The intelligent reminder method provided in this application will be described in detail below with reference to the accompanying drawings, through specific embodiments and application scenarios.

[0021] Figure 1 A flowchart illustrating an intelligent reminder method provided in an embodiment of this application.

[0022] like Figure 1 As shown, the smart reminder method may include steps 110-120. This method is applied to a smart reminder device, as detailed below: Step 110: While the alarm clock interface is displayed, receive the first input; The alarm clock interface refers to the user interface used to set reminder events, which includes configuration elements such as time settings, event descriptions, and trigger conditions; the first input is the operation command executed by the user on this interface, and the input information constitutes the reminder trigger information; For example, users can select the trigger condition type by touching the screen or describe the event intent by voice input, and these input information are uniformly encoded into a structured data format. In specific implementation, the first input can take various forms, such as a click operation completed through the touch screen, a voice command collected through the microphone, or a control signal input through an external device.

[0023] Step 120: In response to the first input, create a reminder event based on the reminder trigger information corresponding to the first input; The reminder trigger information includes at least one of the following: operation behavior information, geographical location information, associated device status information, device status information, application status information, and associated task information.

[0024] The reminder trigger information contains a complete set of parameters required to create a reminder event, including the event intent description and trigger condition configuration; a reminder event is a task to be executed created according to the configuration parameters, which will be activated and executed when preset conditions are met.

[0025] For example, if a user inputs "Remind me to attend a meeting every morning at 9 AM," speech recognition and semantic analysis technologies can be used to extract the time condition "every morning at 9 AM" and the event intent "meeting," creating a timed reminder event with daily repetition. In another example, if a user selects "Remind me to pick up a package when I arrive at the company," a location-triggered reminder event will be generated, which includes environmental attributes such as the company's geofence and a description of the event intent of picking up the package.

[0026] The reminder trigger information refers to the set of parameters used to define the activation conditions of the reminder event, which are explained below: User interaction information: refers to specific interactive actions performed by users on electronic devices. For example, a user taps an app icon to launch a shopping program, or a user performs a specific gesture within the app, such as long-pressing a product image.

[0027] Specifically, users can select action behavior information as the reminder trigger during the settings process, specifying the target application and associated event intent. By continuously monitoring the application status, the system immediately executes the corresponding reminder task when the target application is detected to be launched. For example, if a user sets a shopping application as the primary application, when the application is detected to be launched, a notification interface with preset reminder content is displayed, along with quick access points for the user to directly perform related actions. By accurately matching application launch behavior with user action intent, the timeliness and accuracy of the reminder function are effectively improved, while simplifying the user's operation process.

[0028] Geographic location information refers to the spatial location data of a device, including its own location or the location of associated devices obtained through a communication connection. Examples include the latitude and longitude coordinates of the current device obtained via GPS, or the current location data of a children's smartwatch obtained through a device interconnection protocol.

[0029] Specifically, when setting reminder events, users can select geographical location information as the reminder trigger. For example, a user can set a shopping mall area as the environmental attribute condition. When the device is detected entering the preset geographical area, the corresponding reminder task is triggered. By accurately matching the spatial relationship between the device's location status and the preset geographical area, accurate responses to the user's spatial intentions are achieved. While maintaining the clarity of the judgment logic, the timeliness and reliability of location-related reminders are ensured. This can be applied to location-related reminder needs in daily life, such as shopping reminders upon arriving at a shopping mall or task reminders upon arriving at the office. Through precise spatial location perception, it provides users with timely, contextualized reminder services.

[0030] Associated device status information: refers to the operating status parameters of other smart devices that have established a communication connection with the current device. For example, the on / off status of lighting devices obtained through smart home protocols, or heart rate monitoring data from wearable devices obtained through Bluetooth connections.

[0031] Specifically, by combining environmental attributes with changes in the status of other devices, composite triggering conditions are constructed, enabling alert events to more accurately match the user's actual scenario needs. When setting alert events, users can configure the status information of associated devices; for example, the user can select the "on" status of a smart lighting device as the associated device status information. When the status of the associated device meets the preset conditions, the corresponding alert event will be triggered.

[0032] Device status information: refers to the current hardware and network connection status parameters of the device itself. For example, the device's Wi-Fi connection status changes from disconnected to connected to a specific network, or the device's battery level is lower than a preset threshold.

[0033] Specifically, when device status information is used as the trigger for reminders, the corresponding reminder event execution process will be triggered when the device status is detected to meet preset conditions. This device status information-based triggering mechanism enables intelligent perception of the device's own operating environment. By monitoring changes in device hardware and network connection status, a correlation between device status and user needs can be established, allowing the reminder function to better adapt to device usage scenarios and improving the accuracy and practicality of reminders.

[0034] Application status information: refers to the internal operating status and data status changes of applications on the device. For example, in a shopping application, a coupon status changes from unavailable to available; in a social application, the number of unread messages reaches a preset threshold; and in an online shopping order, the status changes from pending delivery to arrived at the station.

[0035] When application status information is used as the trigger for reminders, changes in application status are obtained through cross-application data interfaces and used as a key basis for triggering reminder events. When application status information meets preset conditions, the corresponding reminder mechanism is activated, achieving cross-task status awareness and linkage. By establishing logical connections between tasks, reminders can better adapt to the needs of multi-step and cross-scenario task execution, improving the consistency and usability of the reminder function.

[0036] Related task information: refers to the triggering conditions that are linked to the execution status of other tasks. For example, the completion of the preceding task "laundry program" triggers the reminder condition for the subsequent task "drying clothes", or the completion of the collaborative task "file transfer" triggers the reminder condition for "file review".

[0037] Specifically, when setting reminder events, users can select associated task information as an important component of the trigger condition and combine it with environmental attribute conditions. The system monitors the completion status of preceding tasks, and once the task is confirmed to be completed, it begins monitoring the fulfillment of environmental attribute conditions. For example, a user sets "Complete Weekly Work Report" as the associated task information and configures "Enter the Company Break Room Area" as the geographical location information. When the weekly work report task status changes to completed and the device enters the break room geofence, a reminder event to print the weekly report is triggered. By combining the completion status of preceding tasks with environmental attribute conditions, composite trigger conditions with a logical sequence are constructed.

[0038] By establishing a collaborative judgment logic between task status and spatial location, the timing of reminders can be more accurately determined, ensuring that appropriate operation prompts are triggered in suitable scenarios. This allows the reminder service to better adapt to the execution needs of multi-step tasks, significantly enhancing the practicality and scenario adaptability of the reminder function. It can be further extended to various scenarios requiring collaborative judgment of task status and location information, such as e-commerce delivery and travel services, providing users with a more intelligent end-to-end reminder service. This task-linked triggering mechanism effectively improves the reminder's ability to support complex workflows.

[0039] In a specific application scenario of this application embodiment, the reminder trigger information may include geographic location information and application status information, forming a composite trigger mechanism. For example, when a device is detected to have entered a preset shopping mall geographic area and a user is detected to have launched a specified shopping application, a corresponding reminder event will be triggered. The composite trigger mechanism ensures that the reminder event is executed only in the target scenario through dual-factor verification. The synergistic effect of geographic location information and application status information effectively improves the accuracy and scenario adaptability of reminder triggering, and can be applied to various scenarios that require coordinated judgment of location and application behavior. By triggering precise reminders when specific application operations are performed at a specific geographic location, effective linkage between offline scenarios and online operations is achieved, avoiding false triggers that may be caused by a single condition, and ensuring timely response when composite conditions are met.

[0040] The geographic location information includes at least one of the geographic location information of the electronic device and the geographic location information of the interconnected devices of the electronic device.

[0041] Geographic location information comprises two levels of location data sources: first, the geographic coordinates obtained by the electronic device itself through positioning; and second, remote location data obtained from associated devices via device interconnection protocols. This dual-source data acquisition mechanism significantly expands the application scope of location-triggered conditions.

[0042] The geographic location information of electronic devices refers to the spatial location parameters acquired in real time. For example, the current street-level positioning coordinates obtained through a GPS module, or the building-level location information determined through Wi-Fi positioning technology.

[0043] The geolocation information of interconnected devices refers to the location parameters returned by other smart devices that have established a data connection with the current device. For example, the current location data of a child's smartwatch obtained through a parental control protocol can trigger a pick-up reminder on the parent's end when the watch's location leaves the school's geographical fence; another example is the real-time location information of a pet tracker obtained through an item tracking protocol, which can trigger a warning reminder to the owner when the pet goes beyond a preset safe area.

[0044] This enables intelligent alerts based on dynamically moving targets by creating alert events using the geographic location information of interconnected electronic devices. When a user's event intent involves monitoring the status of a moving object, data connections between devices are established, and the real-time location information of the interconnected devices is used as an important component of the alert trigger information.

[0045] For example, in parent-child pick-up and drop-off scenarios, when parents set reminder events, an authorization mechanism identifies the child's portable electronic device as the target connected device. The device's geographic location information is obtained, and when the device is detected leaving the preset school geographic area, a corresponding reminder event is immediately triggered on the parent's device. This method achieves dynamic tracking and reminders for moving targets by sensing real-time changes in the connected device's location. It effectively solves the problem of difficulty in determining the timing of reminders due to the uncertain location of moving targets. By incorporating the connected device's geographic location information into the reminder trigger information, a more flexible spatial awareness mechanism is established, providing more accurate reminder services for everyday scenarios requiring coordinated movement.

[0046] By incorporating the location information of interconnected devices into the scope of geographic location information, cross-device spatial status awareness is achieved. This enables alerts to transcend the limitations of single devices, establishing a spatial triggering mechanism based on multi-device collaboration, significantly expanding the application scenarios of location-related alerts. Through a unified location information processing architecture, while maintaining consistency in processing logic, the coverage and practicality of location triggering conditions are effectively improved.

[0047] In one possible embodiment, step 120 may specifically include the following steps: In response to the first input, determine the reminder trigger information; Receive the second input; In response to the second input, a reminder event is created based on the reminder trigger information and the target information corresponding to the second input; the target information includes at least one of the following: reminder event, reminder method, recurring reminder information, and reminder priority.

[0048] In response to the first input, the system parses the reminder trigger information contained therein, which defines the core conditions for activating the reminder event. Next, it receives the second input provided by the user, which contains the auxiliary configuration parameters required to complete the reminder event, i.e., the target information. Finally, by integrating the reminder trigger information and the target information corresponding to the second input, a reminder event with complete attribute definitions is created.

[0049] A phased information collection strategy is adopted, breaking down the event creation process into two relatively independent stages: condition definition and attribute configuration. In the first stage, the focus is on acquiring the core elements triggering the event, such as geographical location conditions or application behavior conditions. In the second stage, user customization requirements for event execution details are received, including important parameters such as reminder methods and execution frequency. For example, the user first sets the environmental attribute condition of "entering the company geofence" through the first input, and then selects the execution frequency of "repeated on weekdays" and the reminder method of "pop-up reminder" through the second input. Integrating these two sets of information generates a complete reminder event.

[0050] The target information corresponding to the second input can include multiple configuration dimensions. Event-related information can include specific content such as event description text and action definition; reminder method information can cover presentation formats such as notification sound type, vibration mode, and display style; recurring reminder information can define time parameters such as execution cycle and effective time range; and reminder priority information can set priority parameters such as interruption level and forced display duration. For example, after setting the behavior attribute condition of "open office application" in the first input, the user further configures the recurring reminder information "Monday to Friday" and the "high priority" reminder level through the second input, thereby creating a periodic event that reminds the user to launch the office application on weekdays with high priority.

[0051] Regarding personalized configuration of reminder tasks, multi-dimensional settings options are provided to meet user needs in different scenarios. In terms of reminder method configuration, for scenarios triggered by behavioral attributes, users can choose appropriate combinations of reminder formats based on the specific application scenario characteristics. For example, for shopping applications, users can choose a combination of "pop-up notification and light vibration" to directly display the preset shopping list through a pop-up while avoiding sound interference; for office applications, a combination of "sound notification and pop-up notification" can be used to ensure that important work reminders are not missed through strong perception.

[0052] Regarding recurring rule settings, it supports configuring execution cycles independently for different types of trigger conditions. Reminder tasks based on behavioral attributes can be set to a single-execution mode, such as product purchase reminders, or a periodic execution mode, such as daily work report reminders. Similarly, reminder tasks based on environmental attributes can also have their execution cycles set according to actual needs, such as weekday commute reminders, eliminating the need for users to repeatedly create reminder tasks with the same conditions.

[0053] In terms of priority management, a tiered strategy is used to achieve differentiated processing. For reminders related to critical tasks and their associated behavioral attributes, a high-priority setting is implemented, employing a highly interactive reminder method to ensure full user awareness. For routine task reminders, a normal priority setting is used, employing a gentler reminder method. This multi-dimensional configuration system based on scenario characteristics enables intelligent reminders to effectively cover various scenarios based on both location status and application usage behavior, meeting the personalized needs of different users.

[0054] The process design of first determining the core triggering conditions and then refining the execution details not only ensures the accurate acquisition of key elements of the reminder event, but also provides users with ample space for personalized configuration, thereby improving operational efficiency and user experience.

[0055] In one possible embodiment, after step 120, the following steps may also be included: Step 130: Obtain the scene status information of the electronic device; Step 140: If the scene state information matches the reminder trigger information, execute the reminder event associated with the reminder trigger information.

[0056] It continuously acquires scene status information of electronic devices, which comprehensively reflects the current environmental and behavioral attributes of the devices; when the scene status information is detected to match the pre-set reminder trigger information, the reminder event associated with the trigger information is automatically executed.

[0057] The system compares the current scene state with preset trigger conditions, and immediately triggers the corresponding event response mechanism once the matching requirements are met. For example, after creating a reminder event for "remind to buy milk when arriving at the supermarket", the system continuously monitors the device's geographical location information. When the device is detected to have entered the preset supermarket geofence area, the execution process of the reminder event is automatically activated.

[0058] Scene status information includes multi-dimensional device status parameters. Environmental attribute information may include physical environmental parameters such as the device's current location coordinates, ambient light intensity, and ambient noise level; behavioral attribute information may include operational status parameters such as the currently running application, the device's network connection status, and user interaction behavior. For example, for alert events based on environmental attribute conditions, the device's location sensor data will be continuously acquired and spatial relationship calculations will be performed with a preset geofence range; for alert events based on behavioral attribute conditions, application lifecycle events will be monitored to detect whether the target application has entered the foreground running state.

[0059] Through a continuous status monitoring mechanism, a real-time and reliable data foundation is provided for the accurate triggering of reminder events, ensuring a sensitive perception capability of changes in the device environment. Through an intelligent matching and automatic execution mechanism, automated processing from status recognition to task execution is realized, effectively improving the accuracy and timeliness of reminder event triggering. It can intelligently provide accurate reminder services at appropriate times without increasing the user's operational burden, thereby enhancing practicality and user experience.

[0060] In one possible embodiment, the reminder trigger information also includes the reminder time; Step 140 may specifically include the following steps: If the current time matches the reminder time and the scene status information matches the reminder trigger information, execute the reminder event associated with the reminder trigger information.

[0061] A key parameter, reminder time, has been added to the reminder trigger information, and the judgment process requires simultaneous fulfillment of both time matching and scene state matching conditions. The system monitors the current time and device scene state information in parallel. If the current time matches the reminder time, and the scene state information matches the environmental or behavioral attributes defined in the reminder trigger information, the associated reminder event is executed.

[0062] For example, a user sets a reminder event to "bring a gym towel when arriving at the gym at 6 PM on a weekday." Here, "6 PM on a weekday" constitutes the time condition, and "arriving at the gym" constitutes the environmental attribute condition. During the time period of 6 PM on weekdays, the system will continuously monitor the spatial relationship between the device's location and the gym's geofence, and only trigger the reminder when both conditions are met simultaneously.

[0063] Matching time conditions can be done using either absolute time points or relative time intervals. Absolute time point matching requires the time to be exactly the same as the preset time, suitable for reminders requiring precise timing; relative time interval matching allows reminders to be triggered within a specific time period based on scene status conditions, suitable for flexible scenarios with time windows. For example, if a rule is configured to "remind you to watch TV series when you open a video app all day on Saturday and Sunday," the reminder task will be triggered immediately once the user launches the target video app during the weekend.

[0064] When the current time matches the reminder time, and the scene status information matches the reminder trigger information, the reminder event associated with the reminder trigger information is executed. By introducing a combined judgment of time conditions and behavioral attribute conditions, the effective time range of the reminder event is effectively limited, avoiding accidental triggering outside the target time period. It can be configured to trigger the reminder event only when both specific time conditions and behavioral attribute conditions are met simultaneously. The time condition limits the effective time range of the reminder, while the behavioral attribute condition defines the usage status of the target application. For example, if the time condition is configured to be all day Saturday and Sunday, and the behavioral attribute condition is that a video application is launched, the reminder task will only be triggered when the user launches the target application within this time interval.

[0065] Dual-factor verification ensures that reminders only respond to corresponding application usage behaviors within the expected time period. The introduction of time conditions prevents false triggers outside the target time period, while simultaneous verification of behavioral attribute conditions ensures the relevance of the reminder content to the current application operation. The synergy of these two dimensions maintains the deterministic advantage of time-based reminders while inheriting the context-awareness of behavioral triggers. It is suitable for various scenarios requiring coordinated judgment of time and application usage behavior, including time-segmented learning reminders and specific-time financial management, among other daily application needs. Through the combined configuration of time and behavioral attribute conditions, while maintaining the sensitivity of behavioral triggers, the accuracy and scenario adaptability of reminder triggers are significantly improved, providing users with a smart reminder service that better suits their usage habits.

[0066] By introducing dual verification of both time and scene state dimensions, the accuracy and applicability of reminder triggering are significantly improved. The addition of time conditions effectively limits the valid time range of reminder events, avoiding accidental triggering during unexpected time periods; the synchronous verification of scene state conditions ensures the relevance of reminder content to the current device environment. The synergistic effect of these two dimensions maintains the deterministic advantage of time-based reminders while inheriting the context-aware capabilities of scene state reminders, enabling more accurate and intelligent reminder services in complex real-world application environments.

[0067] In one possible embodiment, step 140 may specifically include the following steps: The first duration for which the accumulated scene status information matches the reminder trigger information; If the preset duration is reached after the first set duration, execute the reminder event associated with the reminder trigger information.

[0068] When the scene status information and the reminder trigger information are detected to have an initial match, the timing function is started and the first duration of the matching state is continuously accumulated. Then, the first duration is compared with a preset duration threshold. When the matching state continuously reaches or exceeds the threshold, the reminder event is triggered.

[0069] By introducing a verification requirement based on state duration, false matches caused by signal fluctuations or instantaneous state changes are effectively filtered out. An independent state machine and timer are maintained for each alert event. The timer starts when the scene state information changes from "mismatch" to "match." If the matching state is interrupted during the timer, the timer is immediately reset. A valid trigger condition is only determined when the matching state is maintained for a preset threshold. For example, for location-based environmental attributes, a 30-second continuous matching requirement is set, which avoids false triggers caused by devices briefly entering or leaving fence boundaries due to GPS signal drift.

[0070] The preset duration can be configured differently depending on the type of trigger condition. For environmental attribute conditions, such as geolocation matching, a longer duration threshold, such as 30-60 seconds, is typically set to handle location signal fluctuations. For behavioral attribute conditions, such as application startup status matching, a shorter duration threshold, such as 3-5 seconds, can be set to balance response speed and accuracy. For example, if a "remind to keep quiet when entering the library area" reminder event is configured, and a 45-second continuous matching requirement is set, the reminder will only be triggered if the device remains stably within the library geofence for more than 45 seconds, effectively avoiding false reminders when the user briefly passes through the library area.

[0071] By requiring a continuous match between scene state information and alert trigger information, it can effectively identify real scene state changes, filter out transient interference signals, and reduce the probability of false triggers. Configurable duration parameters enable it to adapt to the stability requirements of different scenarios, ensuring the accuracy and usability of alert triggers while maintaining scene awareness sensitivity, ultimately improving overall performance and user experience.

[0072] In one possible embodiment, the first input includes a first sub-input and a second sub-input; step 120 may specifically include the following steps: In response to the first sub-input of the event identifier information in the alarm clock interface, display at least one candidate trigger information; Receive a second sub-input for at least one candidate trigger information; In response to the second sub-input, a reminder event is created based on the reminder trigger information corresponding to the second sub-input.

[0073] The first sub-input is used to determine the basic type of the event, and the second sub-input is used to select the specific trigger conditions. Responding to the user's first sub-input of the event identifier information in the alarm clock interface, the system dynamically displays candidate trigger information related to the event type; it receives the user's second sub-input from the candidate trigger information; and it creates a complete reminder event based on the reminder trigger information corresponding to the second sub-input.

[0074] By employing a phased information presentation and selection mechanism, the complexity of user configuration is reduced. When a user specifies the event type through the first sub-input, the system filters out the most suitable triggering conditions for that type of event using predefined mapping relationships, allowing the user to choose from a limited set of candidates. For example, when a user enters "shopping reminder" in the event identifier area and confirms, it automatically displays candidate triggering information highly relevant to the shopping scenario, such as "enter the shopping mall area" or "open the shopping app," for the user to select from.

[0075] Event identification information can be a natural language description directly entered by the user, or an event tag selected from a preset template library. Candidate trigger information is intelligently recommended based on the event type, covering various types such as environmental and behavioral attributes. For example, for a "study reminder" event, the environmental attribute condition "entering the library area" and the behavioral attribute condition "opening a study application" might be recommended; for a "commuting reminder" event, the environmental attribute condition "leaving the company area" and the device status condition "connecting to car Bluetooth" might be recommended.

[0076] For example, when a user enters "purchase office supplies" in the event identifier area of ​​the alarm clock settings interface and submits it, a list of related candidate conditions will be intelligently displayed based on the event type. These conditions include environmental attribute conditions such as "enter the office supplies mall geofence" and behavioral attribute conditions such as "open the e-commerce application". The user can then select one or more of these conditions as the actual reminder conditions through the first input.

[0077] The event identifier information in the alarm clock settings interface can be either text fields freely entered by the user or tags selected from a preset template library. After the event identifier is confirmed through a second input, relevant candidate conditions are filtered from the condition library based on semantic analysis results or predefined rules, and presented to the user in a visual manner.

[0078] like Figure 2 As shown, the alarm clock settings interface 210 is displayed, and the alarm clock settings interface 210 includes event identifier information 211. For example... Figure 3 As shown, a first input is received, which is used to select an environmental attribute condition from at least one candidate condition 212, or, as...Figure 4 As shown, the first input is used to select a behavioral attribute condition from at least one candidate condition 213.

[0079] By first determining the event intent and then selecting the conditions, the system can provide condition options that are highly relevant to the event, reducing the search cost for users among numerous condition types. At the same time, the pre-screening mechanism for condition options also avoids unreasonable combinations of conditions, ensuring the logical rationality of the reminder task configuration from the source, reducing the risk of accidental triggering due to improper condition settings, and improving the overall configuration efficiency and reliability.

[0080] The first sub-input stage identifies event types to inform subsequent conditional recommendations, while the second sub-input stage uses carefully selected candidate trigger information to ensure the rationality and effectiveness of the configuration. The entire process maintains configuration flexibility while using guided interaction to avoid configuration errors caused by user unfamiliarity with technical concepts, thus improving operational efficiency and ensuring the quality and usability of alert event configurations.

[0081] In one possible embodiment, a third input is received, the input information of which includes reminder intent information; In response to the third input, the reminder intent information is parsed and a reminder trigger information is generated.

[0082] The second input contains reminder intent information expressed in natural language. Subsequently, the received reminder intent information is deeply analyzed, and key elements are automatically identified by analyzing the semantic structure of the text. Based on the identification results, standardized reminder trigger information that conforms to the user's intent is generated.

[0083] The semantic analysis model automatically extracts environmental and behavioral elements from user intent information and converts the user intent information into recognizable structured condition parameters. For example, if a user inputs a reminder intent such as "Remind me to pick up my package every time I walk downstairs to the company," semantic parsing identifies "downstairs to the company" as a geographical location element and "walk to" as a triggering behavioral element, thereby automatically generating an environmental attribute condition centered on the company's location.

[0084] Upon receiving the second input reminder intent information, word segmentation and part-of-speech tagging are performed. Key information such as geographical location, application name, and time expression are extracted using named entity recognition technology. Then, dependency parsing is used to understand the logical relationships between these elements, and a corresponding reminder trigger information object is generated according to preset mapping rules. For example, for the intent information "Remember to buy shampoo when you open the shopping app," "shopping app" is identified as the application entity, and "open" is identified as the behavior trigger word, generating a behavior attribute condition for a specific shopping app.

[0085] By automatically converting natural language expressions into structured reminder trigger information, the burden on users to manually set various condition parameters is effectively reduced. At the same time, the introduction of semantic parsing technology enables more accurate capture of the user's true intent, avoiding the problem of mismatch between conditions and intent caused by improper manual settings, and improving the intelligence level of reminder task configuration and user experience.

[0086] In the embodiments of this application, when the alarm clock interface is displayed, a first input is received. In response to the first input, a reminder event is created based on the reminder trigger information corresponding to the first input, establishing an association between the reminder trigger information and the reminder event. The reminder trigger information includes at least one of the following: operation behavior information, geographic location information, associated device status information, device status information, application status information, and associated task information. Since operation behavior information provides a trigger dimension based on user interaction, geographic location information supports spatial location-related trigger judgments, device status information and associated device status information realize the perception capability of device environmental status, application status information provides a monitoring dimension of the application's internal status, and associated task information establishes dependencies between tasks, the diverse reminder trigger information can cover common reminder scenario needs. Therefore, creating reminder events based on diverse reminder trigger information can meet the diverse needs of users in real-world scenarios.

[0087] The intelligent reminder method provided in this application can be executed by an intelligent reminder device. This application uses an intelligent reminder device executing the intelligent reminder method as an example to illustrate the intelligent reminder device provided in this application.

[0088] Figure 5 This is a block diagram of a smart reminder device provided in an embodiment of this application. The device 500 includes: The receiving module 510 is used to receive the first input when the alarm clock interface is displayed; Module 520 is created to respond to the first input and create a reminder event based on the reminder trigger information corresponding to the first input. The reminder trigger information includes at least one of the following: operation behavior information, geographical location information, associated device status information, device status information, application status information, and associated task information.

[0089] In one possible embodiment, the geographic location information includes at least one of the geographic location information of the electronic device and the geographic location information of the interconnected devices of the electronic device.

[0090] In one possible embodiment, module 520 is specifically used for: In response to the first input, determine the reminder trigger information; Receive the second input; In response to the second input, a reminder event is created based on the reminder trigger information and the target information corresponding to the second input; the target information includes at least one of the following: reminder event, reminder method, recurring reminder information, and reminder priority.

[0091] In one possible embodiment, the device 500 may further include: The acquisition module is used to acquire scene status information of electronic devices; The execution module is used to execute the reminder event associated with the reminder trigger information when the scene status information matches the reminder trigger information.

[0092] In one possible embodiment, the reminder trigger information also includes the reminder time; The execution module is specifically used for: If the current time matches the reminder time and the scene status information matches the reminder trigger information, execute the reminder event associated with the reminder trigger information.

[0093] In one possible embodiment, the execution module is specifically used for: The first duration for which the accumulated scene status information matches the reminder trigger information; If the preset duration is reached after the first set duration, execute the reminder event associated with the reminder trigger information.

[0094] In one possible embodiment, the first input includes a first sub-input and a second sub-input; the creation module 520 is specifically used for: In response to the first sub-input of the event identifier information in the alarm clock interface, display at least one candidate trigger information; Receive a second sub-input for at least one candidate trigger information; In response to the second sub-input, a reminder event is created based on the reminder trigger information corresponding to the second sub-input.

[0095] In the embodiments of this application, when the alarm clock interface is displayed, a first input is received. In response to the first input, a reminder event is created based on the reminder trigger information corresponding to the first input, establishing an association between the reminder trigger information and the reminder event. The reminder trigger information includes at least one of the following: operation behavior information, geographic location information, associated device status information, device status information, application status information, and associated task information. Since operation behavior information provides a trigger dimension based on user interaction, geographic location information supports spatial location-related trigger judgments, device status information and associated device status information realize the perception capability of device environmental status, application status information provides a monitoring dimension of the application's internal status, and associated task information establishes dependencies between tasks, the diverse reminder trigger information can cover common reminder scenario needs. Therefore, creating reminder events based on diverse reminder trigger information can meet the diverse needs of users in real-world scenarios.

[0096] The intelligent reminder device in this application embodiment can be an electronic device or a component within an electronic device, such as an integrated circuit or a chip. The electronic device can be a terminal or other devices besides a terminal. For example, the electronic device can be a mobile phone, tablet computer, laptop computer, PDA, in-vehicle electronic device, mobile internet device (MID), augmented reality (AR) / virtual reality (VR) device, robot, wearable device, ultra-mobile personal computer (UMPC), netbook, or personal digital assistant (PDA), etc. It can also be a server, network attached storage (NAS), personal computer (PC), television (TV), ATM, or self-service machine, etc. This application embodiment does not specifically limit the specific type of device.

[0097] The smart reminder device in this application embodiment can be a device with an action system. The action system can be an Android action system, an iOS action system, or other possible action systems; this application embodiment does not specifically limit it.

[0098] The intelligent reminder device provided in this application embodiment can realize the various processes implemented in the above method embodiments, and will not be described again here to avoid repetition.

[0099] Optionally, such as Figure 6As shown, this application embodiment also provides an electronic device 610, including a processor 611, a memory 612, and a program or instructions stored in the memory 612 and executable on the processor 611. When the program or instructions are executed by the processor 611, they implement the various steps of any of the above-described intelligent reminder method embodiments and achieve the same technical effect. To avoid repetition, they will not be described again here.

[0100] It should be noted that the electronic devices in the embodiments of this application include the mobile electronic devices and non-mobile electronic devices described above.

[0101] Figure 7 A schematic diagram of the hardware structure of an electronic device to implement an embodiment of this application. The electronic device 700 includes, but is not limited to, components such as: radio frequency unit 701, network module 702, audio output unit 703, input unit 704, sensor 705, display unit 706, user input unit 707, interface unit 708, memory 709, and processor 710.

[0102] Those skilled in the art will understand that the electronic device 700 may also include a power supply (such as a battery) for supplying power to various components. The power supply may be logically connected to the processor 710 through a power management system, thereby enabling functions such as managing charging, discharging, and power consumption through the power management system. Figure 7 The electronic device structure shown does not constitute a limitation on the electronic device. The electronic device may include more or fewer components than shown, or combine certain components, or have different component arrangements, which will not be elaborated here.

[0103] The user input unit 707 is used to receive the first input when the alarm clock interface is displayed; The processor 710 is configured to respond to the first input and create a reminder event based on the reminder trigger information corresponding to the first input; The reminder trigger information includes at least one of the following: operation behavior information, geographical location information, associated device status information, device status information, application status information, and associated task information.

[0104] Optionally, the geographic location information includes at least one of the geographic location information of the electronic device and the geographic location information of the interconnected devices of the electronic device.

[0105] Optionally, the processor 710 is also configured to determine the reminder trigger information in response to the first input; User input unit 707 is also used to receive a second input; The processor 710 is also configured to, in response to the second input, create a reminder event based on the reminder trigger information and the target information corresponding to the second input; the target information includes at least one of the following: reminder event, reminder method, recurring reminder information, and reminder priority.

[0106] Optionally, the processor 710 is also used to acquire scene state information of the electronic device; The processor 710 is also used to execute an alert event associated with the alert trigger information when the scene state information matches the alert trigger information.

[0107] Optionally, the reminder trigger information also includes the reminder time; the processor 710 is also used to execute the reminder event associated with the reminder trigger information when the current time matches the reminder time and the scene state information matches the reminder trigger information.

[0108] Optionally, the processor 710 is also used to accumulate a first duration for matching scene status information with reminder trigger information; The processor 710 is also used to execute a reminder event associated with the reminder trigger information when the first duration reaches the preset duration.

[0109] Optionally, the first input includes a first sub-input and a second sub-input; module 520 is created specifically for: Display unit 706 is used to display at least one selectable trigger information in response to a first sub-input of event identifier information in the alarm clock interface; User input unit 707 is also configured to receive a second sub-input for at least one candidate trigger information; The processor 710 is also configured to respond to the second sub-input by creating a reminder event based on the reminder trigger information corresponding to the second sub-input.

[0110] In the embodiments of this application, when the alarm clock interface is displayed, a first input is received. In response to the first input, a reminder event is created based on the reminder trigger information corresponding to the first input, establishing an association between the reminder trigger information and the reminder event. The reminder trigger information includes at least one of the following: operation behavior information, geographic location information, associated device status information, device status information, application status information, and associated task information. Since operation behavior information provides a trigger dimension based on user interaction, geographic location information supports spatial location-related trigger judgments, device status information and associated device status information realize the perception capability of device environmental status, application status information provides a monitoring dimension of the application's internal status, and associated task information establishes dependencies between tasks, the diverse reminder trigger information can cover common reminder scenario needs. Therefore, creating reminder events based on diverse reminder trigger information can meet the diverse needs of users in real-world scenarios.

[0111] It should be understood that, in this embodiment, the input unit 704 may include a graphics processing unit (GPU) 7041 and a microphone 7042. The GPU 7041 processes image data of still images or video images obtained by an image capture device (such as a camera) in video image capture mode or image capture mode. The display unit 706 may include a display panel 7061, which may be configured in the form of a liquid crystal display, an organic light-emitting diode, etc. The user input unit 707 includes at least one of a touch panel 7071 and other input devices 7072. The touch panel 7071 is also called a touch screen. The touch panel 7071 may include a touch detection device and a touch controller. Other input devices 7072 may include, but are not limited to, physical keyboards, function keys (such as volume control buttons, power buttons, etc.), trackballs, mice, and joysticks, which will not be described in detail here. The memory 709 can be used to store software programs and various data, including but not limited to applications and motion systems. Processor 710 can integrate an application processor and a modem processor. The application processor mainly handles the action system, user page, and applications, while the modem processor mainly handles wireless communication. It is understood that the modem processor may also not be integrated into processor 710.

[0112] The memory 709 can be used to store software programs and various data. The memory 709 may primarily include a first storage area for storing programs or instructions and a second storage area for storing data. The first storage area may store the operating system, application programs or instructions required for at least one function (such as sound playback, image playback, etc.). Furthermore, the memory 709 may include volatile memory or non-volatile memory, or it may include both volatile and non-volatile memory. The non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory can be random access memory (RAM), static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct memory bus RAM (DRRAM). The memory 709 in the embodiments of this application includes, but is not limited to, these and any other suitable types of memory.

[0113] Processor 710 may include one or more processing units; optionally, processor 710 integrates an application processor and a modem processor, wherein the application processor mainly handles operations involving the operating system, user interface, and applications, and the modem processor mainly handles wireless communication signals, such as a baseband processor. It is understood that the aforementioned modem processor may also not be integrated into processor 710.

[0114] This application also provides a readable storage medium storing a program or instructions. When the program or instructions are executed by a processor, they implement the various processes of the above-described intelligent reminder method embodiments and achieve the same technical effect. To avoid repetition, they will not be described again here.

[0115] The processor is the processor in the electronic device described in the above embodiments. The readable storage medium includes computer-readable storage media, such as computer read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk.

[0116] This application embodiment also provides a chip, which includes a processor and a communication interface. The communication interface is coupled to the processor. The processor is used to run programs or instructions to implement the various processes of the above-described intelligent reminder method embodiments and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0117] It should be understood that the chip mentioned in the embodiments of this application may also be referred to as a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.

[0118] This application provides a computer program product, which is stored in a storage medium and executed by at least one processor to implement the various processes of the above-described intelligent reminder method embodiments, and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0119] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element. Furthermore, it should be noted that the scope of the methods and apparatuses in the embodiments of this application is not limited to performing functions in the order shown or discussed, but may also include performing functions substantially simultaneously or in the reverse order, depending on the functions involved. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

[0120] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a computer software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal (which may be a mobile phone, computer, server, or network device, etc.) to execute the methods described in the various embodiments of this application.

[0121] The embodiments of this application have been described above with reference to the accompanying drawings. However, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other forms under the guidance of this application without departing from the spirit and scope of the claims, and all of these forms are within the protection scope of this application.

Claims

1. A method for creating a reminder event, characterized in that, The method includes: Receive the first input while the alarm clock interface is displayed; In response to the first input, a reminder event is created based on the reminder trigger information corresponding to the first input; The reminder trigger information includes at least one of the following: operation behavior information, geographical location information, associated device status information, device status information, application status information, and associated task information.

2. The method according to claim 1, characterized in that, The geographic location information includes at least one of the geographic location information of the electronic device and the geographic location information of the interconnected devices of the electronic device.

3. The step of responding to the first input and creating a reminder event based on the reminder trigger information corresponding to the first input includes: In response to the first input, the reminder trigger information is determined; Receive the second input; In response to the second input, the reminder event is created based on the reminder trigger information and the target information corresponding to the second input; The target information includes at least one of the following: reminder event, reminder method, repeated reminder information, and reminder priority.

4. The method according to claim 1, characterized in that, After creating a reminder event based on the reminder trigger information corresponding to the first input, the method further includes: Obtain the scene status information of the electronic device; If the scene status information matches the reminder trigger information, the reminder event associated with the reminder trigger information is executed.

5. The method according to claim 4, characterized in that, The reminder trigger information also includes the reminder time; When the scene state information matches the reminder trigger information, executing the reminder event associated with the reminder trigger information includes: If the current time matches the reminder time and the scene status information matches the reminder trigger information, execute the reminder event associated with the reminder trigger information.

6. The method according to claim 4, characterized in that, When the scene state information matches the reminder trigger information, executing the reminder event associated with the reminder trigger information includes: The first duration during which the scene status information and the reminder trigger information are matched cumulatively; If the first duration reaches the preset duration, an alert event associated with the alert trigger information is executed.

7. The method according to claim 1, characterized in that, The first input includes a first sub-input and a second sub-input; the step of creating a reminder event in response to the first input based on the reminder trigger information corresponding to the first input includes: In response to the first sub-input to the event identifier information in the alarm clock interface, at least one candidate trigger information is displayed; Receive a second sub-input for at least one of the candidate trigger information; In response to the second sub-input, a reminder event is created based on the reminder trigger information corresponding to the second sub-input.

8. A reminder event creation device, characterized in that, The device includes: The receiving module is used to receive the first input when the alarm clock interface is displayed; A creation module is used to respond to the first input and create a reminder event based on the reminder trigger information corresponding to the first input; The reminder trigger information includes at least one of the following: operation behavior information, geographical location information, associated device status information, device status information, application status information, and associated task information.

9. An electronic device, characterized in that, It includes a processor and a memory, the memory storing a program or instructions that can run on the processor, the program or instructions being executed by the processor to implement the steps of the method as described in any one of claims 1-7.

10. A readable storage medium, characterized in that, The readable storage medium stores a program or instructions that, when executed by a processor, implement the steps of the method as described in any one of claims 1-7.

Images