Task management method and apparatus, device, and storage medium

Abstract

Embodiments of the present disclosure relate to a task management method and apparatus, a device and a storage medium. The provided method comprises: on the basis of a first interaction between a target user and a virtual object, obtaining a first request of the target user about creating a target task of periodically obtaining the content; on the basis of the first request, creating a delay task associated with timing information indicated by the first request, wherein the delay task is used for triggering the generation process of the content; and in response to the completion of the creation of the delay task, creating a periodic task associated with the timing information, wherein the periodic task is used for triggering to periodically provide the generated content to the target user on the basis of the timing information. In this way, the embodiments of the present disclosure can improve the content pushing efficiency.

Description

A task management method, apparatus, device, and storage medium Technical Field

[0001] The exemplary embodiments disclosed herein generally relate to the field of computers, and particularly to a task management method, apparatus, device, and computer-readable storage medium. Background Technology

[0002] In recent years, with the development of the internet, more and more users are engaging in online activities on application platforms. For example, users may interact with virtual objects on these platforms. However, existing interaction scenarios with virtual objects cannot meet users' needs for scheduled content delivery.

[0003] Summary of the Invention

[0004] In a first aspect of this disclosure, a task management method is provided. The method includes: obtaining a first request from the target user regarding the creation of a target task for periodically acquiring content, based on a first interaction between the target user and a virtual object; creating a delayed task associated with timing information indicated by the first request, the delayed task being used to trigger a content generation process; and, in response to the completion of the delayed task creation, creating a periodic task associated with the timing information, the periodic task being used to trigger the periodic delivery of the generated content to the target user according to the timing information.

[0005] In a second aspect of this disclosure, an apparatus for task management is provided. The apparatus includes: an acquisition module configured to acquire a first request from a target user regarding the creation of a target task for periodically acquiring content, based on a first interaction between a target user and a virtual object; a first creation module configured to create a delayed task associated with timing information indicated by the first request, the delayed task being used to trigger a content generation process; and a second creation module configured to create a periodic task associated with the timing information in response to the completion of the delayed task creation, the periodic task being used to trigger the periodic delivery of generated content to the target user according to the timing information.

[0006] In a third aspect of this disclosure, an electronic device is provided. The device includes at least one processing unit; and at least one memory coupled to the at least one processing unit and storing instructions for execution by the at least one processing unit. When executed by the at least one processing unit, the instructions cause the device to perform the method of the first aspect.

[0007] In a fourth aspect of this disclosure, a computer-readable storage medium is provided. The computer-readable storage medium stores a computer program that can be executed by a processor to implement the method of the first aspect.

[0008] It should be understood that the content described in this content section is not intended to limit the key or essential features of the embodiments of this disclosure, nor is it intended to restrict the scope of this disclosure. Other features of this disclosure will become readily apparent from the following description. Attached Figure Description

[0009] The above and other features, advantages, and aspects of the embodiments of this disclosure will become more apparent from the accompanying drawings and the following detailed description. In the drawings, the same or similar reference numerals denote the same or similar elements, wherein:

[0010] Figure 1 shows a schematic diagram of an example environment capable of real-time implementation of some embodiments of this disclosure;

[0011] Figures 2A-2G illustrate flowcharts of detailed example processes for task management according to some embodiments of the present disclosure;

[0012] Figure 3 illustrates a flowchart of an example process for task management according to some embodiments of the present disclosure;

[0013] Figure 4 shows a schematic structural block diagram of an example device for task management according to some embodiments of the present disclosure; and

[0014] Figure 5 shows a block diagram of an electronic device capable of implementing several embodiments of the present disclosure. Detailed Implementation

[0015] Embodiments of this disclosure will now be described in more detail with reference to the accompanying drawings. While some embodiments of this disclosure are shown in the drawings, it should be understood that this disclosure can be implemented in various forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided to provide a more thorough and complete understanding of this disclosure. It should be understood that the accompanying drawings and embodiments of this disclosure are for illustrative purposes only and are not intended to limit the scope of protection of this disclosure.

[0016] It should be noted that the headings of any section / subsection provided herein are not limiting. Various embodiments are described throughout this document, and embodiments of any type may be included under any section / subsection. Furthermore, embodiments described in any section / subsection may be combined in any way with any other embodiments described in the same section / subsection and / or different sections / subsections.

[0017] In the description of embodiments of this disclosure, the term "comprising" and similar terms should be understood as open-ended inclusion, i.e., "including but not limited to". The term "based on" should be understood as "at least partially based on". The term "one embodiment" or "the embodiment" should be understood as "at least one embodiment". The term "some embodiments" should be understood as "at least some embodiments". Other explicit and implicit definitions may also be included below. The terms "first", "second", etc., may refer to different or the same objects. Other explicit and implicit definitions may also be included below.

[0018] The embodiments of this disclosure may involve user data, data acquisition, and / or use. All of these aspects comply with applicable laws, regulations, and relevant provisions. In the embodiments of this disclosure, all data collection, acquisition, processing, manipulation, forwarding, and use are conducted with the user's knowledge and confirmation. Accordingly, in implementing the embodiments of this disclosure, the type, scope of use, and usage scenarios of any data or information that may be involved should be communicated to the user and their authorization obtained in accordance with relevant laws and regulations through appropriate means. The specific methods of notification and / or authorization may vary depending on the actual situation and application scenario, and the scope of this disclosure is not limited in this respect.

[0019] In this specification and the embodiments, any processing of personal information will be carried out only under the premise of legality (such as obtaining the consent of the personal information subject, or being necessary for the performance of a contract), and will only be carried out within the scope stipulated or agreed upon. A user's refusal to process personal information other than that necessary for basic functions will not affect the user's use of basic functions.

[0020] As briefly mentioned above, with the development of the internet, more and more users are engaging in online activities on application platforms. For example, users may interact with virtual objects on these platforms. However, existing interaction scenarios with virtual objects cannot meet users' needs for scheduled content delivery.

[0021] Embodiments of this disclosure propose a scheme for task management. According to this scheme, a first request from the target user regarding the creation of a target task for periodically acquiring content can be obtained based on a first interaction between the target user and a virtual object; based on the first request, a delayed task associated with timing information indicated by the first request is created, the delayed task being used to trigger the content generation process; and in response to the completion of the delayed task creation, a periodic task associated with the timing information is created, the periodic task being used to trigger the periodic provision of the generated content to the target user according to the timing information.

[0022] In this way, embodiments of this disclosure can, during the interaction between the target user and the virtual object, create associated delayed tasks and periodic tasks based on a user's request to create periodically retrieved content, and periodically provide content to the user according to the corresponding time intervals. Thus, during the interaction between the user and the virtual object, tasks for scheduled content pushes can be conveniently and efficiently created for the user, improving content push efficiency and meeting the user's need to create scheduled push tasks.

[0023] The following section provides a detailed description of various example implementations of this scheme, with reference to the accompanying drawings.

[0024] Example Environment

[0025] Figure 1 illustrates a schematic diagram of an example environment 100 in which embodiments of the present disclosure can be implemented. As shown in Figure 1, the example environment 100 may include an electronic device 110.

[0026] In this example environment 100, electronic device 110 can run an application 120 that supports user interface interaction. Application 120 can be any suitable type of application for user interface interaction, examples of which may include, but are not limited to, news applications, virtual applications, social applications, or other suitable applications. User 140 can interact with application 120 via electronic device 110 and / or its attached devices.

[0027] In environment 100 of Figure 1, if application 120 is active, electronic device 110 can use application 120 to present interface 150 for supporting interface interaction.

[0028] In some embodiments, electronic device 110 communicates with server 130 to provide services to application 120. Electronic device 110 can be any type of mobile terminal, fixed terminal, or portable terminal, including mobile phones, desktop computers, laptop computers, notebook computers, netbook computers, tablet computers, media computers, multimedia tablets, handheld computers, portable gaming terminals, VR / AR devices, personal communication system (PCS) devices, personal navigation devices, personal digital assistants (PDAs), audio / video players, digital cameras / camcorders, positioning devices, television receivers, radio receivers, e-book devices, gaming devices, or any combination thereof, including accessories and peripherals of these devices or any combination thereof. In some embodiments, electronic device 110 can also support any type of user-facing interface (such as "wearable" circuitry).

[0029] Server 130 can be a standalone physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server providing basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, content delivery networks, and big data and artificial intelligence platforms. Server 130 may include, for example, computing systems / servers such as mainframes, edge computing nodes, computing devices in a cloud environment, etc. Server 130 can provide backend services for applications 120 that support virtual scenarios in electronic devices 110.

[0030] A communication connection can be established between server 130 and electronic device 110. This communication connection can be established via wired or wireless means. The communication connection may include, but is not limited to, Bluetooth, mobile network, Universal Serial Bus (USB), and Wireless Fidelity (WiFi) connections; the embodiments of this disclosure are not limited in this respect. In the embodiments of this disclosure, server 130 and electronic device 110 can achieve signaling interaction through the communication connection between them.

[0031] It should be understood that the structure and function of the various elements in environment 100 are described for illustrative purposes only and do not imply any limitation on the scope of this disclosure.

[0032] The following description will continue with reference to the accompanying drawings, which will provide some exemplary embodiments of this disclosure.

[0033] Content push

[0034] Figures 2A to 2G illustrate flowcharts of detailed example processes 200A to 200G for task management according to some embodiments of the present disclosure. Processes 200A to 200G will now be described with reference to Figure 1. Embodiments according to the present disclosure will be described below using the push of information content as an example. It should be understood that the solutions of the present disclosure are also applicable to other types of content push tasks.

[0035] In some embodiments, as shown in FIG2A, the business layer 202 may receive a first interaction between the target user and the virtual object. Further, based on the first interaction between the target user and the virtual object, the business layer 202 may obtain a first request from the target user regarding a target task of creating periodically retrieved content. As an example, the virtual object may be a robot assistant with dialogue capabilities and the ability to provide feedback based on information. As an example, the virtual object may be implemented based on a bot service.

[0036] In some embodiments, the content requested by the target user is information content. For example, the information content could be news content.

[0037] In some embodiments, continuing to refer to FIG2A, the business layer 202 can receive a session message sent by a target user to a virtual object. Further, the business layer 202 can process the session message based on a language model to determine whether the session message includes a first request from the target user regarding a target task of creating periodically retrieved content. As an example, the session message could be "Please push news content to me every morning at 8:00 AM." In this case, the session message is a first request for a target task of creating periodically retrieved content.

[0038] In some embodiments, continuing to refer to FIG2A, the business layer may also receive preset operations from the target user (e.g., click operations on the periodic task control, etc.) and obtain the target user's first request for creating a target task of periodically acquiring content.

[0039] In some embodiments, continuing to refer to FIG2A, the business layer 202 may create a task ID corresponding to the first request based on the received first request, in order to record the first request. Further, the business layer 202 may pass a message to the delayed task module 204 to create a delayed task associated with the timing information indicated by the first request. The delayed task can be used to trigger the content generation process. As an example, the timing information is used to indicate the preparation time for generating content associated with the first request in the delayed task. As an example, the preparation time can be a start time or a time period. For example, if the timing information is "8:00 AM every day", then the preparation time for the delayed task can be before 8:00 AM every day (e.g., starting content preparation at 7:00 AM or preparing content between 7:00 AM and 7:30 AM). The specific association between the preparation time and the timing information can be set by those skilled in the art as needed, and this disclosure does not impose any restrictions on this.

[0040] In some embodiments, the delayed task may include content requirements. Content requirements may indicate requirements for the content to be generated (e.g., content topic, content scope, etc.).

[0041] In some embodiments, continuing to refer to FIG2A, after receiving the message to create a delayed task, the delayed task module 204 can create the delayed task with the help of the scheduling module 205. Further, after the delayed task is created based on the scheduling module 205, the delayed task module 204 can store the delayed task corresponding to the first request in the worksheet 206.

[0042] In some embodiments, continuing to refer to FIG2A, the delayed task module 204, based on the storage completion of the delayed task for the first request, sends a message of successful storage back to the business layer 202.

[0043] In some embodiments, continuing to refer to FIG2A, the business layer 202 may, in response to the completion of the delayed task creation, request the periodic task module 203 to create a periodic task associated with the timing information of the first request. The periodic task can be used to trigger the periodic delivery of generated content to the target user based on the timing information. As an example, if the target user's first request is "to push news content every morning at 8:00 AM," then the periodic task is to provide the news content to the target user precisely at 8:00 AM every day. The news content is generated based on the delayed task.

[0044] In some embodiments, continuing to refer to FIG2A, the periodic task module 203 may, in response to receiving a request to create a periodic task, invoke the scheduling module 205 to create a periodic task associated with the timing information indicated by the first request.

[0045] In some embodiments, continuing to refer to FIG2A, the periodic task module 203 may, in response to the scheduling module 205 completing the creation of the periodic task, store the periodic task corresponding to the first request in the worksheet 206, and at the same time send a message to the business layer 202 that the periodic task has been successfully saved.

[0046] In some embodiments, continuing to refer to FIG2A, the business layer 202 may associate the delayed task with the periodic task in response to the completion of the creation of both the delayed task and the periodic task associated with the timing information indicated by the first request. Further, the business layer 202 may store the association between the delayed task and the periodic task in the work task table 207. Further, the work task table 207 may, in response to the completion of storing the association between the delayed task and the periodic task, send a message to the business layer 202 indicating that storage is complete.

[0047] In some embodiments, continuing to refer to FIG2A, the business layer 202 may, in response to receiving a storage completion message from the work task table 207, send a target task creation completion message to the user 201 (also known as the target user).

[0048] In some embodiments, referring to FIG2B, the business layer 202 may obtain a second request from user 201 regarding modifying the target task. Further, the business layer 202 may determine whether the delayed task associated with the target task is valid based on worksheet 206.

[0049] In some embodiments, continuing to refer to FIG2B, the business layer 202 may, in response to the validity of the delayed task, invoke the delayed task module 204 to update the delayed task based on the second request. The business layer 202 may, upon completion of the delayed task update, store the updated delayed task in worksheet 206 to replace the original delayed task associated with the first request.

[0050] In some embodiments, continuing to refer to FIG2B, the business layer 202 may, in response to the delayed task being updated, invoke the periodic task module 203 to update the periodic task based on the second request. Further, the business layer 202 may, based on the completion of the periodic task update, store the updated periodic task in worksheet 206 to replace the original periodic task associated with the first request.

[0051] In some embodiments, continuing to refer to FIG2B, the business layer 202 may, in response to an update of surrounding tasks, associate the updated delayed task with the updated periodic task. Further, the business layer 202 may store the association between the updated delayed task and the updated periodic task in the work task table 207 to replace the previous association between the delayed task and the periodic task.

[0052] In some embodiments, the aforementioned delayed task is a first delayed task. Continuing to refer to FIG2B, the business layer 202 may, in response to the failure of the first delayed task, invoke the delayed task module 204 to create a second delayed task based on a second request. Further, the business layer 202 may, in response to the completion of the creation of the second delayed task, store the second delayed task in worksheet 206.

[0053] In some embodiments, continuing to refer to FIG2B, the business layer 202 may, in response to the completion of the creation of the second delayed task, invoke the periodic task module 203 to update the periodic task associated with the first request based on the second request.

[0054] In some embodiments, continuing to refer to FIG2B, the business layer 202 may associate the second delayed task with the updated periodic task in response to the periodic task associated with the second request being updated. Further, the business layer 202 may store the association between the second delayed task and the updated periodic task in the job task table 207, replacing the association between the first delayed task and the periodic task.

[0055] In some embodiments, continuing to refer to FIG2B, the service layer 202 may send an update completion notification to the user 201 in response to the update completion of the second request.

[0056] In some embodiments, continuing to refer to FIG2B, the business layer 202 can obtain a third request from user 201 regarding the cancellation of the target task. Further, the business layer 202 can cancel the periodic task and delayed task corresponding to the target task based on the third request. Further, the business layer 202 can mark the target task as invalid based on the completion of the cancellation of the periodic task and delayed task corresponding to the target task.

[0057] In some embodiments, as shown in FIG2C, the business layer 202 may, in response to receiving a third request from the target user to cancel the target task, query the task table 207 to see if the target task exists. Further, the business layer 202 may, in response to the absence of the target task in the task table 207, inform the user 201 that the task has been deleted.

[0058] In some embodiments, continuing to refer to FIG2C, the business layer 202 may, in response to the existence of a target task in the work task table 207, mark the target task in the work task table 207 as invalid. It may also mark the periodic tasks and delayed tasks associated with the target task in the work table 206 as invalid. Furthermore, the business layer 202 may also invoke the scheduling module 205 (also known as the task scheduling module 205) to close the periodic tasks and delayed tasks associated with the target task.

[0059] In some embodiments, referring to FIG2D, the aforementioned delayed task associated with the first request is the first delayed task, and the periodic task associated with the first request is the first periodic task. The business layer 202 can obtain a fourth request from user 201 (the target user) regarding restarting the target task. Further, the business layer 202 can query whether the target task exists based on the work task table 207. Further, in response to the absence of the target task in the work task table 207, the business layer can inform user 201 that the target task does not exist.

[0060] In some embodiments, continuing to refer to FIG2D, the business layer 202 may, in response to the existence of a target task in the work task table 207 (e.g., the target task is currently in a disabled state), obtain parameter information of the first periodic task from the work table 206 (also known as the task list). As an example, as shown in FIG2D, the business layer 202 may initiate a request to the periodic task module 203 to obtain reference information of the first periodic task. The periodic task module 203 may obtain the first periodic task from the work table 206 based on the request. Further, the periodic task module 203 may return the parameter information of the first periodic task to the business layer 202 based on the obtained first periodic task.

[0061] In some embodiments, continuing to refer to FIG2D, the business layer 202 can, based on the parameter information of the first cycle task, invoke the delayed task module 204 to create a third delayed task and a second cycle task. Further, the business layer 202 can store the association between the third delayed task and the second cycle task in the work task table 207. Further, the business layer 202 can mark the target task as valid.

[0062] In some embodiments, as shown in FIG2E, the business layer 202 may, in response to receiving a request from user 201 to obtain a task list, query the work task table 207 for tasks with a valid status. Further, the business layer 202 may send the tasks with a valid status obtained from the work task table 207 to user 201. As an example, if there are no tasks with a valid status in the work task table 207, the business layer 203 may inform user 201 that no tasks exist.

[0063] In some embodiments, as shown in FIG2F, the service layer 202 may, in response to the triggering of a delayed task from the scheduling module 205, determine the status of the target task corresponding to the delayed task from the work task table 207. Further, the service layer 202 may, in response to the target task being in a valid state, trigger the delayed task to generate content. In some embodiments, the service layer may, in response to the target task being in an invalid state, stop executing the delayed task.

[0064] In some embodiments, as shown in FIG2G, the service layer 202 may determine the status of the target task corresponding to the periodic task from the work task table 207 in response to the triggering of a periodic task from the scheduling module 205. Further, the service layer 202 may trigger the periodic task to generate content in response to the target task being in a valid state. In some embodiments, the service layer may stop executing the periodic task in response to the target task being in an invalid state.

[0065] In some embodiments, the periodic task is set with a deadline, and the business layer 202 can set the status of the periodic task to invalid in response to the deadline being reached.

[0066] In some embodiments, continuing to refer to Figure 2G, the business layer 202 may also call the periodic task module to update the deadline information of the periodic task in response to the execution of the periodic task.

[0067] Based on the process described above, the embodiments of this disclosure can, during the interaction between the target user and the virtual object, create associated delayed tasks and periodic tasks based on a user's request to create periodically retrieved content, and provide content to the user periodically according to the corresponding time. Furthermore, it can also receive user requests to update, stop, or enable target tasks, and adjust the target tasks accordingly. In this way, during the interaction between the user and the virtual object, it can conveniently and efficiently create and update tasks for scheduled content delivery, improving content delivery efficiency and meeting the user's need to create scheduled delivery tasks.

[0068] Example process

[0069] Figure 3 shows a flowchart of an example process 300 for task management according to some embodiments of the present disclosure. Process 300 can be implemented at electronic device 110. Process 300 will now be described with reference to Figure 1.

[0070] As shown in the figure, in box 310, electronic device 110 can obtain the first request from the target user regarding the target task of creating periodically acquired content based on the first interaction between the target user and the virtual object.

[0071] In box 320, electronic device 110 can create a delayed task associated with timing information indicated by the first request, based on the first request. The delayed task is used to trigger the content generation process.

[0072] In box 330, electronic device 110 may, in response to the completion of delayed task creation, create a periodic task associated with timing information, which is used to trigger the periodic delivery of generated content to a target user based on the timing information.

[0073] In some embodiments, method 300 further includes: associating a delayed task with a periodic task; and storing the association between the delayed task and the periodic task.

[0074] In some embodiments, method 300 further includes: obtaining a second request from the target user regarding modifying the target task; determining whether a delayed task associated with the target task is valid; updating the delayed task based on the second request in response to the delayed task being valid; and updating a periodic task based on the second request in response to the delayed task being updated.

[0075] In some embodiments, the delayed task is a first delayed task, and method 300 further includes: in response to the failure of the first delayed task, creating a second delayed task based on a second request; in response to the creation of the second delayed task, updating a periodic task based on the second request; and storing the association between the second delayed task and the periodic task.

[0076] In some embodiments, method 300 further includes: obtaining a third request from the target user to cancel the target task; canceling the periodic task and the delayed task based on the third request; and marking the target task as invalid.

[0077] In some embodiments, canceling delayed tasks and periodic tasks includes: marking the periodic task as invalid in the task list and closing the periodic task via the task scheduling module; and marking the delayed task as invalid in the task list and closing the delayed task via the task scheduling module.

[0078] In some embodiments, the delayed task is a first delayed task, and the periodic task is a first periodic task. The method 300 further includes: obtaining a fourth request from the target user to restart the target task; obtaining parameter information of the first periodic task from the task list; creating a third delayed task and a second periodic task based on the parameter information; storing the association between the third delayed task and the second periodic task; and marking the target task as valid.

[0079] In some embodiments, method 300 further includes: in response to the delayed task being triggered, determining the state of the target task corresponding to the delayed task; and in response to the target task being in a valid state, triggering the delayed task to generate content.

[0080] In some embodiments, method 300 further includes: in response to a periodic task being triggered, determining the state of a target task corresponding to the periodic task; and in response to the target task being in a valid state, triggering the periodic task to provide content to the target user.

[0081] In some embodiments, method 300 further includes: updating the deadline information of the periodic task in response to the periodic task being executed.

[0082] Example devices and equipment

[0083] Embodiments of this disclosure also provide corresponding apparatus for implementing the methods or processes described above. Figure 4 shows a schematic structural block diagram of an example apparatus 400 for content push according to certain embodiments of this disclosure. Apparatus 400 may be implemented as or included in an electronic device. The various modules / components in apparatus 400 may be implemented by hardware, software, firmware, or any combination thereof.

[0084] As shown in Figure 4, the device 400 includes an acquisition module 410 configured to acquire a first request from the target user regarding a target task for creating periodically acquired content based on a first interaction between the target user and a virtual object; a first creation module 420 configured to create a delayed task associated with timing information indicated by the first request, the delayed task being used to trigger the content generation process; and a second creation module 430 configured to create a periodic task associated with the timing information in response to the completion of the delayed task creation, the periodic task being used to trigger the periodic provision of generated content to the target user according to the timing information.

[0085] In some embodiments, the second creation module 430 is further configured to: associate a delayed task with a periodic task; and store the association between the delayed task and the periodic task.

[0086] In some embodiments, the acquisition module 410 is further configured to: acquire a second request from the target user regarding the modification of the target task; determine whether a delayed task associated with the target task is valid; update the delayed task based on the second request in response to the delayed task being valid; and update the periodic task based on the second request in response to the delayed task being updated.

[0087] In some embodiments, the delayed task is a first delayed task, and the first creation module 420 is further configured to: in response to the failure of the first delayed task, create a second delayed task based on a second request; the second creation module 430 is further configured to: in response to the creation of the second delayed task, update the periodic task based on the second request; and store the association between the second delayed task and the periodic task.

[0088] In some embodiments, the acquisition module 410 is further configured to: acquire a third request from the target user to cancel the target task; the device 400 also includes a cancellation module, which is configured to: cancel the periodic task and the delayed task based on the third request; and mark the target task as invalid.

[0089] In some embodiments, the cancellation module is further configured to: cancel delayed tasks and periodic tasks by: marking the periodic task as invalid in the task list and closing the periodic task via the task scheduling module; and marking the delayed task as invalid in the task list and closing the delayed task via the task scheduling module.

[0090] In some embodiments, the delayed task is a first delayed task, the periodic task is a first periodic task, and the acquisition module 410 is further configured to: acquire a fourth request from the target user regarding restarting the target task; acquire parameter information of the first periodic task from the task list; the first creation module 420 and the second creation module 430 are further configured to: create a third delayed task and a second periodic task based on the parameter information; store the association between the third delayed task and the second periodic task; and mark the target task as valid.

[0091] In some embodiments, the apparatus 400 further includes a response module configured to: determine the state of a target task corresponding to the delayed task in response to the delayed task being triggered; and trigger the delayed task to generate content in response to the target task being in a valid state.

[0092] In some embodiments, the response module is further configured to: determine the state of the target task corresponding to the periodic task in response to the periodic task being triggered; and trigger the periodic task to provide content to the target user in response to the target task being in a valid state.

[0093] In some embodiments, the response module is further configured to update the deadline information of the periodic task in response to the execution of the periodic task.

[0094] Figure 5 illustrates a block diagram of an electronic device 500 in which one or more embodiments of the present disclosure may be implemented. It should be understood that the electronic device 500 shown in Figure 5 is merely exemplary and should not be construed as limiting the functionality and scope of the embodiments described herein. The electronic device 500 shown in Figure 5 can be used in electronic devices.

[0095] As shown in Figure 5, the electronic device 500 is in the form of a general-purpose electronic device. Components of the electronic device 500 may include, but are not limited to, one or more processors or processing units 510, memory 520, storage devices 530, one or more communication units 540, one or more input devices 550, and one or more output devices 560. The processing unit 510 may be a physical or virtual processor and is capable of performing various processes according to programs stored in the memory 520. In a multiprocessor system, multiple processing units execute computer-executable instructions in parallel to improve the parallel processing capability of the electronic device 500.

[0096] Electronic device 500 typically includes multiple computer storage media. Such media can be any accessible media that is accessible to electronic device 500, including but not limited to volatile and non-volatile media, removable and non-removable media. Memory 520 can be volatile memory (e.g., registers, cache, random access memory (RAM)), non-volatile memory (e.g., read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory), or some combination thereof. Storage device 530 can be removable or non-removable media and can include machine-readable media, such as flash drives, disks, or any other media that can be used to store information and / or data and can be accessed within electronic device 500.

[0097] Electronic device 500 may further include additional removable / non-removable, volatile / non-volatile storage media. Although not shown in FIG. 5, disk drives for reading from or writing to removable, non-volatile disks (e.g., "floppy disks") and optical disk drives for reading from or writing to removable, non-volatile optical disks may be provided. In these cases, each drive may be connected to a bus (not shown) via one or more data media interfaces. Memory 520 may include computer program product 525 having one or more program modules configured to perform various methods or actions of various embodiments of the present disclosure.

[0098] Communication unit 540 enables communication with other electronic devices via a communication medium. Additionally, the functionality of components of electronic device 500 can be implemented using a single computing cluster or multiple computing machines capable of communicating via communication connections. Therefore, electronic device 500 can operate in a networked environment using logical connections to one or more other servers, network personal computers (PCs), or another network node.

[0099] Input device 550 can be one or more input devices, such as a mouse, keyboard, trackball, etc. Output device 560 can be one or more output devices, such as a monitor, speaker, printer, etc. Electronic device 500 can also communicate with one or more external devices (not shown) via communication unit 540 as needed. These external devices include storage devices, display devices, etc., and can communicate with one or more devices that enable user interaction with electronic device 500, or with any device that enables electronic device 500 to communicate with one or more other electronic devices (e.g., network card, modem, etc.). Such communication can be performed via input / output (I / O) interface (not shown).

[0100] According to an exemplary implementation of this disclosure, a computer-readable storage medium is provided that stores computer-executable instructions thereon, wherein the computer-executable instructions are executed by a processor to implement the methods described above. According to an exemplary implementation of this disclosure, a computer program product is also provided, which is tangibly stored on a non-transitory computer-readable medium and includes computer-executable instructions, which are executed by a processor to implement the methods described above.

[0101] Various aspects of this disclosure are described herein with reference to flowchart illustrations and / or block diagrams of methods, apparatuses, devices, and computer program products implemented according to this disclosure. It should be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer-readable program instructions.

[0102] These computer-readable program instructions can be provided to a processing unit of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus to produce a machine such that, when executed by the processing unit of the computer or other programmable data processing apparatus, they create means for implementing the functions / actions specified in one or more blocks of the flowchart and / or block diagram. These computer-readable program instructions can also be stored in a computer-readable storage medium that causes a computer, programmable data processing apparatus, and / or other device to operate in a particular manner. Thus, the computer-readable medium storing the instructions comprises an article of manufacture that includes instructions for implementing aspects of the functions / actions specified in one or more blocks of the flowchart and / or block diagram.

[0103] Computer-readable program instructions can be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable data processing apparatus, or other device to produce a computer-implemented process, thereby causing the instructions that execute on the computer, other programmable data processing apparatus, or other device to perform the functions / actions specified in one or more boxes of a flowchart and / or block diagram.

[0104] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this disclosure. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of an instruction, which contains one or more executable instructions for implementing the specified logical function. In some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutive blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, may be implemented using a dedicated hardware-based system that performs the specified function or action, or using a combination of dedicated hardware and computer instructions.

[0105] Various implementations of this disclosure have been described above. These descriptions are exemplary and not exhaustive, nor are they limited to the disclosed implementations. Many modifications and variations will be apparent to those skilled in the art without departing from the scope and spirit of the described implementations. The terminology used herein is chosen to best explain the principles, practical applications, or improvements to technology in the market, or to enable others skilled in the art to understand the various implementations disclosed herein.

Claims

1. A task management method, comprising: obtaining a first request of a target user for creating a target task of periodically obtaining content based on a first interaction of the target user with a virtual object; creating a delay task associated with timing information indicated by the first request based on the first request, the delay task being used to trigger a generation process of the content; and in response to completion of the creation of the delay task, creating a periodic task associated with the timing information, the periodic task being used to trigger periodic provision of the generated content to the target user according to the timing information. 2.The method of claim 1, further comprising: associating the delay task to the periodic task; and storing the association between the delay task and the periodic task. 3.The method of claim 1, further comprising: obtaining a second request of the target user for modifying the target task; determining whether the delay task associated with the target task is valid; in response to the delay task being valid, updating the delay task based on the second request; in response to the delay task being updated, updating the periodic task based on the second request. 4.The method of claim 3, wherein the delay task is a first delay task, the method further comprising: in response to the first delay task being invalid, creating a second delay task based on the second request; in response to the second delay task being created, updating the periodic task based on the second request; and storing the association between the second delay task and the periodic task. 5.The method of claim 1, further comprising: obtaining a third request of the target user for canceling the target task; canceling the periodic task and the delay task based on the third request; and marking the target task as invalid. 6.The method of claim 5, wherein canceling the delay task and the periodic task comprises: marking the periodic task as invalid in a task list and closing the periodic task via a task scheduling module; and marking the delay task as invalid in the task list and closing the delay task via the task scheduling module. 7.The method of claim 6, wherein the delay task is a first delay task and the periodic task is a first periodic task, the method further comprising: obtaining a fourth request of the target user for restarting the target task; obtaining parameter information of the first periodic task from the task list; creating a third delay task and a second periodic task based on the parameter information; storing the association between the third delay task and the second periodic task; and marking the target task as valid. 8.The method of claim 1, further comprising: in response to the delay task being triggered, determining a state of the target task corresponding to the delay task; and in response to the target task being in a valid state, triggering the delay task to generate the content. 9.The method of claim 1, further comprising: ​ ​ ​ ​ ​ ​ ​ ​ in response to the periodic task being triggered, determining a state of the target task corresponding to the periodic task; and in response to the target task being in an active state, triggering the periodic task to provide the content to the target user.

10. The method of claim 9, further comprising: in response to the periodic task being executed, updating deadline information of the periodic task.

11. An apparatus for task management, comprising: an obtaining module configured to obtain, based on a first interaction of a target user with a virtual object, a first request of the target user for a target task of periodically obtaining content; a first creating module configured to create, based on the first request, a delay task associated with timing information indicated by the first request, the delay task being used to trigger a generation process of content; and a second creating module configured to create, in response to the delay task being created, a periodic task associated with the timing information, the periodic task being used to trigger a periodic provision of the generated content to the target user according to the timing information.

12. An electronic device, comprising: at least one processing unit; and at least one memory that is coupled to the at least one processing unit and stores instructions for execution by the at least one processing unit, the instructions, when executed by the at least one processing unit, cause the electronic device to perform the method according to any one of claims 1 to 10.

13. A computer-readable storage medium having stored thereon a computer program, the computer program being executable by a processor to implement the method according to any one of claims 1 to 10.

Images