Schedule generation method, electronic device and storage medium

Abstract

The present application provides a schedule generation method, an electronic device and a storage medium. The method comprises: acquiring an input text; processing the input text on the basis of user information of a first user to obtain a target task set, wherein the first user is a user using a first device, and the target task set comprises one or more target tasks corresponding to the first user; and generating a corresponding schedule on the basis of the target task set. Therefore, the present application can be conducive to adapting to various different complex scenarios, thereby improving the user experience.

Description

Schedule generation method, electronic device, and storage medium

[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office on November 30, 2023, with application number 202311630510.2 and application name “Schedule Generation Method, Electronic Device and Storage Medium”, the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of information technology, and in particular to a schedule generation method, electronic device, and storage medium. Background Art

[0003] As electronic devices like mobile phones continue to evolve, their functionality becomes increasingly powerful. Among these features, schedule reminders are a crucial feature. For example, a user can create a schedule on their electronic device, which can include pre-set tasks. When a schedule expires, the electronic device can remind the user to complete the tasks listed in the schedule.

[0004] However, the current schedule generation and reminder methods are relatively simple and cannot adapt to complex scenarios, which reduces the user experience.

[0005] Summary of the Invention

[0006] This application provides a schedule generation method, a schedule reminder method, an electronic device and a storage medium, which help to adapt to various complex scenarios and enhance the user experience.

[0007] In the first aspect, the present application provides a schedule generation method, applied to a first device, including: obtaining input text; processing the input text based on user information of a first user to obtain a target task set, wherein the first user is a user using the first device, and the target task set includes one or more target tasks corresponding to the first user; generating a corresponding schedule based on the target task set.

[0008] In this application, a schedule corresponding to a user is generated according to different user information, that is, a schedule can be generated according to different user adaptability, thereby improving the matching degree between the schedule and the user and enhancing the user experience.

[0009] In one possible implementation, the processing of the input text based on the user information of the first user to obtain a target task set includes: decomposing the input text to obtain an initial task set, wherein the initial task set includes one or more initial tasks; and completing and / or filtering the initial task set based on the user information of the first user to obtain a target task set.

[0010] In this application, during the schedule generation process, the information of the tasks included in the schedule is completed to avoid incomplete tasks due to missing information, and / or the tasks included in the schedule are filtered to remove tasks that are not relevant to the user, thereby improving the efficiency of task execution and enhancing the user experience.

[0011] In one possible implementation, the information completion and / or screening of the initial task set based on the user information of the first user includes: completing the information of the initial tasks that are missing information in the initial task set based on information queried in the user information of the first user and / or information inferred based on the user information of the first user.

[0012] In one possible implementation manner, the completing and / or filtering the initial task set based on the user information of the first user includes: filtering out completed tasks and / or tasks unrelated to the first user from the initial task set.

[0013] In one possible implementation, the target task set includes multiple target tasks, and the schedule generated based on the target task set is a chain schedule, wherein the multiple schedules in the chain schedule are generated by the multiple target tasks in the target task set, the multiple schedules in the chain schedule are arranged in a chronological order of their execution times, and the multiple schedules in the chain schedule have schedule associations.

[0014] In the present application, during the schedule generation process, multiple generated schedules are formed into a chain schedule with correlation, so that the efficiency of schedule creation can be improved and omission of schedules that the user needs to create can be avoided.

[0015] In one possible implementation, before processing the input text based on the user information of the first user, the method further includes: determining whether the input text contains the intention to generate a schedule; if the input text contains the intention to generate a schedule, processing the input text based on the user information of the first user.

[0016] In the present application, by determining the intention of the input text, invalid processing of the input text can be avoided, thereby improving the efficiency of schedule generation.

[0017] In one possible implementation manner, the user information of the first user includes personal information of the first user and / or social relationship information of the first user.

[0018] In one possible implementation, the personal information of the first user includes at least the address location information of the first user, and / or the historical behavior information of the first user, and / or the historical schedule information of the first user.

[0019] In one possible implementation manner, the content of the input text comes from at least one of email, social software or instant messaging.

[0020] In one possible implementation, after the corresponding schedule is generated based on the target task set, the method further includes: displaying a reminder interface in response to the expiration of the reminder time of the first schedule; wherein the reminder interface is used to remind the user to perform the target task corresponding to the expired schedule, and the reminder interface includes information for indicating the recommended service of the expired first schedule, and the information of the recommended service of the expired first schedule includes a target application, and the target application is an application for performing the target task corresponding to the expired first schedule; in response to the user's operation for opening the target application on the reminder interface, jumping to the target page, wherein the target page is the page displayed when the user completes the target task corresponding to the expired first schedule.

[0021] In this application, the recommended service in the reminder interface is used to directly reach the target page to complete the task corresponding to the due schedule, thereby improving the efficiency of task completion and enhancing the user experience.

[0022] In one possible implementation, after jumping to the target page, the method further includes: automatically entering target information corresponding to the recommended service of the expired first schedule on the target page, wherein the target information is task information required to be entered on the target page to complete the target task corresponding to the expired first schedule.

[0023] In one possible implementation, before automatically inputting the target information corresponding to the recommended service of the expired first schedule on the target page, the method further includes: determining whether the target information corresponding to the recommended service of the expired first schedule has missing information; if it is determined that the target information corresponding to the recommended service of the expired first schedule has missing information, completing the target information corresponding to the recommended service of the expired first schedule.

[0024] In this application, by completing the information of the recommended service, the situation where the recommended service cannot be executed due to missing information can be effectively avoided.

[0025] In one possible implementation, the completing the target information corresponding to the recommended service of the expired first schedule includes: if the expired first schedule is a schedule in a chain schedule, completing the target information corresponding to the recommended service of the expired first schedule based on information of other schedules in the chain schedule except the expired first schedule; wherein, the multiple schedules in the chain schedule are generated by multiple target tasks, the multiple schedules in the chain schedule are arranged in chronological order of their execution times, and the multiple schedules in the chain schedule have schedule associations.

[0026] In this application, since multiple schedules in a chain schedule are related to each other, the efficiency and accuracy of information completion can be improved by using other schedules in the chain schedule to complete the recommendation service of the schedule with missing information.

[0027] In one possible implementation, after generating the corresponding schedule based on the target task set, the method further includes: obtaining a first target schedule; in response to the distance between the current location of the first user and the target location indicated by the first target schedule being less than or equal to a preset threshold, the first device sends a reminder message, wherein the reminder message is used to remind the user to complete the task corresponding to the first target schedule.

[0028] In this application, reminders are generated based on the distance between the user's current location and the task location, which can improve the diversity and flexibility of reminders and meet the needs of users in different scenarios.

[0029] In one possible implementation, after the first device sends the reminder information, the method further includes: sending a schedule cancellation instruction to the third device in response to the received task completion notification; wherein the task indicated by the first target schedule is the same as the task indicated by the second target schedule, the second target schedule is a schedule in the third device, the task completion notification is used to notify that the task indicated by the first target schedule has been completed, and the schedule cancellation instruction is used to instruct the third device to cancel the second target schedule.

[0030] In this application, in a scenario where schedules are shared among multiple users, any user can notify other users to cancel the relevant schedules after completing a task, thereby avoiding the execution of invalid tasks, thereby improving task execution efficiency and enhancing user experience.

[0031] In a second aspect, the present application provides a schedule generation method, comprising: obtaining input text; processing the input text to obtain a target task set, wherein the target task set includes multiple target tasks; generating a chain schedule based on the target task set, wherein the multiple schedules in the chain schedule are arranged in chronological order according to the execution time of the schedules, and the multiple schedules in the chain schedule have schedule associations.

[0032] In a third aspect, the present application provides a schedule reminder method, comprising: displaying a reminder interface in response to the expiration of the reminder time of a first schedule; wherein, the reminder interface is used to remind the user to perform the target task corresponding to the expired schedule, and the reminder interface includes information for indicating the recommended service of the expired first schedule, and the information of the recommended service of the expired first schedule includes a target application, and the target application is an application for executing the target task corresponding to the expired first schedule; in response to the user's operation on the reminder interface for opening the target application, jumping to the target page, wherein the target page is the page displayed when the user completes the target task corresponding to the expired first schedule.

[0033] In one possible implementation, after jumping to the target page, the method further includes: automatically entering target information corresponding to the recommended service of the expired first schedule on the target page, wherein the target information is task information required to be entered on the target page to complete the target task corresponding to the expired first schedule.

[0034] In one possible implementation, before automatically inputting the target information corresponding to the recommended service of the expired first schedule on the target page, the method further includes: determining whether the target information corresponding to the recommended service of the expired first schedule has missing information; if it is determined that the target information corresponding to the recommended service of the expired first schedule has missing information, completing the target information corresponding to the recommended service of the expired first schedule.

[0035] In one possible implementation, the completing the target information corresponding to the recommended service of the expired first schedule includes: if the expired first schedule is a schedule in a chain schedule, completing the target information corresponding to the recommended service of the expired first schedule based on information of other schedules in the chain schedule except the expired first schedule; wherein, the multiple schedules in the chain schedule are generated by multiple target tasks, the multiple schedules in the chain schedule are arranged in chronological order of their execution times, and the multiple schedules in the chain schedule have schedule associations.

[0036] In a fourth aspect, the present application provides a schedule reminder method, applied to a first device, including: obtaining a first target schedule; in response to the distance between the current location of the first user and the target location indicated by the first target schedule being less than or equal to a preset threshold, the first device sends a reminder message, wherein the reminder message is used to remind the user to complete the task corresponding to the first target schedule.

[0037] In one possible implementation, after the first device sends the reminder information, the method further includes: sending a schedule cancellation instruction to the third device in response to the received task completion notification; wherein the task indicated by the first target schedule is the same as the task indicated by the second target schedule, the second target schedule is a schedule in the third device, the task completion notification is used to notify that the task indicated by the first target schedule has been completed, and the schedule cancellation instruction is used to instruct the third device to cancel the second target schedule.

[0038] In a fifth aspect, the present application provides a schedule generation device, comprising one or more functional modules, wherein the one or more functional modules are used to implement the schedule generation method as described in the first aspect.

[0039] In a sixth aspect, the present application provides a schedule generation device, comprising one or more functional modules, wherein the one or more functional modules are used to implement the schedule generation method as described in the second aspect.

[0040] In a seventh aspect, the present application provides a schedule reminder device, comprising one or more functional modules, wherein the one or more functional modules are used to implement the schedule reminder method as described in the third aspect.

[0041] In an eighth aspect, the present application provides a schedule reminder device, comprising one or more functional modules, wherein the one or more functional modules are used to implement the schedule reminder method as described in the fourth aspect.

[0042] In the ninth aspect, the present application provides an electronic device comprising: a processor and a memory, the memory being used to store a program; the processor being used to run the program to implement the schedule generation method as described in the first and second aspects, or to implement the schedule reminder method as described in the third and fourth aspects.

[0043] In the tenth aspect, the present application provides a readable storage medium, which stores a program. When the program is run on an electronic device, the electronic device implements the schedule generation method described in the first and second aspects, or implements the schedule reminder method described in the third and fourth aspects.

[0044] In the eleventh aspect, the present application provides a program, which, when run on a processor of an electronic device, enables the electronic device to execute the schedule generation method described in the first and second aspects, or implement the schedule reminder method described in the third and fourth aspects.

[0045] In one possible design, the program in the eleventh aspect may be stored in whole or in part on a storage medium packaged together with the processor, or may be stored in whole or in part on a memory not packaged together with the processor. BRIEF DESCRIPTION OF THE DRAWINGS

[0046] FIG1 is a schematic structural diagram of an electronic device provided in an embodiment of the present application;

[0047] FIG2 is a diagram of the system architecture provided by an embodiment of the present application;

[0048] FIG3 is a flow chart of an embodiment of a schedule generation method provided by the present application;

[0049] 4A and 4B are schematic diagrams of a text copying method provided in an embodiment of the present application;

[0050] FIG5 is a schematic diagram of triggering schedule generation provided in an embodiment of the present application;

[0051] 6A and 6B are schematic diagrams of task information provided in an embodiment of the present application;

[0052] FIG7 is a schematic diagram of an embodiment of adding a schedule provided by the present application;

[0053] FIG8 is a schematic diagram of another embodiment of adding a schedule provided by the present application;

[0054] FIG9 is a flow chart of an embodiment of a schedule reminder method provided by the present application;

[0055] FIG10 is a schematic diagram of service recommendations provided in an embodiment of the present application;

[0056] FIG11 is a schematic diagram of a target page provided in an embodiment of the present application;

[0057] FIG12 is a flow chart of another embodiment of the schedule reminder method provided by the present application;

[0058] FIG13 is a schematic structural diagram of an embodiment of a schedule generating device provided by the present application;

[0059] FIG14 is a schematic structural diagram of another embodiment of the schedule generating device provided by the present application. DETAILED DESCRIPTION

[0060] In the embodiments of this application, unless otherwise specified, the character " / " indicates that the associated objects are in an "or" relationship. For example, A / B can represent A or B. "And / or" describes the relationship between the associated objects, indicating that three possible relationships exist. For example, "A and / or B" can represent: A exists alone, A and B exists simultaneously, or B exists alone.

[0061] It should be pointed out that the words "first", "second", etc. involved in the embodiments of this application are only used for distinguishing description purposes, and cannot be understood as indicating or implying relative importance or implicitly indicating the number of technical features indicated, nor can they be understood as indicating or implying order.

[0062] In the embodiments of the present application, "at least one" refers to one or more, and "plurality" refers to two or more. In addition, "at least one of the following" or similar expressions refers to any combination of these items, which may include any combination of single items or plural items. For example, at least one of A, B, or C can represent: A, B, C, A and B, A and C, B and C, or A, B and C. Among them, each of A, B, and C can be an element itself, or a set containing one or more elements.

[0063] In the embodiments of this application, the terms "exemplary," "in some embodiments," and "in another embodiment" are used to indicate examples, illustrations, or descriptions. Any embodiment or design described as "exemplary" in this application should not be construed as preferred or advantageous over other embodiments or designs. Rather, the use of the word "exemplary" is intended to present concepts in a concrete manner.

[0064] In the embodiments of this application, the terms "of," "corresponding," and "relevant" may sometimes be used interchangeably. It should be noted that, when the distinction between them is not emphasized, the meanings they convey are the same. In the embodiments of this application, the terms "communication" and "transmission" may sometimes be used interchangeably. It should be noted that, when the distinction between them is not emphasized, the meanings they convey are the same. For example, "transmission" may include "sending" and / or "receiving," and may be either a noun or a verb.

[0065] In the embodiments of this application, "equal to" can be used in conjunction with "greater than" and is applicable to the technical solution adopted when "greater than" is used, and can also be used in conjunction with "less than" and is applicable to the technical solution adopted when "less than" is used. It should be noted that when "equal to" is used in conjunction with "greater than", it cannot be used in conjunction with "less than"; and when "equal to" is used in conjunction with "less than", it cannot be used in conjunction with "greater than".

[0066] With the continuous updating of technology in electronic devices such as mobile phones, their functions are becoming more and more powerful. Among them, schedule reminder is one of the more important functions. For example, a user can create a schedule in an electronic device, which can include tasks preset by the user. When the schedule expires, the electronic device can remind the user so that the user can perform the tasks corresponding to the schedule.

[0067] However, the current schedule generation is relatively simple, and only stays at the generation of simple schedules based on time and tasks, which cannot adapt to complex scenarios, thereby reducing the user experience.

[0068] To address the above issues, embodiments of the present application provide a schedule generation method for an electronic device. The electronic device may be a mobile terminal, which may also be referred to as user equipment (UE), access terminal, subscriber unit, subscriber station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent, or user device. The mobile terminal can be a station (STAION, ST) in a WLAN, a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA) device, a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a vehicle networking terminal, a computer, a laptop computer, a handheld communication device, a handheld computing device, a satellite wireless device, a wireless modem card, a TV set-top box (STB), customer premise equipment (CPE) and / or other devices used to communicate on a wireless system and a next-generation communication system, for example, a mobile terminal in a 5G network or a mobile terminal in a future evolved Public Land Mobile Network (PLMN) network, etc.

[0069] In some optional embodiments, the electronic device may also be a wearable device. Wearable devices, also known as wearable smart devices, are a general term for wearable devices that are intelligently designed and developed using wearable technology for everyday wear, such as smart watches and smart bracelets.

[0070] FIG1 exemplarily shows a schematic structural diagram of an electronic device 100 .

[0071] The electronic device 100 may include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, an earphone interface 170D, a sensor module 180, a button 190, a motor 191, an indicator 192, a camera 193, a display screen 194, etc.

[0072] It should be understood that the structure illustrated in the embodiments of the present invention does not constitute a specific limitation on the electronic device 100. In other embodiments of the present application, the electronic device 100 may include more or fewer components than shown, or may combine or separate certain components, or arrange the components differently. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0073] The processor 110 may include one or more processing units. For example, the processor 110 may include an application processor (AP), a modem processor, a graphics processing unit (GPU), an image signal processor (ISP), a controller, a video codec, a digital signal processor (DSP), a baseband processor, and / or a neural-network processing unit (NPU). The different processing units may be independent devices or integrated into one or more processors.

[0074] The controller can generate operation control signals according to the instruction operation code and timing signal to complete the control of instruction fetching and execution.

[0075] Processor 110 may also include a memory for storing instructions and data. In some embodiments, the memory in processor 110 is a cache memory. This memory can store instructions or data that have just been used or are being recycled by processor 110. If processor 110 needs to use the same instruction or data again, it can directly access the memory. This avoids duplicate accesses, reduces processor 110 latency, and thus improves system efficiency.

[0076] The charging management module 140 is configured to receive charging input from a charger. The charger can be either a wireless charger or a wired charger. In some wired charging embodiments, the charging management module 140 can receive charging input from the wired charger via the USB interface 130. In some wireless charging embodiments, the charging management module 140 can receive wireless charging input via the wireless charging coil of the electronic device 100. While charging the battery 142, the charging management module 140 can also provide power to the electronic device via the power management module 141.

[0077] The power management module 141 is used to connect the battery 142, the charging management module 140, and the processor 110. The power management module 141 receives input from the battery 142 and / or the charging management module 140, and provides power to the processor 110, the internal memory 121, the display 194, the camera 193, and the wireless communication module 160. The power management module 141 can also be used to monitor parameters such as battery capacity, battery cycle count, and battery health status (leakage, impedance). In some other embodiments, the power management module 141 can also be set in the processor 110. In other embodiments, the power management module 141 and the charging management module 140 can also be set in the same device.

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

[0079] 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 a single or multiple communication frequency bands. Different antennas can also be reused to improve antenna utilization. For example, antenna 1 can be reused as a diversity antenna for a wireless local area network. In other embodiments, the antennas can be used in conjunction with a tuning switch.

[0080] The mobile communication module 150 can provide solutions for wireless communications including 2G / 3G / 4G / 5G applied to the electronic device 100. The mobile communication module 150 may include at least one filter, a switch, a power amplifier, a low noise amplifier (LNA), etc. The mobile communication module 150 can receive electromagnetic waves from the antenna 1, and filter, amplify, and process the received electromagnetic waves, and transmit them to the modulation and demodulation processor for demodulation. The mobile communication module 150 can also amplify the signal modulated by the modulation and demodulation processor, and convert it into electromagnetic waves for radiation through the antenna 1. In some embodiments, at least some of the functional modules of the mobile communication module 150 can be set in the processor 110. In some embodiments, at least some of the functional modules of the mobile communication module 150 can be set in the same device as at least some of the modules of the processor 110.

[0081] The modem processor may include a modulator and a demodulator. The modulator is used to modulate the low-frequency baseband signal to be transmitted into a medium-high frequency signal. The demodulator is used to demodulate the received electromagnetic wave signal into a low-frequency baseband signal. The demodulator then transmits the demodulated low-frequency baseband signal to the baseband processor for processing. After being processed by the baseband processor, the low-frequency baseband signal is passed to the application processor. The application processor outputs a sound signal through an audio device (not limited to the speaker 170A, the receiver 170B, etc.) or displays an image or video through the display screen 194. In some embodiments, the modem processor may be an independent device. In other embodiments, the modem processor may be independent of the processor 110 and be set in the same device as the mobile communication module 150 or other functional modules.

[0082] The wireless communication module 160 can provide wireless communication solutions including wireless local area networks (WLAN) (such as wireless fidelity (WIFI) networks), Bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), infrared (IR), etc., which are applied to the electronic device 100. The wireless communication module 160 can be one or more devices that integrate at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via the antenna 2, frequency modulates and filters the electromagnetic wave signals, and sends the processed signals to the processor 110. The wireless communication module 160 can also receive the signal to be sent from the processor 110, frequency modulate it, amplify it, and convert it into electromagnetic waves for radiation through the antenna 2.

[0083] In some embodiments, the antenna 1 of the electronic device 100 is coupled to the mobile communication module 150, and the antenna 2 is coupled to the wireless communication module 160, so that the electronic device 100 can communicate with a network and other devices through wireless communication technologies. The wireless communication technologies 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 technology. The GNSS may include a global positioning system (GPS), a global navigation satellite system (GLONASS), a Beidou navigation satellite system (BDS), a quasi-zenith satellite system (QZSS) and / or a satellite based augmentation system (SBAS).

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

[0085] Display screen 194 is used to display images, videos, and the like. Display screen 194 includes a display panel. The display panel can be a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode (AMOLED), a flexible light-emitting diode (FLED), a MiniLED, a MicroLED, a Micro-oLed, or a quantum dot light-emitting diode (QLED). In some embodiments, electronic device 100 may include one or N display screens 194, where N is a positive integer greater than one.

[0086] The electronic device 100 can implement a shooting function through an ISP, a camera 193, a video codec, a GPU, a display screen 194, and an application processor.

[0087] The NPU is a neural network (NN) computing processor. Drawing on the structure of biological neural networks, such as the transmission patterns between neurons in the human brain, it rapidly processes input information and can continuously self-learn. The NPU can enable intelligent cognitive applications in electronic device 100, such as image recognition, face recognition, speech recognition, and text comprehension.

[0088] The external memory interface 120 can be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the electronic device 100. The external memory card communicates with the processor 110 via the external memory interface 120 to implement data storage functions. For example, files such as music and videos can be stored on the external memory card.

[0089] The internal memory 121 can be used to store computer executable program codes, which include instructions. The internal memory 121 may include a program storage area and a data storage area. Among them, the program storage area may store an operating system, an application required for at least one function (such as a sound playback function, an image playback function, etc.), etc. The data storage area may store data created during the use of the electronic device 100 (such as audio data, a phone book, etc.), etc. In addition, the internal memory 121 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, a universal flash storage (UFS), etc. The processor 110 executes various functional applications and data processing of the electronic device 100 by running instructions stored in the internal memory 121 and / or instructions stored in a memory provided in the processor.

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

[0091] The audio module 170 is used to convert digital audio information into analog audio signal output, and is also used to convert analog audio input into digital audio signals. The audio module 170 can also be used to encode and decode audio signals. In some embodiments, the audio module 170 can be provided in the processor 110, or some functional modules of the audio module 170 can be provided in the processor 110.

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

[0093] The receiver 170B, also called a "handset", is used to convert audio electrical signals into sound signals. When the electronic device 100 receives a call or a voice message, the user can place the receiver 170B close to the ear to hear the voice.

[0094] Microphone 170C, also known as "microphone" or "microphone", is used to convert sound signals into electrical signals. When making a call or sending a voice message, the user can speak by putting their mouth close to the microphone 170C to input the sound signal into the microphone 170C. The electronic device 100 can be provided with at least one microphone 170C. In other embodiments, the electronic device 100 can be provided with two microphones 170C, which can not only collect sound signals but also realize noise reduction function. In other embodiments, the electronic device 100 can also be provided with three, four or more microphones 170C to collect sound signals, reduce noise, identify the source of sound, realize directional recording function, etc.

[0095] The headphone jack 170D is used to connect a wired headphone and can be the USB interface 130 or a 3.5mm open mobile terminal platform (OMTP) standard interface or a cellular telecommunications industry association of the USA (CTIA) standard interface.

[0096] The buttons 190 include a power button, a volume button, and the like. The buttons 190 may be mechanical buttons or touch buttons. The electronic device 100 may receive key inputs and generate key signal inputs related to user settings and function control of the electronic device 100.

[0097] Motor 191 can generate vibration prompts. Motor 191 can be used for incoming call vibration prompts, and can also be used for touch vibration feedback. For example, touch operations acting on different applications (such as taking pictures, audio playback, etc.) can correspond to different vibration feedback effects. For touch operations acting on different areas of the display screen 194, motor 191 can also correspond to different vibration feedback effects. Different application scenarios (for example: time reminders, receiving messages, alarm clocks, games, etc.) can also correspond to different vibration feedback effects. The touch vibration feedback effect can also support customization.

[0098] The indicator 192 may be an indicator light, which may be used to indicate the charging status, power level changes, messages, missed calls, notifications, etc.

[0099] Figure 2 is a diagram of a network architecture provided by an embodiment of the present application. As shown in Figure 2, the network architecture may include multiple electronic devices, for example, the multiple electronic devices may be electronic device 1, electronic device 2, ..., electronic device n, where n is a positive integer, and the multiple electronic devices may be the aforementioned electronic device 100.

[0100] It is understandable that multiple electronic devices can communicate with each other through a mobile communication network, or multiple electronic devices can communicate with each other through the mobile Internet, or multiple electronic devices can communicate with each other through local networks such as Wireless Fidelity (WiFi), or multiple electronic devices can communicate with each other through other forms of networks. The embodiments of the present application do not specifically limit the communication method between multiple electronic devices.

[0101] It should be noted that for the same input text, different schedules can be generated from different user perspectives, that is, different users can have different schedules. However, current schedule generation methods do not distinguish between users for the same input text, that is, the schedules generated for different users for the same input text are the same, and the schedule only includes information such as time and tasks. The schedule generation method provided in the embodiment of the present application can generate a corresponding schedule for the same input text based on the user using the current electronic device, thereby achieving adaptive generation of schedules to meet the usage needs of multiple users.

[0102] For example, assume there are three users, namely user 1, user 2, and user 3. User 1 uses electronic device 1, user 2 uses electronic device 2, and user 3 uses electronic device 3. Assume that electronic devices 1, 2, and 3 simultaneously obtain the same input text. For ease of explanation, the same input text is referred to as input text 1. Then, electronic device 1 can generate schedule 1 for user 1, electronic device 2 can generate schedule 2 for user 2, and electronic device 3 can generate schedule 3 for user 3. Schedule 1, schedule 2, and schedule 3 are different from each other.

[0103] Among them, the above-mentioned input text can be the content in social software, for example, the input text can be the chat history of multiple users, or the above-mentioned input text can be push messages, notification messages, or instant messages such as short messages, or the above-mentioned input text can be the content in an email. The embodiment of this application does not specifically limit the type of input text.

[0104] In some optional embodiments, multiple schedules generated for any user can be chained. These chained schedules can be arranged in chronological order, or they can be arranged in the order in which tasks were executed. Schedules can be related to each other, and this is not specifically limited in this embodiment of the present application. Compared to the prior art, which can only create a single schedule, this embodiment of the present application can greatly improve the efficiency of schedule creation and prevent users from missing schedules they need to create.

[0105] For example, taking user 1 as an example, assuming that the intention recognized from input text 1 is to go to the movies, the input text 1 may contain two chain tasks: buying movie tickets and going to the movies, so that a schedule corresponding to the two chain tasks of buying movie tickets and going to the movies can be generated, and buying movie tickets needs to be executed before going to the movies.

[0106] In some optional embodiments, to improve task execution efficiency and enhance the user experience, when creating a schedule, service recommendations can be associated with the corresponding task. This allows the user to use the recommended service to perform the corresponding task when the schedule is reminded. Compared to the existing technology where schedule reminders are simply reminders, the service recommendations in the embodiments of the present application can greatly improve the efficiency of user task execution.

[0107] The recommended service may be a system application, or the recommended service may be a third-party application. The embodiment of the present application does not specifically limit the type of the recommended service.

[0108] For example, taking the task of purchasing movie tickets as an example, after generating a schedule for purchasing movie tickets, the task of purchasing movie tickets can be associated with a ticket purchasing application, so that when the user receives a schedule reminder, he can click on the associated ticket purchasing application and enter the ticket purchasing application to purchase tickets, without having to look for or search for related ticket purchasing applications, thereby improving the efficiency of task execution.

[0109] In some optional embodiments, in order to further improve the efficiency of task execution, when the user enters the recommended service, he or she can directly enter the page associated with the currently executed task without entering the homepage of the recommended service, thereby improving efficiency.

[0110] For example, still taking the task of buying movie tickets as an example, when the user clicks on the associated ticket purchasing application, he can directly enter the ticket purchasing page without entering the homepage of the ticket purchasing application, thus allowing the user to avoid tedious operations.

[0111] In some optional embodiments, for the same schedule, different users can generate different reminders based on different triggering conditions. This can meet the needs of multiple people being reminded of the same schedule. The triggering condition can be distance, or other conditions, which are not specifically limited in the embodiments of the present application.

[0112] For example, assuming that user 1, user 2, and user 3 share the same schedule, which may be a task corresponding to picking up a package at a certain destination, when any one of user 1, user 2, and user 3 approaches the destination, a corresponding schedule reminder may be generated to complete the task of picking up the package.

[0113] Next, the schedule generation method provided in the embodiment of the present application is described with reference to FIG. 3 , FIG. 4A , FIG. 4B , FIG. 5 , FIG. 6A , FIG. 6B , and FIG. 7 - FIG. 10 .

[0114] FIG3 is a flow chart of an embodiment of a schedule generation method provided by the present application, which specifically includes the following steps:

[0115] Step 301: The first device obtains input text.

[0116] Specifically, the first device may be any electronic device among a plurality of electronic devices.

[0117] As mentioned above, the input text can be the chat content between multiple users, or the input text can be meeting minutes, or the input text can be the content in an email, or the input text can be the content in an instant message, or the input text can be other types of content. This application does not specifically limit the type of input text.

[0118] Taking input text as chat content as an example, multiple users can have a conversation in the chat box, and any user can copy the content in the chat box as input text.

[0119] In some optional embodiments, the user may select the content in the chat box as the input text by selecting the entire content displayed on the current interface as the input text. For example, the user may copy the entire conversation content on the current display interface to obtain the input text.

[0120] Now, an exemplary explanation is given by taking Figure 4A as an example. Referring to Figure 4A, interface 401 is a chat dialog box between multiple users. Taking the multiple users as user 1, user 2 and user 3 as an example, the current interface contains a total of 5 chat records, of which there are 2 chat records corresponding to user 1, 1 chat record corresponding to user 2, and 2 chat records corresponding to user 3. The user can copy all the contents in interface 401 (for example, the 5 chat records in the current interface) as input text.

[0121] In some optional embodiments, a user may select content in a chat box as input text by selecting and copying a portion of the content currently displayed on the interface as input text. For example, a user may select and copy several records in a chat dialog box as input text, thereby filtering out some noise information and improving text recognition efficiency.

[0122] Now, an exemplary explanation is given by taking Figure 4B as an example. Referring to Figure 4B, interface 402 is a chat dialog box between multiple users. Still taking the multiple users as User 1, User 2, and User 3 as an example, the current interface contains a total of 5 chat records, of which there are 2 chat records corresponding to User 1, 1 chat record corresponding to User 2, and 2 chat records corresponding to User 3. Then, the user can select a chat record by clicking the control corresponding to the chat record, and can copy the selected chat record. For example, the user can select and copy 2 chat records of User 1, 1 chat record of User 2, and 1 chat record of User 3 as input text. It can be understood that the chat content and method selected in the above embodiment are only exemplary and do not constitute a limitation to the embodiments of the present application. In some embodiments, the user can select content according to his or her own needs, or select chat content by other methods other than controls.

[0123] In some optional embodiments, a user may select content in a chat box as input text by selecting all or part of the content in multiple interfaces as input text. For example, chat records of multiple users may involve multiple interfaces, and the user may scroll through the interfaces to select all or part of the content in the multiple interfaces as input text.

[0124] Step 302: The first device determines whether the input text contains an intention to generate a schedule.

[0125] Specifically, after acquiring the input text, the first device may determine whether the input text contains an intention to generate a schedule.

[0126] Among them, whether the input text contains the intention to generate a schedule can be determined through an existing recognition model. For example, the recognition model can be a binary classification model, which can be obtained in advance through training. This application does not specifically limit the recognition model.

[0127] If the first device determines that the input text contains the intention to generate a schedule, step 303 may be executed. Alternatively,

[0128] If the first device determines that the input text does not contain the intention to generate a schedule, the process ends.

[0129] In some optional embodiments, after the first device determines that the input text contains the intention to generate a schedule, it can also display a corresponding control or menu on the current interface to allow the user to choose whether to generate a schedule in the first device.

[0130] For example, taking FIG4B as an example, when the first device determines that the input text contains the intention to generate a schedule, it can display an application icon for generating a schedule on the current interface. For example, assuming that the application for generating a schedule is a calendar application, the icon of the calendar application can be displayed, thereby obtaining the interface 500 shown in FIG5. On the interface 500 shown in FIG5, the user can click icon 501 to enter the calendar application to generate a corresponding schedule in the calendar application.

[0131] In some optional embodiments, the user may be advised whether to jump to the page of the application for generating the schedule through a system application, a third-party application, or other interactive methods. This embodiment of the present application does not specifically limit this.

[0132] Step 303: The first device decomposes the input text to obtain an initial task set.

[0133] Specifically, the first user is a user using the first device, and the initial task set may include one or more initial tasks.

[0134] In some optional embodiments, after the first device determines that the input text contains the intention to generate a schedule, it can decompose the input text into tasks to obtain one or more initial tasks, each of which may include but is not limited to one or more information of time, place, person, and event.

[0135] In some optional embodiments, the multiple initial tasks obtained by task decomposition may be related tasks, and the multiple related tasks may be referred to as chain tasks. For example, the chain tasks may be multiple tasks arranged in chronological order, wherein the chronological order may be determined according to the order in which the tasks are executed. In the prior art, only one task is usually obtained by recognizing the input text, and a corresponding schedule is generated based on the task. However, the input text may very likely contain multiple tasks. Since the prior art does not decompose the tasks in the schedule, it is impossible to identify more tasks, which may result in the loss of some tasks, thereby reducing the user experience.

[0136] In this application, tasks are decomposed based on their relevance to obtain a chain of tasks, thereby mining multiple tasks in the input text. It can be seen that the embodiment of this application decomposes the input text into tasks to obtain chained tasks, thereby allowing users to fully execute all tasks indicated in the input text, effectively preventing users from forgetting tasks.

[0137] For example, assuming that a chat record contains information about going to a movie on a certain date in a certain year, the prior art can generate a schedule for going to a movie on a certain date in a certain year based on the chat information. Since a schedule for going to a movie on a certain date in a certain year can include two tasks, for example, the two tasks can be the task of buying movie tickets and the task of watching the movie, the embodiment of the present application can generate two schedules based on the chat information: one schedule for buying movie tickets and the other schedule for going to a movie on a certain date in a certain year. It can be seen that compared to the embodiment of the present application, the prior art lacks the schedule for buying movie tickets, and thus lacks the task of buying movie tickets, which may result in the user not being able to watch the movie because they forget to buy movie tickets.

[0138] In step 304 , the first device determines whether there is any missing information in the one or more initial tasks obtained after the disassembly.

[0139] Specifically, after the first device decomposes the input text into tasks, it can determine whether there is any missing information in one or more initial tasks obtained after the decomposition.

[0140] The method for determining whether there is information missing in one or more initial tasks obtained after the decomposition may be to determine whether the information field in the initial task contains corresponding information.

[0141] It is understandable that the information fields of a task can be preset. For example, a task can include information fields such as time, place, person, event, etc., but this does not constitute a limitation on the embodiments of the present application. In some embodiments, a task can also include more or fewer information fields, and the information fields can be selected according to the specific usage scenario or actual needs.

[0142] After breaking down the input text into tasks, the content can be written into the corresponding information fields. This allows us to determine whether any information is missing from one or more of the initial tasks obtained after the breakdown. If any information field corresponding to an initial task does not contain the corresponding content, then the initial task corresponding to that information field has information missing. If all information fields corresponding to an initial task contain the corresponding content, then the initial task corresponding to that information field has no information missing.

[0143] The information fields in the task are now described exemplarily with reference to FIG6A and FIG6B , assuming that the preset information fields include information fields such as time, place, person, and event.

[0144] Referring to Figure 6A , by decomposing the input text into tasks, we can obtain Initial Task 1 and Initial Task 2. Initial Task 1 and Initial Task 2 contain fields such as time, location, person, and event. The time, person, and event information fields in Initial Task 1 all contain corresponding content, while the location information field in Initial Task 1 lacks corresponding content. However, the time, location, person, and event information fields in Initial Task 2 all contain corresponding content. Since the location information field in Initial Task 1 lacks corresponding content, all information fields in Initial Task 2 contain corresponding content. Therefore, it can be determined that Initial Task 1 has missing information, while Initial Task 2 does not.

[0145] Referring to Figure 6B , by breaking down the input text into tasks, we can obtain Initial Task 1 and Initial Task 2. Initial Task 1 and Initial Task 2 contain fields such as time, location, person, and event. The time, location, person, and event information fields in Initial Task 1 and Task 2 all contain corresponding content. Therefore, there is no missing information in Initial Task 1 or Initial Task 2.

[0146] If the first device determines that there is missing information in one or more initial tasks obtained after disassembly, step 305 may be executed.

[0147] If the first device determines that there is no missing information in the one or more initial tasks obtained after disassembly, the initial task set may be considered as the target task set, and step 306 may be executed.

[0148] Step 305 : The first device completes and / or filters one or more initial tasks with missing information based on the user information of the first user to obtain a target task set.

[0149] Specifically, the target task set may include one or more target tasks corresponding to the first user, wherein the one or more target tasks may be obtained by completing and / or filtering one or more initial tasks with missing information.

[0150] For example, taking the network architecture shown in Figure 2 as an example, for user 1 using electronic device 1, the first user is user 1, and the first device is electronic device 1, that is, a target task corresponding to user 1 can be generated in electronic device 1; or, for user 2 using electronic device 2, the first user is user 2, and the first device is electronic device 2, that is, a target task corresponding to user 2 can be generated in electronic device 2; or, for user n using electronic device n, the first user is user n, and the first device is electronic device n, that is, a target task corresponding to user n can be generated in electronic device n.

[0151] In some optional embodiments, when the first device determines that one or more initial tasks obtained after disassembly are missing information, the first device may complete the information of the initial tasks with missing information based on the user information of the first user. The number of initial tasks with missing information may be one or more, and the user information of the first user may include the personal information of the first user and / or the social relationship information of the first user. The personal information of the first user may include but is not limited to the geographic location of the first user, the historical behavior of the first user, the historical schedule of the first user, and other information. The social relationship information of the first user may include but is not limited to information such as classmates, colleagues, family members, and friends.

[0152] In some optional embodiments, the user information of the first user may be from a user's personal knowledge base. The user's personal knowledge base may be described in the form of a knowledge graph, or in other forms, which are not specifically limited in this embodiment of the present application.

[0153] It is understandable that the user information of the first user may also be represented in forms other than the user's personal knowledge base, for example, documents, tables, charts, etc., and this embodiment of the present application does not impose any special limitation on this.

[0154] Understandably, missing information is often caused by the user's conversation being too colloquial or concise. Therefore, using the user's personal knowledge base can help complete the information in the chat, further complementing the information fields in the initial task.

[0155] In some optional embodiments, for non-customary references, information can be supplemented by searching the user's personal knowledge base. Non-customary references can also be called specific references, and the content they refer to is specific.

[0156] For example, suppose a chat contains "Xiao A's birthday." Since "Xiao A's birthday" does not contain an exact time, the information is missing. However, "Xiao A's birthday" does have an exact time. Therefore, by searching the user's personal knowledge base, Xiao A's birthday time can be easily and quickly found, thus completing the information.

[0157] For example, suppose the chat includes "the last movie theater I went to." Since "the last movie theater I went to" does not contain the exact location, the information is missing. However, "the last movie theater I went to" does have a specific location. By searching the user's personal knowledge base, the name and location of the movie theater that was visited last time can be easily and quickly found, thus completing the information.

[0158] For example, suppose the chat content contains "Lao Wang's daughter". Since "Lao Wang's daughter" does not contain a specific person, the information is missing. However, "Lao Wang's daughter" has a specific name. By searching the user's personal knowledge base, the exact name of Lao Wang's daughter can be easily and quickly found, thus completing the information.

[0159] In some optional embodiments, for habitual references, information can be supplemented by knowledge reasoning based on the content in the user's personal knowledge base. Habitual references can also be called non-specific references, as the content they refer to is non-specific.

[0160] For example, suppose a chat contains "the hot pot restaurant the three of us often go to." Since "the hot pot restaurant the three of us often go to" doesn't include a specific location, information is missing. Furthermore, since "the hot pot restaurant the three of us often go to" doesn't contain a specific reference, the required information cannot be obtained through a query. Therefore, we can use knowledge reasoning in the user's personal knowledge base to count the hot pot restaurants the three of us visit most frequently. This allows us to infer the exact name and location of the hot pot restaurant the three of us often go to, thus completing the information.

[0161] In some optional embodiments, after the first device obtains the initial task set, it may further filter one or more initial tasks in the initial task set to exclude tasks completed by the first user and / or tasks not related to the first user.

[0162] For example, suppose four initial tasks are generated through task decomposition: Initial Task 1, Initial Task 2, Initial Task 3, and Initial Task 4. Task 1 is for purchasing concert tickets, Task 2 is for purchasing train tickets, Task 3 is for booking a hotel, and Task 4 is for booking a taxi. If the first user has already booked the train ticket, Task 2 is a completed task and can be eliminated.

[0163] For another example, suppose that multiple initial tasks are obtained through task decomposition, and the multiple initial tasks include the task of "purchasing a train ticket from place A to place B". Assuming that the first user is in place B, the task of "purchasing a train ticket from place A to place B" is a task irrelevant to the first user and can be filtered out.

[0164] It is understandable that the first device can complete the information of the initial task set alone, or the first device can filter the initial task set alone, or the first device can complete and filter the information of the initial task set at the same time. The embodiments of the present application do not specifically limit this.

[0165] In some optional embodiments, when the first device decomposes the input text, it can decompose it based on the user information of the first user, and can complete and / or filter the information while decomposing it. This can avoid the redundant step of obtaining the initial task set through decomposition, that is, the target task set can be obtained in one step, thereby improving the efficiency of obtaining the target task.

[0166] Step 306: The first device generates a corresponding schedule based on the target task set.

[0167] Specifically, after determining one or more target tasks in the target task set, a corresponding schedule can be generated based on the one or more target tasks in the target task set, wherein the correspondence between the schedule and the target tasks is one-to-one, that is, one target task corresponds to one schedule.

[0168] It is understandable that the schedule generated by the first device corresponds to the first user, that is, when the schedule expires, the first user can be reminded to perform the target task corresponding to the schedule.

[0169] For example, assuming that three target tasks are finally obtained, namely target task 1, target task 2 and target task 3, schedule 1 corresponding to target task 1, schedule 2 corresponding to target task 2 and schedule 3 corresponding to target task 3 can be generated.

[0170] In some optional embodiments, if the target task set includes multiple target tasks, and the multiple target tasks are chain tasks, then the corresponding multiple schedules generated can be chain schedules, wherein the multiple schedules in the chain schedule are arranged in the order of the execution time of the schedules, and the multiple schedules in the chain schedule have schedule associations.

[0171] In some optional embodiments, after a corresponding schedule is generated based on a target task, the user may also select from a plurality of generated schedules to be selected to generate a schedule required by the user.

[0172] For example, in an application for displaying schedules (eg, a calendar application), multiple schedules to be selected may be displayed, and the user may select a final schedule in the display interface of the calendar application, and the final schedule may be displayed in the application for displaying schedules.

[0173] As an example, let's use Figure 7 to illustrate this. Assume that two candidate schedules are generated based on the target task. These two candidate schedules are Schedule 1 and Schedule 2, and can be displayed in the calendar application's display interface. The user can select either or both of Schedule 1 and Schedule 2 as the final schedule, which can then be displayed in the calendar application.

[0174] For another example, a plurality of schedules to be selected may be displayed in the chat box, and the user may determine the final schedule by selecting in the display interface of the chat box, and the final schedule may be displayed in an application for displaying schedules (eg, a calendar application).

[0175] As an example, let's consider Figure 8. Assume that two schedules are generated based on the target task. These two schedules are Schedule 1 and Schedule 2, and can be displayed in the chat box interface. The user can select either one or both of Schedule 1 and Schedule 2 as the final schedule, which can then be displayed in the calendar application.

[0176] In some optional embodiments, after a schedule is generated, target information may be associated with the corresponding tasks in the schedule. The target information may be the information required when using a target application to execute the target task in the schedule. The target application may be an application included in a recommendation service. The target application may be used to complete the target task in the schedule. The recommendation service may be displayed on a reminder page after the schedule expires. For example, if a schedule includes a ticket purchase task, ticket purchase information may be associated with the schedule. The ticket purchase information may include information such as which cinema to buy, how many people to buy tickets for, and which ticket number to buy. Therefore, after the ticket purchase schedule expires, a recommended service including a ticket purchase application may be displayed on the displayed reminder page. Since the ticket purchase information is associated with the schedule, the user does not need to enter the ticket purchase information when purchasing tickets through the ticket purchase application, thereby improving ticket purchase efficiency and user experience.

[0177] In some optional embodiments, for chained schedules, the target information of a schedule in a chained schedule can be determined based on the information of other schedules in the chained schedule, thereby helping users to perform tasks more consistently and improving the efficiency of task execution.

[0178] For example, suppose there's a chained schedule for a trip to a concert. This chained schedule may contain two schedules, for example, Schedule 1 and Schedule 2. Schedule 1 may be for booking a hotel, and Schedule 2 may be for booking concert tickets. It's understandable that, to facilitate their itinerary, they typically choose a hotel address near the concert venue. Therefore, the address information in Schedule 1 can be determined by the address information in Schedule 2, thereby improving the user's efficiency in executing the task. However, in the prior art, even if a user generates two schedules, one for booking a hotel and the other for booking concert tickets, there's no recommendation service for the hotel booking schedule, nor is there a hotel recommendation service that takes the concert venue's address information into account. This indicates that the tasks in the prior art lack relevance and coherence, significantly reducing the user's efficiency in executing the task.

[0179] In some optional embodiments, the target application in the recommendation service can be determined based on the user's habitual preferences, that is, the target application in the recommendation service can be the user's most frequently used application or favorite application. The user's habitual preferences can be obtained from the user's personal knowledge base.

[0180] The above text has exemplarily described the generation of a schedule with reference to Figures 3, 4A, 4B, 5, 6A, 6B, 7 and 8. Next, the following text will exemplarily describe the reminder of a schedule with reference to Figures 9 to 11.

[0181] FIG9 is a flow chart of an embodiment of the schedule reminder method provided by the present application. After step 306, the following steps may also be included:

[0182] Step 901: In response to the expiration of a reminder time in a first schedule, a first device obtains a recommended service.

[0183] Specifically, each schedule may correspond to a target task, and each target task may include a reminder time, which may be a time to remind the user to perform the target task.

[0184] When a first schedule expires, the first device may obtain a recommendation service for a target task corresponding to the expired first schedule. The target task in the first schedule may be a task that needs to be completed using a target application, and the target application is an application that executes the target task corresponding to the expired first schedule. Therefore, the recommendation service may include a recommended target application.

[0185] For example, taking the first schedule as a ticket purchasing schedule, the target task corresponding to the ticket purchasing schedule is the ticket purchasing task. Therefore, when the ticket purchasing schedule expires, the first device can obtain the corresponding recommended service. For example, the recommended service can be a ticket purchasing application, so that the user can complete the ticket purchasing task through the ticket purchasing application.

[0186] In some optional embodiments, the target application can be determined based on the user's common habits, or the target application can be determined based on the application frequently used by the user, or the target application can be determined based on the type of the current target task. The embodiments of the present application do not specifically limit this.

[0187] It is understandable that the reminder time can be indicated by the content in the time information field in the target task.

[0188] For example, taking the goal task of watching a movie as an example, assuming that the content of the time information field contained in the goal task of watching a movie is 18:00 on January 1, 2000, the reminder time can be 18:00 on January 1, 2000.

[0189] In some optional embodiments, the recommendation service may further include target information, which is task information required to be entered on the target page to complete the target task corresponding to the first schedule due.

[0190] In some optional embodiments, the target information may be obtained from the first due schedule.

[0191] It is understandable that the first schedule itself contains task-related information. By querying the task information in the first schedule, the target information required to execute the target task can be obtained.

[0192] In some optional embodiments, the task-related information included in the first schedule itself may not include target information. In this case, the target information can be obtained from the user information of the first user.

[0193] Step 902: The first device determines whether there is any missing information in the recommended service of the expired first schedule.

[0194] Specifically, after obtaining the recommended service for the expired first schedule, the first device may further determine whether the recommended service for the expired first schedule has any missing information. The missing information in this step refers to whether the recommended service has any missing target information required to execute the target task in the schedule.

[0195] For example, taking the purchase of movie tickets as an example, the target task of purchasing movie tickets may include a time information field and an event information field, wherein the content indicated by the time information field may include a reminder time, that is, reminding the user when to buy movie tickets, and the content indicated by the event information field is used to remind the user what to do. For example, in an embodiment of the present application, it is to remind the user to buy movie tickets. Since the task in this embodiment is to buy movie tickets, the application in the recommendation service can be a ticket purchase application. However, in order to purchase tickets smoothly, information such as how many tickets to buy, which cinema to go to, and what movie to watch is required. This information is not included in the information field of the target task. Therefore, the information required to execute the target task of purchasing tickets in the recommendation service is missing, and the target information required to execute the target task of purchasing tickets can also be supplemented.

[0196] If the first device determines that the target information of the recommended service of the expired first schedule is missing, step 903 may be executed. Alternatively,

[0197] If the first device determines that there is no missing information in the target information of the recommended service of the expired first schedule, step 904 may be executed.

[0198] Step 903: The first device completes the target information of the recommended service of the expired first schedule.

[0199] Specifically, the first device may complete the target information of the recommended service of the expired first schedule in the following two ways.

[0200] In method 1, the first device completes information based on information in other schedules in the chain schedule.

[0201] Because multiple schedules in a chain are coherent and relevant, if information is missing from the recommended service for any expired schedule, the first device can obtain information from schedules other than the expired schedule and use the information from the other schedules to complete the recommended service information for the expired schedule. Therefore, if the first schedule is one of the chained schedules, the first device can complete the target information for the recommended service for the expired first schedule based on the information from schedules other than the expired first schedule in the chained schedule.

[0202] Mode 2: The first device completes the information based on the information in the user's personal knowledge base.

[0203] Because the user's personal knowledge base contains personal information such as user habits and preferences, as well as user relationship information such as social relationships, knowledge reasoning and other methods can be used to supplement the target information of the recommended service in the first scheduled event. For example, using the example of purchasing movie tickets, the user's personal knowledge base can be used to infer the theaters the user frequently visits, thereby supplementing the theater information.

[0204] It is understandable that the above two methods can be used alone or in combination according to actual needs, and the embodiments of the present application do not impose any special limitations on this.

[0205] Step 904: The first device displays a reminder interface, where the reminder interface includes information indicating a recommended service.

[0206] Specifically, the reminder interface can be in the form of a card, notification, or other forms, and the embodiments of the present application do not specifically limit this.

[0207] The reminder interface may include information for indicating the recommended service of the first schedule that has expired. For example, the information of the recommended service may include a target application and target information, thereby allowing the user to click on the target application indicated by the recommended service and jump to the target page, and automatically enter the above-mentioned target information on the target page, so that the user can complete the target task corresponding to the first schedule that has expired through one-click operation on the target page.

[0208] Now, let's take a card-style reminder as an example, and illustrate it with reference to Figure 10. Referring to Figure 10, card 1000 may include a first area 1010, a second area 1020, and a third area 1030, wherein the first area 1010 contains information related to the user's schedule, the second area 1020 contains the target application, and the third area 1030 may be a jump control, which can be used to jump to the target page in the target application corresponding to the second area 1020. Taking the ticket purchase task as an example, the first area 1010 may contain information related to the ticket purchase schedule, the second area 1020 may indicate the name of the ticket purchase application, and the jump control in the third area 1030 may be used to jump to the target page in the ticket purchase application. It is understandable that the target page may be a page that automatically enters task information, that is, the target page may not be the homepage.

[0209] In some optional embodiments, target information (for example, how many tickets to buy, which cinema to go to, what movie to watch, etc.) can be indicated in the first area 1010. For example, the first area 1010 already contains the above target information. Therefore, when the user clicks the jump control, it can jump directly to the ticket purchase page 1100 as shown in Figure 11. The target information indicated by the first area 1010 can be automatically entered into the ticket purchase page 1100. The user can directly purchase the ticket after selecting a seat, thereby realizing one-click ticket purchase without entering the homepage, entering the ticket purchase information from the homepage, and then entering the relevant ticket purchase page to purchase.

[0210] In some optional embodiments, the first area 1010 may contain some target information, or the first area 1010 may not contain target information. In this case, the target information can be carried by the jump control. For example, when the user clicks the jump control, the user can jump directly to the ticket purchase page 1100 as shown in Figure 11. The target information carried by the jump control can be automatically entered in the ticket purchase page 1100. The user can directly purchase the ticket after selecting a seat, thereby realizing one-click ticket purchase without entering the homepage, entering the ticket purchase information from the homepage, and then entering the relevant ticket purchase page to make the purchase.

[0211] It can be seen that compared with the schedule reminders in the prior art that do not include recommendations for the next step, the embodiment of the present application, while providing schedule reminders, gives suggestions for the next plan, provides guiding suggestions and related service recommendations, and directly enters the target page to complete the task by obtaining the target information required to perform the task, which greatly improves the efficiency of task execution, facilitates user operations, and improves the user experience.

[0212] The following is an illustrative example of the schedule generation and schedule reminder provided by the embodiments of the present application through specific examples.

[0213] Suppose there are three users: User 1, User 2, and User 3. User 1 uses electronic device 1, User 2 uses electronic device 2, and User 3 uses electronic device 3. User 1 is in location A, while User 2 and User 3 are in location B. These three users are chatting in a group chat, discussing a concert in location A, with User 1 treating User 2 and User 3 to dinner.

[0214] User 1 can copy the content in the chat box on electronic device 1. Once electronic device 1 recognizes that the content in the chat box is intended to generate a schedule, it can further break down the content into tasks and generate a corresponding chain schedule 1 based on user 1's perspective. Information missing from chain schedule 1 can be supplemented, and each schedule in chain schedule 1 has a corresponding recommended service. Following the chained sequence of events, chain schedule 1 may include three schedules: concert ticket purchase, concert viewing, and dinner party. All schedules in chain schedule 1 can then be displayed on electronic device 1's calendar. When the date indicated in the concert ticket purchase schedule expires, electronic device 1 can remind user 1 with a card. The card may include a recommended ticket purchase app and purchase information. The user can then purchase the tickets through the ticket purchase app's entry in the card, completing the ticket purchase task. When the date indicated in the concert schedule expires, the electronic device 1 can remind the user 1 through a card, wherein the card can include a recommended taxi app and taxi information, and the user can hail a taxi through the entrance of the taxi app in the card to complete the task of going to the destination to watch the concert. When the date indicated in the dinner schedule expires, the electronic device 1 can remind the user 1 through a card, wherein the card can include a recommended taxi app and taxi information, and the user can hail a taxi through the entrance of the taxi app in the movie to complete the task of going to the destination to watch the dinner. It is understandable that when executing the relevant task through the recommended application entrance in the card, there is no need to enter the homepage of the application, but the user can directly enter the relevant page of the application to complete the relevant task.

[0215] Table 1 exemplarily shows each schedule in the chain schedule 1.

[0216] Table 1

[0217] User 2 can copy the content in the chat box on electronic device 2. When electronic device 2 recognizes that the content in the chat box is intended to generate a schedule, it can further break down the content into tasks and generate a corresponding chained schedule 2 based on user 2's perspective. Information can be supplemented for schedules with missing information in chained schedule 2, and each schedule in chained schedule 2 has a corresponding recommended service. In the chained order of events, chained schedule 2 can include five schedules: concert ticket purchase, train ticket purchase, hotel reservation, concert, and dinner. User 2's schedules for concert ticket purchase, concert, and dinner are the same as user 1's schedules for concert ticket purchase, concert, and dinner. All schedules in chained schedule 2 can then be displayed on electronic device 2's calendar. When the dates indicated in the concert ticket purchase schedule, the concert ticket purchase schedule, and the dinner schedule expire, user 2 can be reminded. The specific method for reminding user 2 can be referenced to the method for reminding user 1 in the above embodiment and will not be further described here. When the date indicated in the train ticket purchase schedule expires, the electronic device 2 can remind the user 2 by means of a card, wherein the card can include a recommended ticket purchase application and purchase information, and the user can purchase the ticket through the entry of the ticket purchase application in the card, thereby completing the train ticket purchase task. When the date indicated in the hotel reservation schedule expires, the electronic device 2 can remind the user 2 by means of a card, wherein the card can include a recommended travel application and travel information, and the user can make the hotel reservation through the entry of the travel application in the card, thereby completing the hotel reservation task.

[0218] Table 2 exemplarily shows each schedule in the chain schedule 2.

[0219] Table 2

[0220] For user 3, they can copy the content in the chat box on electronic device 3. When electronic device 3 recognizes that the content in the chat box has the intention of generating a schedule, electronic device 3 can further decompose the content in the chat box into tasks and generate a corresponding chain schedule 3 based on user 3's perspective. Information can be supplemented for schedules with missing information in chain schedule 3, and each schedule in chain schedule 3 has a corresponding recommended service. According to the chain sequence of events, the schedules in chain schedule 3 are the same as those in chain schedule 2. The specific reminder methods for each schedule in chain schedule 3 can be referred to the reminder methods for schedules in chain schedule 2, and will not be repeated here.

[0221] FIG12 is a flow chart of another embodiment of the schedule reminder method provided by the present application. In the embodiment shown in FIG12 , multiple users can share the same target task, and corresponding reminders can be issued based on the itineraries or movement trajectories of different users. Specifically, the following steps are included:

[0222] Step 1201: The first device obtains a first target schedule.

[0223] Specifically, the first target schedule may be a schedule generated according to the method in the above embodiment, or the first target schedule may be a schedule generated according to the prior art, which is not particularly limited in the embodiment of the present application.

[0224] In some optional embodiments, the first target schedule may be generated by the first device, and multiple users may generate their own corresponding schedules through their respective electronic devices. These multiple different schedules may share the same target task.

[0225] For example, take three users as an example, the three users may be user 1, user 2, and user 3, wherein user 1 uses electronic device 1, user 2 uses electronic device 2, and user 3 uses electronic device 3. Electronic device 1 can generate schedule 1 based on input text, electronic device 2 can generate schedule 2 based on input text, and electronic device 3 can generate schedule 3 based on input text.

[0226] It can be understood that the first device can be any one of the electronic device 1 , the electronic device 2 and the electronic device 3 .

[0227] It should be noted that electronic device 1, electronic device 2, and electronic device 3 can be based on the same input text. Therefore, schedule 1, schedule 2, and schedule 3 may correspond to the same target task and target location. For example, the target task may be a pickup task, or other tasks. This embodiment of the present application does not specifically limit this. Taking the target task as a pickup task as an example, the target location may be a pickup address. The target tasks of user 1, user 2, and user 3 may all be to go to the same location to pick up the item. In some embodiments, the target location may also be other types of addresses. This embodiment of the present application does not specifically limit this.

[0228] In some optional embodiments, after the second device generates a schedule, it can share the target task corresponding to the schedule with other devices. After receiving the target task shared by the second device, the first device can use the shared target task as the target task of the first target schedule. The second device can be any electronic device among the multiple electronic devices except the first device.

[0229] For example, still taking the above three users as an example, if the first device is electronic device 1, the second device can be any one of electronic device 2 or electronic device 3; or, if the first device is electronic device 2, the second device can be any one of electronic device 1 or electronic device 3; if the first device is electronic device 3, the second device can be any one of electronic device 1 or electronic device 2.

[0230] It is understood that the second user can be a user using a second device. When the second user shares the target task among multiple users, they can share it not only with the first user but also with other users. For example, still using the three users mentioned above as an example, assuming the first user is User 1 and the second user is User 2, User 2 can share the target task with User 1 and User 3.

[0231] Step 1202: The first device obtains the current location of the first user in real time.

[0232] Specifically, the first user may be a user using the first device.

[0233] Although schedule 1, schedule 2 and schedule 3 may correspond to the same target task and target location, schedule 1, schedule 2 and schedule 3 correspond to different electronic devices, that is, schedule 1, schedule 2 and schedule 3 are aimed at different users. Therefore, the reminder times corresponding to schedule 1, schedule 2 and schedule 3 may be different.

[0234] The first device can obtain the current location of the first user in real time to obtain the reminder time corresponding to the first user.

[0235] The reminder time corresponding to the first user may be determined according to the distance between the current location of the first user and the target location in the schedule.

[0236] For example, still taking user 1, user 2, and user 3 as an example, the reminder time corresponding to user 1's schedule 1 may be t1, the reminder time corresponding to user 2's schedule 2 may be t2, and the reminder time corresponding to user 3's schedule 3 may be t3. Among them, t1 may be determined by the distance between user 1's current location and the target location in schedule 1, t2 may be determined by the distance between user 2's current location and the target location in schedule 2, and t3 may be determined by the distance between user 3's current location and the target location in schedule 3.

[0237] Step 1203: In response to the distance between the current location of the first user and the target location indicated by the first target schedule being less than or equal to a preset threshold, the first device sends a reminder message.

[0238] Specifically, as the first user moves, the first user's current location will continuously change. That is, the distance between the first user's current location and the target location indicated by the first target schedule will also continuously change. Therefore, the first device can obtain the first user's current location in real time, determine whether the distance between the first user's current location and the target location indicated by the first target schedule is less than or equal to a preset threshold, and determine whether to send a reminder message based on the determination result.

[0239] Still taking user 1, user 2, and user 3 as an example, the first user can be any one of the above-mentioned users 1, user 2, and user 3. That is, from the perspective of different users, the user is the first user. For example, from the perspective of user 1, user 1 is the first user; or, from the perspective of user 2, user 2 is the first user, and from the perspective of user 3, user 3 is the first user. Electronic device 1 can obtain the current location of user 1 and can determine whether the distance between the current location of user 1 and the target location indicated by schedule 1 is less than or equal to a preset threshold; or, electronic device 2 can obtain the current location of user 2 and can determine whether the distance between the current location of user 2 and the target location indicated by schedule 2 is less than or equal to a preset threshold; or, electronic device 3 can obtain the current location of user 3 and can determine whether the distance between the current location of user 3 and the target location indicated by schedule 3 is less than or equal to a preset threshold.

[0240] If the electronic device 1 determines that the distance between the current location of the user 1 and the target location indicated by the schedule 1 is less than or equal to a preset threshold, the electronic device 1 may send a reminder message; or,

[0241] If the electronic device 2 determines that the distance between the current location of the user 2 and the target location indicated by the schedule 2 is less than or equal to the preset threshold, the electronic device 2 may send a reminder message; or,

[0242] If the electronic device 3 determines that the distance between the current location of the user 3 and the target location indicated by the schedule 3 is less than or equal to a preset threshold, the electronic device 3 may send a reminder message.

[0243] The specific form of the reminder information sent by the first device can be referred to the relevant description in the above embodiment, and will not be repeated here.

[0244] In some optional embodiments, step 1204 may be further included after step 1203 .

[0245] Step 1204: In response to the received task completion notification, the first device sends a schedule cancellation instruction to the third device.

[0246] Specifically, after the first user completes the target task indicated by the first target schedule, the task platform may send a task completion notification to the first device.

[0247] The task completion notification is used to notify the first user that the target task indicated by the first target schedule has been completed.

[0248] For example, taking the task platform as a shopping platform, after the first user makes a purchase on the shopping platform, the shopping platform may send a pickup notification message to the first device and the third device. The pickup notification message may be the input text in step 1201. After the first user completes the pickup, the task platform may send a pickup completion notification to the first device.

[0249] The third device is a device used by a third user, and the third user and the first user form a user group that shares the target task.

[0250] For example, still taking the three users in the above embodiment as an example, target tasks can be shared among user 1, user 2, and user 3. If user 1 is the first user, electronic device 1 is the first device, user 2 and user 3 are the third users, and electronic device 2 and electronic device 3 are the third devices; or, if user 2 is the first user, electronic device 2 is the first device, user 1 and user 3 are the third users, and electronic device 1 and electronic device 3 are the third devices; or, if user 3 is the first user, electronic device 3 is the first device, user 1 and user 2 are the third users, and electronic device 1 and electronic device 2 are the third devices.

[0251] In response to the received task completion notification, the first device may mark the first target schedule as completed or delete the first target schedule, and may send a schedule cancellation instruction to the third device.

[0252] Among them, the schedule cancellation indication is used to instruct the third device to cancel the second target schedule, the second schedule is a schedule obtained by the third device, and the target task corresponding to the second target schedule is the same as the target task corresponding to the first target schedule, that is, the target task in the second target schedule is shared with the target task in the first target schedule.

[0253] In some optional embodiments, after the task platform determines that the first user has completed the target task indicated by the first target schedule, it can send a task completion notification to the first device and the third device. In this way, the first device and the third device can mark their respective corresponding target schedules as completed or delete them based on the task completion notification, thereby reducing message interaction between the first device and the third device, reducing overhead, and saving power consumption.

[0254] In some optional embodiments, step 1205 may be further included after step 1201 .

[0255] Step 1205: In response to the received task update notification, the first device sends a schedule update instruction to the third device.

[0256] Specifically, the first user can update the target task indicated by the first target schedule on the task platform.

[0257] Among them, the update of the target task indicated by the first target schedule may be a change in the execution method of the target task, or the update of the first target schedule may be a change in the target location indicated by the first target schedule, or the update of the first target schedule may be a change in other information in the first target schedule. The embodiments of the present application do not specifically limit this.

[0258] After determining that the target task indicated by the first target schedule has been updated, the task platform may send a task update notification to the first device. The task update notification is used to notify the first device that the target task indicated by the first target schedule has been updated.

[0259] In response to the received task update notification, the first device may update the first target schedule based on the task update notification, and may send a schedule update instruction to the third device.

[0260] The schedule update instruction may be used to instruct the third device to update the second target schedule.

[0261] In some optional embodiments, after determining that the target task indicated by the first target schedule has been updated, the task platform may send a task update notification to the first device and the third device. The task update notification is used to notify the first device and the third device that the target tasks indicated by the first target schedule and the second target schedule have been updated, so that the first device and the third device can update the first target schedule and the second target schedule respectively based on the task update notification.

[0262] Next, the schedule generation and schedule reminder provided by the embodiments of the present application are exemplarily described below through specific embodiments.

[0263] Suppose there are three users: User 1, User 2, and User 3. User 1 uses electronic device 1, User 2 uses electronic device 2, and User 3 uses electronic device 3. Users 1, 2, and 3 are members of the same family. These users 1, 2, and 3 can form a user group. Within this user group, target tasks can be shared when creating schedules. For example, after User 1 makes a purchase on a shopping app, Electronic device 1 can push a purchase notification to User 2 and User 3, or the shopping platform can push a purchase notification to User 2 and User 3. Then, when the package purchased by User 1 arrives at the storage locker, the delivery app can simultaneously send a pickup notification to Electronic devices 1, 2, and 3. Based on the pickup notifications, Electronic devices 1, 2, and 3 can generate corresponding schedules 1, 2, and 3, respectively. The pickup tasks and addresses for Schedules 1, 2, and 3 are identical, and the pickup reminder times for Schedules 1, 2, and 3 can be determined based on the itineraries of Users 1, 2, and 3. If user 1 approaches the pickup address first, electronic device 1 can generate a reminder to remind user 1 to pick up the item. Alternatively, if user 2 approaches the pickup address first, electronic device 2 can generate a reminder to remind user 2 to pick up the item. Alternatively, if user 3 approaches the pickup address first, electronic device 3 can generate a reminder to remind user 3 to pick up the item. In other words, the pickup reminder time is determined by the distance between the user and the pickup address; the reminder is sent to the user who approaches the pickup address first.

[0264] It is understood that when any one of User 1, User 2, and User 3 completes the pickup, the courier software can send a pickup completion notification to the calendar application of the electronic device that completed the pickup. After the electronic device that completed the pickup completes the pickup, the electronic device that completed the pickup can delete the schedule in the calendar application and send a schedule cancellation instruction to the other two electronic devices, so that the other two electronic devices can cancel the corresponding schedule.

[0265] For example, assuming user 1 completes the pickup first, the courier software can send a pickup completion notification to the calendar application on electronic device 1, notifying electronic device 1 that the pickup has been completed. In this case, schedule 1 on electronic device 1 can be marked as completed, or schedule 1 on electronic device 1 can be deleted, meaning user 1 no longer needs to process schedule 1. Subsequently, electronic device 1 can send a schedule cancellation instruction to the calendar applications on electronic devices 2 and 3, indicating that users 2 and 3 no longer need to process the schedules on electronic devices 2 and 3.

[0266] In some optional embodiments, when any one of user 1, user 2 and user 3 picks up the package, the express software can send a pickup completion notification to the calendar application in electronic device 1, electronic device 2 and electronic device 3, so that electronic device 1, electronic device 2 and electronic device 3 can delete schedule 1, schedule 2 and schedule 3 respectively according to the pickup completion notification.

[0267] In some optional embodiments, any one of user 1, user 2, and user 3 may also update the pickup information. Upon determining that the pickup information in electronic device 1 has been updated, the courier software may send a pickup information update notification to the calendar application in electronic device 1 based on the updated pickup information, allowing electronic device 1 to update schedule 1 based on the pickup information update notification. Furthermore, electronic device 1 may send a schedule update instruction to electronic devices 2 and 3, instructing them to update their respective schedules.

[0268] For example, assuming that user 1 changes the pickup method from a courier locker to home delivery, electronic device 1 can update the pickup method of the generated schedule 1 and send a schedule update instruction to electronic devices 2 and 3, respectively instructing electronic devices 2 and 3 to update the pickup methods of the generated schedules 2 and 3. Alternatively, assuming that user 1 changes the home delivery to a courier locker pickup, electronic device 1 can update the pickup method of schedule 1 and send a schedule update instruction to electronic devices 2 and 3, respectively instructing electronic devices 2 and 3 to update the pickup methods of the corresponding schedules 2 and 3.

[0269] In some optional embodiments, when it is determined that the pickup information in electronic device 1 is updated, the express software can send a pickup information update notification to the calendar applications of electronic device 1, electronic device 2 and electronic device 3 based on the updated pickup information, so that electronic device 1, electronic device 2 and electronic device 3 can update schedule 1, schedule 2 and schedule 3 respectively based on the pickup information update notification.

[0270] FIG13 is a schematic diagram of the structure of an embodiment of the schedule generation device of the present application. As shown in FIG13 , the schedule generation device 1300 is applied to the first device. The schedule generation device 1300 may include: an acquisition module 1310, a processing module 1320, and a generation module 1330; wherein,

[0271] An acquisition module 1310 is used to acquire input text;

[0272] a processing module 1320 configured to process the input text based on user information of a first user to obtain a target task set, wherein the first user is a user using the first device, and the target task set includes one or more target tasks corresponding to the first user;

[0273] The generating module 1330 is configured to generate a corresponding schedule based on the target task set.

[0274] In one possible implementation, the processing module 1320 is specifically configured to decompose the input text to obtain an initial task set, wherein the initial task set includes one or more initial tasks;

[0275] The initial task set is supplemented and / or filtered based on the user information of the first user to obtain a target task set.

[0276] In one possible implementation, the processing module 1320 is specifically used to complete the information of the initial tasks with missing information in the initial task set based on the information queried in the user information of the first user and / or the information inferred based on the user information of the first user.

[0277] In one possible implementation, the processing module 1320 is specifically configured to filter out completed tasks and / or tasks irrelevant to the first user from the initial task set.

[0278] In one possible implementation, the target task set includes multiple target tasks, and the schedule generated based on the target task set is a chain schedule, wherein the multiple schedules in the chain schedule are generated by the multiple target tasks in the target task set, the multiple schedules in the chain schedule are arranged in a chronological order of their execution times, and the multiple schedules in the chain schedule have schedule associations.

[0279] In one possible implementation, the schedule generating device 1300 further includes:

[0280] A judgment module, configured to judge whether the input text contains an intention to generate a schedule;

[0281] If the input text contains an intention to generate a schedule, the input text is processed based on the user information of the first user.

[0282] In one possible implementation manner, the user information of the first user includes personal information of the first user and / or social relationship information of the first user.

[0283] In one possible implementation, the personal information of the first user includes at least the address location information of the first user, and / or the historical behavior information of the first user, and / or the historical schedule information of the first user.

[0284] In one possible implementation, the schedule generating device 1300 further includes:

[0285] a display module configured to display a reminder interface in response to the expiration of a reminder time of a first schedule; wherein the reminder interface is configured to remind a user to perform a target task corresponding to the expired schedule, the reminder interface including information indicating a recommended service for the expired first schedule, the recommended service information for the expired first schedule including a target application, the target application being an application for performing the target task corresponding to the expired first schedule;

[0286] The jump module is configured to jump to a target page in response to a user operation of opening the target application on the reminder interface, wherein the target page is a page displayed when the user completes the target task corresponding to the due first schedule.

[0287] In one possible implementation, the processing module 1320 is further used to automatically input target information corresponding to the recommended service of the expired first schedule on the target page, wherein the target information is task information required to be input on the target page to complete the target task corresponding to the expired first schedule.

[0288] In one possible implementation, the processing module 1320 is further configured to determine whether there is any missing information in the target information corresponding to the recommended service of the expired first schedule;

[0289] If it is determined that the target information corresponding to the recommended service of the expired first schedule is missing information, the target information corresponding to the recommended service of the expired first schedule is supplemented.

[0290] In one possible implementation, the processing module 1320 is specifically configured to, if the expired first schedule is a schedule in a chain schedule, complete the target information corresponding to the recommended service of the expired first schedule based on information of other schedules in the chain schedule except the expired first schedule;

[0291] The multiple schedules in the chain schedule are generated by multiple target tasks, the multiple schedules in the chain schedule are arranged in the order of their execution times, and there is a schedule correlation between the multiple schedules in the chain schedule.

[0292] In one possible implementation, the schedule generating device 1300 further includes:

[0293] A reminder module, configured to obtain a first target schedule;

[0294] In response to the distance between the current location of the first user and the target location indicated by the first target schedule being less than or equal to a preset threshold, the first device sends a reminder message, wherein the reminder message is used to remind the user to complete the task corresponding to the first target schedule.

[0295] In one possible implementation, the schedule generating device 1300 further includes:

[0296] a sending module, configured to send a schedule cancellation instruction to a third device in response to the received task completion notification;

[0297] The task indicated by the first target schedule is the same as the task indicated by the second target schedule, the second target schedule is a schedule in the third device, the task completion notification is used to notify that the task indicated by the first target schedule has been completed, and the schedule cancellation indication is used to instruct the third device to cancel the second target schedule.

[0298] The schedule generating device 1300 provided in the embodiment shown in FIG13 can be used to implement the technical solution of the method embodiment shown in this application. Its implementation principle and technical effects can be further referred to the relevant description in the method embodiment.

[0299] FIG14 is a schematic diagram of the structure of another embodiment of the schedule generating device of the present application. As shown in FIG14 , the schedule generating device 1400 may include: an acquisition module 1410, a processing module 1420, and a generation module 1430; wherein,

[0300] An acquisition module 1410 is used to acquire input text;

[0301] A processing module 1420 is configured to process the input text to obtain a target task set, wherein the target task set includes a plurality of target tasks;

[0302] The generating module 1430 is configured to generate a chain schedule based on the target task set, wherein the multiple schedules in the chain schedule are arranged in the order of their execution times and have schedule associations.

[0303] The schedule generating device 1400 provided in the embodiment shown in FIG14 can be used to implement the technical solution of the method embodiment shown in this application. Its implementation principle and technical effects can be further referred to the relevant description in the method embodiment.

[0304] It should be understood that the division of the various modules of schedule generation device 1300 shown in FIG13 and schedule generation device 1400 shown in FIG14 is merely a division of logical functions. In actual implementation, they may be fully or partially integrated into a single physical entity or physically separated. Furthermore, these modules may be implemented entirely in the form of software invoked through a processing element, or entirely in the form of hardware. Alternatively, some modules may be implemented in the form of software invoked through a processing element, while others may be implemented in the form of hardware. For example, the detection module may be a separate processing element, or it may be integrated into a chip of an electronic device. The implementation of other modules is similar. Furthermore, these modules may be fully or partially integrated together, or implemented independently. During implementation, each step of the above method or each of the above modules may be completed by hardware integrated logic circuits in a processor element or by software instructions.

[0305] For example, the above modules may be one or more integrated circuits configured to implement the above methods, such as one or more application-specific integrated circuits (ASICs), one or more microprocessors (DSPs), or one or more field programmable gate arrays (FPGAs). For another example, these modules may be integrated together to implement a system-on-a-chip (SOC).

[0306] In the above embodiments, the processor involved may include, for example, a CPU, a DSP, a microcontroller, or a digital signal processor, and may also include a GPU, an embedded neural network processor (Neural-network Process Units; hereinafter referred to as: NPU) and an image signal processor (hereinafter referred to as: ISP). The processor may also include necessary hardware accelerators or logic processing hardware circuits, such as ASICs, or one or more integrated circuits for controlling the execution of the program of the technical solution of this application. In addition, the processor may have the function of operating one or more software programs, and the software programs may be stored in a storage medium.

[0307] An embodiment of the present application also provides a readable storage medium, which stores a program. When the program is run on an electronic device, the electronic device executes the method provided by the embodiment shown in the present application.

[0308] An embodiment of the present application also provides a program product, which includes a program. When the program product is run on an electronic device, the electronic device executes the method provided by the embodiment shown in the present application.

[0309] In the embodiments of the present application, "at least one" refers to one or more, and "more" refers to two or more. "And / or" describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can represent the existence of A alone, the existence of A and B at the same time, and the existence of B alone. Among them, A and B can be singular or plural. The character " / " generally indicates that the previous and next associated objects are in an "or" relationship. "At least one of the following" and similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b and c can represent: a, b, c, a and b, a and c, b and c or a and b and c, where a, b, c can be single or multiple.

[0310] Those skilled in the art will appreciate that the various units and algorithm steps described in the embodiments disclosed herein can be implemented using a combination of electronic hardware, computer software, and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professionals and technicians can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0311] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0312] In the several embodiments provided in this application, if any function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a readable storage medium. Based on this understanding, the technical solution of this application, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for enabling a device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the method described in each embodiment of this application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (Read-Only Memory; hereinafter referred to as: ROM), random access memory (Random Access Memory; hereinafter referred to as: RAM), magnetic disk or optical disk, and other media that can store program codes.

[0313] The above description is merely a specific embodiment of the present application. Any person skilled in the art may easily conceive of variations or substitutions within the technical scope disclosed in this application, and such variations or substitutions shall be within the scope of protection of this application. The scope of protection of this application shall be subject to the scope of protection of the claims.

Claims

1. A schedule generation method, characterized in that: Applied to a first device, the method includes: Get input text; Processing the input text based on user information of a first user to obtain a target task set, wherein the first user is a user using the first device, and the target task set includes one or more target tasks corresponding to the first user; A corresponding schedule is generated based on the target task set.

2. The method according to claim 1, characterized in that The processing of the input text based on the user information of the first user to obtain the target task set includes: Decomposing the input text to obtain an initial task set, wherein the initial task set includes one or more initial tasks; The initial task set is supplemented and / or screened based on the user information of the first user to obtain a target task set.

3. The method according to claim 2, characterized in that The completing and / or filtering the initial task set based on the user information of the first user includes: The initial tasks with missing information in the initial task set are supplemented based on the information queried in the user information of the first user and / or the information inferred based on the user information of the first user.

4. The method according to claim 2, characterized in that: The completing and / or filtering the initial task set based on the user information of the first user includes: Completed tasks and / or tasks irrelevant to the first user are filtered out from the initial task set.

5. The method according to any one of claims 1 to 4, characterized in that: The target task set includes multiple target tasks, and the schedule generated based on the target task set is a chain schedule, wherein the multiple schedules in the chain schedule are generated by the multiple target tasks in the target task set, the multiple schedules in the chain schedule are arranged in the order of the execution time of the schedules, and the multiple schedules in the chain schedule have schedule association.

6. The method according to any one of claims 1 to 5, characterized in that: Before processing the input text based on the user information of the first user, the method further includes: Determining whether the input text contains an intention to generate a schedule; If the input text contains an intention to generate a schedule, the input text is processed based on the user information of the first user.

7. The method according to any one of claims 1 to 6, characterized in that: The user information of the first user includes personal information of the first user and / or social relationship information of the first user.

8. The method according to claim 7, characterized in that The personal information of the first user includes at least the address location information of the first user, and / or the historical behavior information of the first user, and / or the historical schedule information of the first user.

9. The method according to any one of claims 1 to 8, characterized in that: After generating a corresponding schedule based on the target task set, the method further includes: In response to the reminder time of the first schedule expiring, displaying a reminder interface; wherein the reminder interface is used to remind the user to perform the target task corresponding to the expired schedule, the reminder interface includes information for indicating the recommended service of the expired first schedule, the recommended service information of the expired first schedule includes a target application, and the target application is an application for performing the target task corresponding to the expired first schedule; In response to the user's operation of opening the target application on the reminder interface, jumping to the target page, wherein the target page is a page displayed when the user completes the target task corresponding to the due first schedule.

10. The method according to claim 9, characterized in that After jumping to the target page, the method further includes: The target information corresponding to the recommended service of the first due schedule is automatically input on the target page, wherein the target information is task information required to be input on the target page to complete the target task corresponding to the first due schedule.

11. The method according to claim 9, characterized in that Before automatically inputting the target information corresponding to the recommended service of the expired first schedule on the target page, the method further includes: Determining whether there is any missing information in the target information corresponding to the recommended service of the first schedule that is due; If it is determined that the target information corresponding to the recommended service of the first schedule that has expired has missing information, the target information corresponding to the recommended service of the first schedule that has expired is supplemented.

12. The method according to claim 11, characterized in that The completing the target information corresponding to the recommended service of the expired first schedule includes: If the expired first schedule is a schedule in a chain schedule, completing the target information corresponding to the recommended service of the expired first schedule based on information of other schedules in the chain schedule except the expired first schedule; The multiple schedules in the chain schedule are generated by multiple target tasks, the multiple schedules in the chain schedule are arranged in the order of execution time of the schedules, and the multiple schedules in the chain schedule are associated with each other.

13. The method according to any one of claims 1 to 8, characterized in that: After generating a corresponding schedule based on the target task set, the method further includes: Get the first target schedule; In response to the distance between the current location of the first user and the target location indicated by the first target schedule being less than or equal to a preset threshold, the first device sends a reminder message, wherein the reminder message is used to remind the user to complete the task corresponding to the first target schedule.

14. The method according to claim 13, characterized in that After the first device sends the reminder information, the method further includes: In response to the received task completion notification, sending a schedule cancellation instruction to the third device; Among them, the task indicated by the first target schedule is the same as the task indicated by the second target schedule, the second target schedule is a schedule in the third device, the task completion notification is used to notify that the task indicated by the first target schedule has been completed, and the schedule cancellation indication is used to instruct the third device to cancel the second target schedule.

15. A schedule generation method, characterized in that: The method comprises: Get input text; Processing the input text to obtain a target task set, wherein the target task set includes a plurality of target tasks; A chain schedule is generated based on the target task set, wherein the multiple schedules in the chain schedule are arranged in a chronological order of their execution times, and the multiple schedules in the chain schedule are associated with each other.

16. An electronic device, characterized in that: include: A processor and a memory, wherein the memory is used to store a program; the processor is used to run the program to implement the schedule generation method according to any one of claims 1 to 14; or, to implement the schedule generation method according to claim 15.

17. A readable storage medium, characterized in that: The readable storage medium stores a program, and when the program is executed on an electronic device, the schedule generation method according to any one of claims 1 to 16 is implemented.

Images