CN117130739A

CN117130739A - Task management method, task configuration method, task display method and device

Info

Publication number: CN117130739A
Application number: CN202210554569.7A
Authority: CN
Inventors: 石智灵; 程亮; 程超
Original assignee: Tencent Technology Shenzhen Co Ltd
Current assignee: Tencent Technology Shenzhen Co Ltd
Priority date: 2022-05-19
Filing date: 2022-05-19
Publication date: 2023-11-28

Abstract

The embodiment of the application discloses a task management method, a task configuration method, a task display method and a task display device, and belongs to the technical field of computers. The method comprises the following steps: the method comprises the steps that a first terminal creates at least two tasks and task flows of a target application program based on a task configuration interface corresponding to the target application program, wherein the task flows comprise at least two task nodes corresponding to the at least two tasks and trigger conditions between any two task nodes; the first terminal determines task configuration information of a target application program based on at least two tasks and task flows and sends the task configuration information to a server; the server determines task configuration information matched with the trigger event based on the trigger event sent by the second terminal, and sends the task configuration information to the second terminal; and the second terminal displays task content in at least one task according to the task flow in the task configuration information. The task management mode improves the relevance among the tasks and the display effect of the tasks.

Description

Task management method, task configuration method, task display method and device

Technical Field

The embodiment of the application relates to the technical field of computers, in particular to a task management method, a task configuration method, a task display method and a task display device.

Background

With the development of computer technology, in order to effectively display various types of information in an application program, a method for displaying tasks is currently provided, the information to be displayed is created into tasks, and the tasks are displayed in the application program so as to attract users to view task contents or execute certain operations on the displayed tasks.

Of course, the task needs to be configured before the task is displayed, in the related art, a technician configures one task at a time, and the task can be released after the task is configured. However, this task configuration method needs to configure each task separately, and the correlation between the configured tasks is poor.

Disclosure of Invention

The embodiment of the application provides a task management method, a task configuration method, a task display method and a task display device, which improve the relevance among various tasks and the task display effect. The technical scheme is as follows:

in one aspect, a task management method is provided, the method being performed by a task management system, the task management system including a first terminal, a server, and a second terminal, the method including:

The first terminal creates at least two tasks and task flows of a target application program based on a task configuration interface corresponding to the target application program, wherein the task flows comprise at least two task nodes corresponding to the at least two tasks and trigger conditions between any two task nodes, each two task nodes comprise a leading task node and a following task node, and the trigger conditions between the leading task node and the following task node indicate that the task corresponding to the leading task node executes the task corresponding to the following task node under the condition that the task corresponding to the leading task node meets the trigger conditions;

the first terminal determines task configuration information of the target application program based on the at least two tasks and the task flow, and sends the task configuration information to the server, wherein the task configuration information is used for indicating to display tasks according to the task flow;

the server determines the task configuration information matched with the trigger event based on the trigger event sent by the second terminal, and sends the task configuration information to the second terminal, wherein the task configuration information is matched with the trigger event: the trigger event is a trigger event corresponding to a first task in the task configuration information, and the first task is a task corresponding to a first task node in the task configuration information;

And the second terminal displays task content in at least one task according to the task flow in the task configuration information.

In another aspect, a task configuration method is provided, the method including:

displaying a task configuration interface corresponding to the target application program;

creating at least two tasks of the target application program based on the task configuration interface;

creating a task flow based on the task configuration interface, wherein the task flow comprises at least two task nodes corresponding to the at least two tasks and trigger conditions between any two task nodes, each two task nodes comprises a preamble task node and a successor task node, and the trigger conditions between the preamble task node and the successor task node indicate that the task corresponding to the successor task node is executed under the condition that the task corresponding to the preamble task node meets the trigger conditions;

and determining task configuration information of the target application program based on the at least two tasks and the task flow, wherein the task configuration information is used for indicating to display tasks according to the task flow.

In one possible implementation manner, the task corresponding to the task node is a task indicated by a task identifier included in the task node, and the creating a task flow based on the task configuration interface includes:

Inputting a first task identifier corresponding to a first task in a first task node in the task configuration interface, wherein the first task node is a displayed task node in the task configuration interface;

responding to the triggering operation of a successor node adding control corresponding to the first task node, and adding the successor task node of the first task node;

adding a triggering condition between the first task node and a subsequent task node of the first task node;

and inputting a second task identifier corresponding to a second task into a subsequent task node of the first task node.

In another possible implementation manner, the inputting, in a first task node in the task configuration interface, a first task identifier corresponding to a first task includes:

inputting a first task type in the first task node;

displaying a task identifier corresponding to at least one task belonging to the first task type;

and responding to the selection operation of the first task identifier in at least one task identifier, and inputting the first task identifier in the first task node.

In another possible implementation manner, the adding a trigger condition between the first task node and a subsequent task node of the first task node includes:

Displaying a preset trigger condition between the first task node and a subsequent task node of the first task node;

responding to the selection operation of the preset trigger conditions, and displaying a plurality of trigger conditions;

and responding to the selection operation of any trigger condition in the plurality of trigger conditions, and replacing the preset trigger condition with the selected trigger condition.

In another possible implementation, the method further includes:

and deleting the task node and the subsequent task nodes of the task node in response to the deleting operation of any task node displayed in the task configuration interface.

In another possible implementation manner, the creating at least two tasks of the target application program based on the task configuration interface includes:

acquiring a template identifier and task content input in the task configuration interface;

creating a task based on the template identification and the task content;

the task comprises the template identification and the task content, wherein the template identification indicates a task template, and the task indication displays the task content according to the task template.

In another possible implementation manner, before the obtaining the template identifier and the task content input in the task configuration interface, the method further includes:

Displaying a template configuration interface;

acquiring an input template identifier, a template style and a display form based on the template configuration interface;

creating the task template based on the template identification, the template style and the display form;

the template style comprises at least one category and a display position corresponding to each category, the template style is used for determining that task contents belonging to the category are filled in the display positions in the task template, and the display form is used for determining the display positions of the task template on the terminal when the terminal displays the task contents according to the task template.

In another possible implementation, the method further includes:

and sending the task template to a server corresponding to the target application program, wherein the server is used for sending a target task and a task template corresponding to a template identifier in the target task to the terminal so that the terminal displays task content in the target task according to the task template.

In another possible implementation manner, after the creating a task based on the template identifier and the task content, the method further includes:

Acquiring a release condition input in the task configuration interface, and establishing a corresponding relation between the task and the release condition, wherein the release condition indicates a condition which needs to be met when task configuration information taking the task as a first task is released, and the first task is a task corresponding to a first task node in the task configuration information;

the issuing condition comprises at least one of a condition to be met by a terminal receiving the task, a trigger event for indicating to issue the task, a condition to be met by an issuing object and a condition to be met by issuing time.

In another possible implementation manner, after the obtaining the release condition corresponding to the task input in the task configuration interface and establishing the correspondence between the task and the release condition, the method further includes:

and sending the corresponding relation between the task and the release condition to a server corresponding to the target application program, wherein the server is used for releasing task configuration information taking the task as a first task based on the release condition.

In another possible implementation, the method further includes:

And sending the task configuration information to a server corresponding to the target application program, wherein the server is used for sending the task configuration information to a terminal so that the terminal displays the task according to the task flow.

In another aspect, a task display method is provided, the method including:

receiving task configuration information of a target application program, wherein the task configuration information comprises at least two tasks and a task flow, the task flow comprises at least two task nodes corresponding to the at least two tasks and trigger conditions between any two task nodes, each two task nodes comprises a preamble task node and a successor task node, the trigger conditions between the preamble task node and the successor task node indicate that the task corresponding to the successor task node is executed under the condition that the task corresponding to the preamble task node meets the trigger conditions;

displaying task content in a first task according to the task flow, wherein the first task is a task corresponding to any task node in the task configuration information;

and displaying task content in a second task corresponding to the target trigger condition when the first task meets the target trigger condition, wherein the target trigger condition is a trigger condition between a first task node corresponding to the first task and other task nodes in the task flow, and the second task is a task corresponding to a subsequent task node to which the target trigger condition belongs.

In one possible implementation manner, the receiving task configuration information of the target application program includes:

responding to a trigger event detected based on the target application program, and sending the trigger event to a server corresponding to the target application program, wherein the server is used for determining and returning task configuration information matched with the trigger event from a plurality of task configuration information based on the trigger event;

receiving the task configuration information sent by the server;

wherein, the matching of the task configuration information with the trigger event means that: the trigger event is a trigger event corresponding to a first task in the task configuration information, and the first task is a task corresponding to a first task node in the task configuration information.

In another possible implementation manner, the sending the trigger event to the server corresponding to the target application program includes:

the trigger event and the terminal information of the current terminal are sent to the server, and the server is used for determining and returning task configuration information matched with the trigger event and the terminal information from a plurality of task configuration information based on the trigger event;

Wherein, the matching of the task configuration information with the trigger event means that: the triggering event is a triggering event corresponding to the first task, and the terminal information meets the release condition corresponding to the first task.

In another possible implementation manner, after displaying the task content in the first task according to the task flow, the method further includes:

under the condition that a trigger event meeting any target trigger condition is not detected in a first time period after the task content is displayed, canceling to display the task content;

and after the second time period passes after the display of the task content is canceled, the task content is displayed again.

In another possible implementation manner, displaying the task content in the first task according to the task flow includes:

acquiring first display times of the task content, wherein the first display times are display times in a first reference time before a current time point;

and displaying the task content under the condition that the first display times do not exceed a first time number threshold.

Acquiring second display times, wherein the second display times are the total times of task contents displayed in a second reference time before the current time point;

and displaying the task content under the condition that the second display times do not exceed a second time threshold.

under the condition that a plurality of task configuration information is received, determining task configuration information with highest priority of the plurality of task configuration information;

and displaying task content in a first task according to the task flow of the task configuration information with the highest priority, wherein the first task is any task in the task configuration information with the highest priority.

In another aspect, a task publishing method is provided, the method including:

acquiring task configuration information, wherein the task configuration information is determined based on at least two tasks and a task flow, and is used for indicating to display the tasks according to the task flow, the task flow comprises at least two task nodes corresponding to the at least two tasks and trigger conditions between any two task nodes, each two task nodes comprises a leading task node and a following task node, and the trigger conditions between the leading task node and the following task node indicate to execute the tasks corresponding to the following task node under the condition that the tasks corresponding to the leading task node meet the trigger conditions;

Based on a trigger event sent by a terminal, determining task configuration information matched with the trigger event, wherein the task configuration information is matched with the trigger event: the trigger event is a trigger event corresponding to a first task in the task configuration information, and the first task is a task corresponding to a first task node in the task configuration information;

and sending task configuration information matched with the trigger event to the terminal, wherein the terminal is used for displaying task content in at least one task according to task flow in the task configuration information.

In one possible implementation, the method further includes:

acquiring a corresponding relation between a task and a release condition, wherein the release condition comprises at least one of a condition to be met by a terminal for receiving the task, a trigger event for indicating release of the task, a condition to be met by a release object and a condition to be met by release time;

the determining task configuration information matched with the trigger event based on the trigger event sent by the terminal comprises the following steps:

determining task configuration information matched with the trigger event based on the trigger event and the terminal information sent by the terminal, wherein the task configuration information is matched with the trigger event: the triggering event is a triggering event corresponding to the first task, and the terminal information meets the release condition corresponding to the first task.

In another possible implementation manner, the task in the task configuration information includes a template identifier, and the method further includes:

acquiring a task template, wherein the task template is created based on a template identifier, a template pattern and a display form, the template pattern comprises at least one category and a display position corresponding to each category, the template pattern is used for determining that task contents belonging to the category are filled in the display position in the task template, and the display form is used for determining the display position of the task template on a terminal when the terminal displays the task contents according to the task template;

the sending task configuration information matched with the trigger event to the terminal comprises the following steps:

determining a task template corresponding to the template identifier based on the template identifier in the task configuration information matched with the trigger event;

and sending task configuration information matched with the trigger event and the task template to the terminal, wherein the terminal is used for displaying task content in a corresponding task according to the task template.

In another possible implementation manner, the sending, to the terminal, task configuration information matched with the trigger event includes:

Selecting a target release channel from a plurality of release channels, wherein the release channels comprise a first release channel, a second release channel and a third release channel, the first release channel is used for releasing tasks based on the target application program, the second release channel is used for releasing tasks based on other application programs associated with the target application program, and the third release channel is used for releasing tasks based on an operating system of the terminal;

and sending task configuration information matched with the trigger event to the terminal through the target release channel.

In another aspect, a task configuration device is provided, the device including:

the interface display module is used for displaying a task configuration interface corresponding to the target application program;

the task creation module is used for creating at least two tasks of the target application program based on the task configuration interface;

the process creation module is used for creating a task process based on the task configuration interface, wherein the task process comprises at least two task nodes corresponding to the at least two tasks and trigger conditions between any two task nodes, each two task nodes comprises a preamble task node and a successor task node, and the trigger conditions between the preamble task node and the successor task node indicate that the task corresponding to the successor task node is executed under the condition that the task corresponding to the preamble task node meets the trigger conditions;

The configuration information determining module is used for determining task configuration information of the target application program based on the at least two tasks and the task flow, and the task configuration information is used for indicating to display tasks according to the task flow.

In one possible implementation manner, the task corresponding to the task node is a task indicated by a task identifier included in the task node, and the flow creation module includes:

the identification input unit is used for inputting a first task identification corresponding to a first task in a first task node in the task configuration interface, wherein the first task node is a displayed task node in the task configuration interface;

the node adding unit is used for responding to the triggering operation of adding a control to the successor node corresponding to the first task node and adding the successor task node of the first task node;

a trigger condition adding unit, configured to add a trigger condition between the first task node and a subsequent task node of the first task node;

the identifier input unit is further configured to input a second task identifier corresponding to a second task in a subsequent task node of the first task node.

In another possible implementation manner, the identification input unit is configured to:

inputting a first task type in the first task node;

In another possible implementation manner, the trigger condition adding unit is configured to:

In another possible implementation, the apparatus further includes:

and the node deleting module is used for responding to the deleting operation of any task node displayed in the task configuration interface and deleting the task node and the subsequent task nodes of the task node.

In another possible implementation manner, the task creation module is configured to:

creating a task based on the template identification and the task content;

In another possible implementation, the apparatus further includes: the template creation module is used for:

displaying a template configuration interface;

In another possible implementation, the apparatus further includes:

The template sending module is used for sending the task template to a server corresponding to the target application program, and the server is used for sending a target task and a task template corresponding to a template identifier in the target task to the terminal so that the terminal can display task content in the target task according to the task template.

In another possible implementation, the apparatus further includes:

the task configuration interface is used for acquiring task configuration information of a first task node in the task configuration information, and acquiring a task configuration condition input in the task configuration interface;

In another possible implementation, the apparatus further includes:

the corresponding relation sending module is used for sending the corresponding relation between the task and the release condition to a server corresponding to the target application program, and the server is used for releasing task configuration information taking the task as a first task based on the release condition.

In another possible implementation, the apparatus further includes:

the configuration information sending module is used for sending the task configuration information to a server corresponding to the target application program, and the server is used for sending the task configuration information to a terminal so that the terminal can display tasks according to the task flow.

In another aspect, there is provided a task display device, the device including:

the configuration information receiving module is used for receiving task configuration information of a target application program, the task configuration information comprises at least two tasks and a task flow, the task flow comprises at least two task nodes corresponding to the at least two tasks and trigger conditions between any two task nodes, each two task nodes comprises a front task node and a rear task node, the trigger conditions between the front task node and the rear task node indicate that the task corresponding to the front task node executes the task corresponding to the rear task node under the condition that the task corresponding to the front task node meets the trigger conditions;

the task display module is used for displaying task content in a first task according to the task flow, wherein the first task is a task corresponding to any task node in the task configuration information;

The task display module is further configured to display task content in a second task corresponding to a target trigger condition when the first task meets the target trigger condition, where the target trigger condition is a trigger condition between a first task node corresponding to the first task and other task nodes in the task flow, and the second task is a task corresponding to a subsequent task node to which the target trigger condition belongs.

In one possible implementation manner, the configuration information receiving module includes:

a trigger event sending unit, configured to respond to a trigger event detected based on the target application program, and send the trigger event to a server corresponding to the target application program, where the server is configured to determine and return task configuration information matched with the trigger event from multiple task configuration information based on the trigger event;

the configuration information receiving unit is used for receiving the task configuration information sent by the server;

In another possible implementation manner, the trigger event sending unit is configured to:

In another possible implementation manner, the task display module is further configured to:

In another possible implementation manner, the task display module is configured to:

In another aspect, there is provided a task issuing apparatus including:

the configuration information acquisition module is used for acquiring task configuration information, the task configuration information is determined based on at least two tasks and a task flow, the task configuration information is used for indicating to display tasks according to the task flow, the task flow comprises at least two task nodes corresponding to the at least two tasks and trigger conditions between any two task nodes, each two task nodes comprises a preamble task node and a successor task node, the trigger conditions between the preamble task node and the successor task node indicate to execute the tasks corresponding to the successor task node under the condition that the tasks corresponding to the preamble task node meet the trigger conditions;

The configuration information matching module is used for determining task configuration information matched with a trigger event based on the trigger event sent by the terminal, wherein the task configuration information is matched with the trigger event: the trigger event is a trigger event corresponding to a first task in the task configuration information, and the first task is a task corresponding to a first task node in the task configuration information;

the configuration information sending module is used for sending task configuration information matched with the trigger event to the terminal, and the terminal is used for displaying task content in at least one task according to task flow in the task configuration information.

In one possible implementation, the apparatus further includes:

the system comprises a corresponding relation acquisition module, a distribution module and a distribution module, wherein the corresponding relation acquisition module is used for acquiring a corresponding relation between a task and a distribution condition, and the distribution condition comprises at least one of a condition which needs to be met by a terminal for receiving the task, a trigger event for indicating to distribute the task, a condition which needs to be met by a distribution object and a condition which needs to be met by distribution time;

the configuration information matching module is configured to determine task configuration information matched with a trigger event based on the trigger event and terminal information sent by the terminal, where the task configuration information is matched with the trigger event: the triggering event is a triggering event corresponding to the first task, and the terminal information meets the release condition corresponding to the first task.

In another possible implementation manner, the task in the task configuration information includes a template identifier, and the apparatus further includes:

the system comprises a template acquisition module, a template processing module and a display module, wherein the template acquisition module is used for acquiring a task template, the task template is created based on a template identifier, a template pattern and a display form, the template pattern comprises at least one category and a display position corresponding to each category, the template pattern is used for determining that task contents belonging to the category are filled in the display position in the task template, and the display form is used for determining the display position of the task template on a terminal when the terminal displays the task contents according to the task template;

the configuration information sending module is configured to:

In another possible implementation manner, the configuration information sending module is configured to:

In another aspect, there is provided a terminal including a processor and a memory in which at least one computer program is stored, the at least one computer program being loaded and executed by the processor to implement the operations performed by the task configuration method or the task display method as described in the above aspect.

In another aspect, a server is provided, the server including a processor and a memory, the memory storing at least one computer program, the at least one computer program being loaded and executed by the processor to implement the operations performed by the task issuing method as described in the above aspect.

In another aspect, there is provided a computer-readable storage medium having stored therein at least one computer program loaded and executed by a processor to implement the operations performed by the task configuration method, the task display method, or the task distribution method as described in the above aspects.

In another aspect, a computer program product is provided, including a computer program that, when executed by a processor, implements the operations performed by the task configuration method, the task display method, or the task distribution method described in the above aspect.

The task management scheme provided by the embodiment of the application comprises the steps that a first terminal configures a task, a task flow is created through a task configuration interface, at least two created tasks are associated through a task node in the task flow and trigger conditions between a former task node and a latter task node, task configuration information is determined based on at least two tasks and the task flow, the task configuration information is sent to a server, then the server sends the task configuration information to a second terminal after receiving a trigger event which is sent by the second terminal and is matched with the task configuration information, and the second terminal can display task content in at least one task according to the task flow in the task configuration information. In the whole task management process, each task is firstly associated through a task flow when the task is configured, so that the association between each task is improved, then when the task is issued, the association between each task displayed in sequence is considered, and the display effect of the task is improved by only determining whether the trigger event corresponding to the first task in the task configuration information is consistent with the received trigger event and not carrying out the corresponding operation on each task in the task configuration information, so that the issuing efficiency of the task configuration information is improved, and finally, when the task is displayed, the tasks are displayed according to the task flow, so that the association between each task displayed in sequence is improved.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are needed in the description of the embodiments will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.

FIG. 1 is a schematic diagram of a task management system according to an embodiment of the present application;

FIG. 2 is a schematic diagram of another task management system provided by an embodiment of the present application;

FIG. 3 is a flowchart of a task configuration method provided by an embodiment of the present application;

FIG. 4 is a flowchart of another task configuration method provided by an embodiment of the present application;

FIG. 5 is a schematic diagram of a task configuration interface provided by an embodiment of the present application;

FIG. 6 is a schematic diagram of a configuration entry interface provided by an embodiment of the present application;

FIG. 7 is a schematic diagram of a task creation area provided by an embodiment of the present application;

FIG. 8 is a schematic diagram of a distribution condition configuration area according to an embodiment of the present application;

FIG. 9 is a schematic diagram of another distribution condition configuration area provided by an embodiment of the present application;

FIG. 10 is a schematic diagram of a template configuration interface provided by an embodiment of the present application;

FIG. 11 is a schematic diagram of a task identity input process provided by an embodiment of the present application;

FIG. 12 is a schematic diagram of a task flow creation area provided by an embodiment of the present application;

FIG. 13 is a schematic diagram of a task node addition process provided by an embodiment of the present application;

FIG. 14 is a schematic diagram of a trigger condition input process provided by an embodiment of the present application;

FIG. 15 is a flowchart of a task publishing method according to an embodiment of the present application;

FIG. 16 is a flowchart of a task display method provided by an embodiment of the present application;

FIG. 17 is a flowchart of another task display method provided by an embodiment of the present application;

FIG. 18 is a schematic diagram of a task display process provided by an embodiment of the present application;

FIG. 19 is a schematic diagram of another task display process provided by an embodiment of the present application;

FIG. 20 is a schematic diagram of yet another task display process provided by an embodiment of the present application;

FIG. 21 is a flowchart of a task management method according to an embodiment of the present application;

FIG. 22 is a schematic diagram illustrating interaction between a second terminal and a server according to an embodiment of the present application;

FIG. 23 is a schematic diagram of yet another task display process provided by an embodiment of the present application;

FIG. 24 is a schematic diagram of a task configuration device according to an embodiment of the present application;

FIG. 25 is a schematic diagram of a task display device according to an embodiment of the present application;

FIG. 26 is a schematic diagram of a task issuing device according to an embodiment of the present application;

fig. 27 is a schematic structural diagram of a terminal according to an embodiment of the present application;

fig. 28 is a schematic structural diagram of a server according to an embodiment of the present application.

Detailed Description

For the purpose of making the objects, technical solutions and advantages of the embodiments of the present application more apparent, the following detailed description of the embodiments of the present application will be given with reference to the accompanying drawings.

It is to be understood that the terms "first," "second," and the like, as used herein, may be used to describe various concepts, but are not limited by these terms unless otherwise specified. These terms are only used to distinguish one concept from another. For example, the first permutation may be referred to as a second permutation and the second permutation may be referred to as a first permutation without departing from the scope of the present application.

The terms "at least one", "a plurality", "each", "any" and the like as used herein, at least one includes one, two or more, a plurality includes two or more, each means each of the corresponding plurality, and any one means any of the plurality. For example, the plurality of tasks includes 3 tasks, and each task refers to each of the 3 tasks, and any one of the 3 tasks may be the first task, the second task, or the third task.

It will be appreciated that in the specific embodiments of the present application, related data such as user information is involved, and when the above embodiments of the present application are applied to specific products or technologies, user permissions or consents need to be obtained, and the collection, use and processing of related data need to comply with related laws and regulations and standards of related countries and regions.

In order to facilitate understanding of the embodiments of the present application, keywords related to the embodiments of the present application are explained:

single task: i.e. a single task scenario, a task of a single task content, such as a push task. In addition, there are a plurality of task scenes, a plurality of tasks of task contents, such as a task of combining a push task and an icon task. The task scene is divided into an external pushing scene of the application program, an internal pushing scene of the application program and an applet pushing scene.

Task type: the task types are distinguished according to task scenes, the task types supported by different task scenes are different, the task types comprise three types of an external task type of an application program, an internal task type of the application program and an applet task type, and a plurality of other task types can be further included under each task type divided according to the task scenes. For example, the application external task types include a notification bar task type and an application icon task type, and the application internal task types include a top page recommended task type, a popup task type, and a message center task type.

Task identification: and may also be referred to as a task list number, which is an independent unique identifier configured for each task, through which a task can be quickly searched, or through which a task can be quickly referenced in configuring task configuration information.

Task flow canvas: the task flow canvas may also be referred to as a task flow creation area, based on which multiple tasks are serially or parallelly connected through multiple trigger conditions, thereby combining a complete task flow. The task flow canvas supports task flow orchestration capabilities that are triggered by user operations, support multi-step and logical control, support multi-policy combinations of workflow. Supporting user operation triggering refers to determining a task to be displayed next based on user operation in the process of displaying the task; supporting multi-step and logic control means that a plurality of tasks are mutually related through task flows, the tasks are displayed in a plurality of steps when being displayed, and each task has a logic relationship; multiple policy combining supporting workflow refers to supporting the association of multiple tasks with one another.

Fig. 1 is a schematic diagram of a task management system according to an embodiment of the present application. Referring to fig. 1, the task management system includes a first terminal 101 and a server 102. The first terminal 101 and the server 102 are connected by a wireless or wired network. Optionally, the first terminal 101 is a computer, a mobile phone, a tablet computer, or other terminals. Optionally, the server 102 is a stand-alone physical server, or a server cluster or a distributed system formed by a plurality of physical servers, or a cloud server providing cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDNs (Content Delivery Network, content delivery networks), and basic cloud computing services such as big data and artificial intelligence platforms.

In one possible implementation, the first terminal 101 installs a first application program served by the server 102, and the first terminal 101 can implement functions such as task creation, task flow creation, and task configuration through the first application program. For example, the first application configures an application for a task. The first terminal 101 creates a task through a task configuration interface in the first application program, creates a task flow, and determines task configuration information based on the created task and task flow, and then sends the task, task flow, or task configuration information to the server 102, so that the server 102 can issue a task to the terminal based on the task flow. Optionally, the server 102 is a background server of the first application program or a cloud server that provides services such as cloud computing and cloud storage.

Optionally, a database is configured in the server 102, in which task configuration information is stored. The database can perform operations such as adding, inquiring, updating, deleting and the like on stored data, and is a data set which is stored together in a certain mode, can be shared with a plurality of users, has the smallest redundancy as possible and is independent of application programs. The database can be managed by a database management system to ensure the safety of task configuration information stored in the database, and the database management system has the functions of storage, interception, safety guarantee, backup and the like.

In one possible implementation, referring to fig. 2, the task management system further includes a second terminal 103, where the second terminal 103 and the server 102 are connected through a wired or wireless network, and the second terminal 103 receives the task issued by the server 102. A target application is installed on the second terminal 103, and the second terminal 103 can realize functions such as task display by the target application. Wherein the target application is different from the first application. For example, the target application is an application such as an instant messaging application, a video playing application, or the like. Optionally, the second terminal 102 is a computer, a mobile phone, a tablet computer, or other terminals.

The method provided by the embodiment of the application comprises a task configuration process, a task release process and a task display process, and the task configuration process is explained first.

Fig. 3 is a flowchart of a task configuration method according to an embodiment of the present application. The embodiment of the application is executed by the first terminal. Referring to fig. 3, the method includes the steps of:

301. the first terminal displays a task configuration interface corresponding to the target application program.

The task configuration interface corresponding to the target application program is used for configuring tasks for the target application program.

302. The first terminal creates at least two tasks of the target application based on the task configuration interface.

In the embodiment of the application, the first terminal can create at least two tasks for the target application program based on the task configuration interface, wherein the at least two tasks are respectively created based on the task configuration interface. Wherein each task has a corresponding task identity for uniquely representing a corresponding one of the tasks.

303. The first terminal creates a task flow based on a task configuration interface, wherein the task flow comprises at least two task nodes corresponding to at least two tasks and trigger conditions between any two task nodes, each two task nodes comprise a preamble task node and a successor task node, and the trigger conditions between the preamble task node and the successor task node indicate that the task corresponding to the successor task node is executed under the condition that the task corresponding to the preamble task node meets the trigger conditions.

After the first terminal creates at least two tasks, a task flow is created based on a task configuration interface, in the process of creating the task flow, task nodes corresponding to each task and trigger conditions between a preceding task node and a subsequent task node are sequentially created, the tasks corresponding to the preceding task node and the tasks corresponding to the subsequent task node are associated through the trigger conditions, namely, each independent task is associated through the task flow, the association between each task is improved, and the next associated task is conveniently displayed in the process of displaying the tasks according to whether the displayed tasks meet the corresponding trigger conditions or not.

304. The first terminal determines task configuration information of the target application program based on at least two tasks and task flows, wherein the task configuration information is used for indicating to display tasks according to the task flows.

The first terminal determines task configuration information based on task flows and tasks corresponding to task nodes in the task flows, and can sequentially display tasks in the task configuration information based on the task flows in the task configuration information later when the tasks are displayed, namely, for any preceding task node and a subsequent task node corresponding to the preceding task node, when task content in the tasks corresponding to the preceding task node is displayed, when the tasks corresponding to the preceding task node meet triggering conditions, task content in the tasks corresponding to the subsequent task node is displayed.

In the method provided by the embodiment of the application, in the process of configuring tasks, the tasks and the task flows can be created through the task configuration interface of the target application program, the created at least two tasks are associated through the task nodes in the created task flows and the trigger conditions between the former task nodes and the latter task nodes, the task configuration information is determined based on the at least two tasks and the task flows, the relevance among the tasks is improved, and the tasks in the task configuration information can be displayed subsequently based on the task flows in the task configuration information, so that the subsequently displayed tasks can be determined in real time based on the trigger conditions in the process of displaying the tasks

The embodiment shown in fig. 3 above simply illustrates the task configuration process, which is described in detail below with respect to the embodiment of fig. 4.

Fig. 4 is a flowchart of another task configuration method according to an embodiment of the present application. The embodiment of the application is executed by the first terminal. Referring to fig. 4, the method includes the steps of:

401. the first terminal displays a task configuration interface corresponding to the target application program.

The target application is any application requiring a task to be configured, for example, the target application is an application such as an instant messaging application, a video playing application, and the like. The task configuration interface corresponding to the target application program is used for configuring tasks for the target application program.

In one possible implementation manner, the first terminal is provided with a first application program, and the first terminal displays a task configuration interface corresponding to the target application program based on the first application program. The first application program is used for creating tasks, creating task flows and configuring task configuration information, and is different from the target application program, and the first application program is an application program which is associated with the target application program and is used for configuring tasks for the target application program.

In one possible implementation, the task configuration interface includes a task creation area for creating a task and a task flow creation area for creating a task flow. For example, referring to the task configuration interface 501 shown in fig. 5, the task configuration interface 501 includes a task creation area 502 and a task flow creation area 503.

In one possible implementation manner, the first terminal displays a configuration entry interface corresponding to the target application program, and responds to a triggering operation of the configuration entry in the configuration entry interface to display a task configuration interface of the target application program.

Optionally, the configuration portal interface includes multiple types of configuration portals, different tasks can be configured by triggering task configuration interfaces displayed by the different types of configuration portals, and the configuration portal interface includes an external task configuration portal, an internal task configuration portal, and an applet task configuration portal. The task configuration interface is triggered to display a task configuration interface, and external tasks displayed outside the target application program can be created based on the task configuration interface; the task configuration interface is displayed by triggering the internal task configuration inlet, and the internal task displayed in the target application program can be created based on the task configuration interface; by triggering the applet task configuration portal to display a task configuration interface, the tasks displayed in the applet of the target application can be created based on the task configuration interface. For example, referring to FIG. 6, the configuration entry interface 601 includes an external task configuration entry 602, an internal task configuration entry 603, and an applet task configuration entry 604.

402. The first terminal creates at least two tasks of the target application based on the task configuration interface.

In the embodiment of the application, the first terminal can create at least two tasks for the target application program based on the task configuration interface, and the creation modes of different tasks are similar, and the creation process of the task is described below by taking any task as an example:

in one possible implementation, the first terminal obtains a template identifier and task content input in the task configuration interface, and creates a task based on the template identifier and the task content. The task comprises a template identifier and task content, wherein the template identifier indicates task templates, and each template identifier is used for indicating a unique corresponding task template; the task indication displays task content according to a task template, wherein the task template indicates the display position of the task template on the terminal and the display position of the task content in the task template.

The task content comprises at least one of a task identifier, a task name, a task title, a task icon or a button document, wherein the task identifier is an identifier uniquely representing the task; task names are used for facilitating task understanding; the task title is a title when the task is displayed, optionally, the task title comprises a main title and a sub-title; the task icon is a picture displayed when the task is displayed, the task icon is input in a picture uploading mode or a picture link filling mode, and after the picture is input, the picture can be previewed or cleared on the task configuration interface; the button document is a document displayed in a button in the case where the button is displayed at the time of task display.

Alternatively, the task configuration interface includes a task creation area, and obtains a template identifier and task content input in the task creation area, for example, referring to a task creation area 701 shown in fig. 7, in the task creation area 701, a task name, a task identifier, a template identifier, a main title, a subtitle, an icon, and a button document are input.

In one possible implementation, after the first terminal creates a task, the first terminal can continue to configure a corresponding publishing condition for the task. The first terminal acquires a release condition input in a task configuration interface, and establishes a corresponding relation between the task and the release condition, wherein the release condition indicates that the corresponding task is released based on the release condition.

The issuing condition comprises at least one of a condition to be met by a terminal receiving the task, a trigger event for indicating the issuing task, a condition to be met by an issuing object and a condition to be met by issuing time. The condition that the terminal receiving the task needs to meet is a terminal condition, and the terminal condition refers to a condition that the attribute of the terminal needs to meet, for example, the storable capacity of the terminal, whether the terminal opens a storage authority, and the like; the trigger event is an event executed by the object detected by the terminal, for example, the trigger event is a start operation of the application program, a switching operation of an interface in the application program, and the like; the conditions to be met by the published object are conditions to be met by an object account of the login application program, for example, the object account belongs to a specific category and the like; the condition that the issue time needs to be satisfied refers to a condition that the time when the task is issued needs to be satisfied, for example, the issue time belongs to a period of 12:00-18:00.

Optionally, the task configuration interface includes a release condition configuration area, and the first terminal acquires release conditions input in the release condition configuration area. For example, referring to the distribution condition configuration area 801 shown in fig. 8, the first terminal configures a trigger event and a terminal condition in the distribution condition configuration area. Specifically, the first terminal configures a trigger event identifier and a trigger event name corresponding to the trigger event, where the trigger event identifier is used to uniquely represent a trigger event, and the trigger event name is the name of the trigger event, and optionally, the trigger event identifier and the trigger event name may be the same or different. The first terminal configures a terminal condition identifier and a terminal condition name corresponding to the terminal condition, and configures content of the terminal condition, for example, the name, the type and the default value of a certain condition in the configured terminal condition as shown in fig. 8, for example, the terminal condition is that a remaining capacity storable by the terminal needs to be greater than 100M.

For another example, referring to the distribution condition configuration area 901 shown in fig. 9, the first terminal configures a distribution condition for a task based on the distribution condition configuration area 901, and can configure at least one trigger condition and a plurality of terminal conditions for the task, where the plurality of terminal conditions may be an "or" relationship or an "and" relationship.

In order to enable the server to which the target application corresponds to issue a task, in one possible implementation, the first terminal sends the created task to the server so that the server can issue the task to the second terminal later.

Optionally, in order to facilitate the server to issue the task based on the issue condition, the first terminal sends a correspondence between the task and the issue condition to the server corresponding to the target application, and the server stores the correspondence, so that the server issues the corresponding task based on the issue condition.

For the task created in the above embodiment, the task instruction displays the task content according to a task template, wherein the task template is preconfigured. In one possible implementation, the first terminal displays a template configuration interface; acquiring an input template identifier, a template style and a display form based on a template configuration interface; a task template is created based on the template identification, the template style, and the display form.

Wherein the template identifier is used for uniquely indicating the task template; the template style comprises at least one category and a display position corresponding to each category, the template style is used for determining that task content belonging to the corresponding category is filled in the display position in the task template, namely, when the task content is displayed, the task content belonging to the category is required to be displayed in the display position corresponding to each category in the task template, and the category refers to the category of the task content required to be filled in, for example, the category comprises at least one of a task identification category, a task name category, a task title category, a task icon category or a button document category; the display form is used for determining the display position of the task template on the terminal when the terminal displays the task content according to the task template, and comprises displaying the task template on a notification bar, displaying the task template on an interface of an application program in a popup form, displaying the task template in a first page of the application program, displaying the task template in a message form in a message center of the application program, and the like.

For example, referring to the template configuration interface 1001 shown in fig. 10, a template identifier, a template name, whether notification bar display is supported, whether jump link is supported, a display form, an effect graph, and a service field are input in the template configuration interface 1001, where the effect graph is used to show a display style of task content in the task template, and the service field indicates inputtable task content.

In one possible implementation manner, the first terminal sends a task template to a server corresponding to the target application program, so that the server sends a target task and a task template corresponding to a template identifier in the target task to the terminal installed with the target application program, and the terminal displays task content in the target task according to the task template. The target task refers to any task stored in the server.

It should be noted that, in the embodiment of the present application, only one task is created as an example, and when a plurality of tasks are created, the release conditions corresponding to the plurality of tasks may be the same or different, which is not limited in the embodiment of the present application. Each task has a corresponding priority, and when the corresponding release conditions of the plurality of tasks are the same, the task with the highest priority needs to be released according to the priority of the task.

403. The first terminal displays a first task node in a task configuration interface, and inputs a first task identifier corresponding to the first task in the first task node.

The first task node is any task node displayed in the task configuration interface, and the task corresponding to the task node is a task indicated by a task identifier contained in the task node. And when the first task node is the first task node, creating a task flow from the first task node.

Inputting the first task identification in the first task node comprises: inputting a first task identifier in the first task node through a keyboard or other equipment; or displaying a plurality of task identifications at the first task node, and selecting the first task identification from the plurality of task identifications.

In one possible implementation, a first task type is input in a first task node; displaying task identifiers corresponding to at least one task belonging to the first task type; in response to a selection operation of a first task identity of the at least one task identity, the first task identity is input in the first task node. The first task type is any task type of a plurality of task types, for example, the task type comprises a notification bar task type, an application icon task type, a home page recommended task type, a popup task type, a message center task type and the like. The method comprises the steps of displaying a notification bar task type through the notification bar, displaying an application icon task type in an icon of an application program to which the task belongs, recommending a task type in a front page of the application program to which the task belongs, displaying a popup task type in a popup form in the application program to which the task belongs, and displaying a message center task type in a message center of the application program to which the task belongs.

For example, referring to fig. 11, the first terminal displays a plurality of task types, after selecting a task type "notification bar task type", displays a plurality of task identifiers belonging to the task type, and then selects one task identifier from the plurality of task identifiers, and determines the task identifier as a first task identifier corresponding to the first task node.

Additionally, in one possible implementation, the task node may be deleted. And the first terminal responds to the deleting operation of any task node displayed in the task configuration interface, and deletes the task node and the subsequent task nodes of the task node. Optionally, each task node has a corresponding deletion control, and the task node and the subsequent task nodes of the task node are deleted in response to a trigger operation of the deletion control corresponding to any task node. When deleting a task node and a subsequent task node of the task node, triggering conditions between the task node and the subsequent task node are also deleted.

Optionally, the first terminal responds to the deletion operation of any task node displayed in the task configuration interface, and displays a confirmation deletion popup window, wherein the deletion popup window comprises a confirmation deletion control and a cancellation deletion control, and responds to the triggering operation of the confirmation deletion control, and the task node and the subsequent task nodes of the task node are deleted; and responding to the triggering operation of the cancel deletion control, canceling the task node and the subsequent task nodes of the task node. For example, referring to fig. 12, in response to the deletion operation of the second task node, a confirmation deletion popup prompting "whether to delete the current task node and 3 subsequent task nodes", in which case the 4 task nodes are deleted in the case of selection of "confirmation deletion", and in which case the task nodes are not deleted in the case of selection of "tentative".

In the above embodiment, the task node has a corresponding successor task node as an example, and in another embodiment, the task node is deleted when the task node does not have a corresponding successor task node.

In another possible implementation, since if the first task node is deleted, the entire task flow is deleted, and a new task flow needs to be re-established, in order to avoid establishing a new task flow, the first task node in the task flow does not have a corresponding deletion control, so as to ensure that the first task node cannot be deleted.

404. And the first terminal responds to the triggering operation of the adding control of the successor node corresponding to the first task node, and adds the successor task node of the first task node.

In the embodiment of the application, each task node is provided with a corresponding successor node adding control, and each successor node adding control is used for adding a successor task node for the corresponding task node. For example, referring to fig. 13, a successor task node 1302 is added in response to a trigger operation to a successor node add control 1301.

For the first task node, adding a subsequent task node corresponding to the first task node in response to a trigger operation of adding a control to the subsequent node; and then, responding to the re-triggering operation of adding the control to the subsequent node, and continuing to add another subsequent task node corresponding to the first task node, so that a plurality of subsequent task nodes corresponding to the first task node can be added through the repeated triggering operation of adding the control to the subsequent node.

405. The first terminal adds a trigger condition between a first task node and a subsequent task node of the first task node, and inputs a second task identifier corresponding to a second task in the subsequent task node of the first task node until a task flow comprising at least two task nodes corresponding to at least two tasks and the trigger condition between any two task nodes is obtained.

And adding a trigger condition between the first task node and the subsequent task node while adding the subsequent task node of the first task node, wherein the trigger condition indicates that the task corresponding to the subsequent task node is executed under the condition that the first task corresponding to the first task node meets the trigger condition.

In one possible implementation manner, a preset trigger condition is displayed between a first task node and a subsequent task node of the first task node; responding to the selection operation of the preset trigger conditions, and displaying a plurality of trigger conditions; in response to a selection operation of any one of the plurality of trigger conditions, replacing the preset trigger condition with the selected trigger condition. The triggering conditions include exposure, clicking, non-exposure and the like, wherein the exposure refers to displaying a first task corresponding to a first task node, the clicking refers to clicking the first task within a preset time period after displaying the first task, the non-clicking refers to not clicking the first task within the preset time period after displaying the first task, and the non-exposure refers to not displaying the first task.

For example, referring to fig. 14, a preset trigger condition "no click" is displayed first, and then a plurality of trigger conditions "exposure", "click", "no click", and "no exposure" are displayed in response to a selection operation of "no click".

The manner of inputting the second task identifier in the subsequent task node is the same as the manner of inputting the first task identifier in the first task node, and will not be described herein. After the second task identifier is input into the subsequent task node, the subsequent task node can be continuously added aiming at any displayed task identifier until a task flow comprising at least two task nodes corresponding to at least two tasks and trigger conditions between any two task nodes is obtained.

Note that, when a plurality of subsequent task nodes are added after the first task node, the trigger conditions between the plurality of subsequent task nodes and the first task node are different.

Another point to be described is that in the embodiment of the present application, the task identifier and the corresponding trigger condition in each task node can be modified during the process of creating the task flow.

406. The first terminal determines task configuration information of the target application program based on at least two tasks and task flows, wherein the task configuration information is used for indicating to display tasks according to the task flows.

After the first terminal creates and obtains at least two tasks and task flows, the task configuration information can be determined according to the task indicated by the task identifiers in the task flows and the task indicated by the task identifiers in the task flows, and the task configuration information comprises the task indicated by the task identifiers in the task flows and the task flows. When the terminal with the target application program is subsequently installed to display the task configuration information, the corresponding tasks are displayed according to the display sequence of the tasks indicated by the task flow.

407. The first terminal sends task configuration information to a server corresponding to the target application program, and the server is used for sending the task configuration information to the terminal so that the terminal displays the task according to the task flow.

After the first terminal configures the task configuration information, the task configuration information is sent to a server corresponding to the target application program, so that the server can send the task configuration information to the terminal provided with the target application program, and the terminal displays the task according to the task flow. The process of the server issuing task configuration information and displaying tasks on the terminal with the target application program is described in detail in the embodiments of fig. 15 and 16 below.

In the method provided by the embodiment of the application, in the task configuration process, the task and the task flow can be created through the task configuration interface of the target application program, the created at least two tasks are associated through the task node in the created task flow and the trigger condition between the former task node and the latter task node, the task configuration information is determined based on the at least two tasks and the task flow, the relevance between the tasks is improved, and the tasks in the task configuration information can be displayed subsequently based on the task flow in the task configuration information, so that the subsequently displayed tasks can be determined in real time based on the trigger condition in the task display process.

And by adding the task identifier in the task node, the task node is associated with the task, and only the task identifier is needed to be added, so that the task content of the whole task is not needed to be added, and the creation process is simple.

In addition, in order to facilitate the selection of task identifiers, the task types are selected firstly, then the required task identifiers are selected from the task identifiers belonging to the task types, the number of task identifiers to be selected can be reduced through the operation of determining the task types firstly, the selection of users is facilitated, and the efficiency of selecting the task identifiers is improved.

In addition, because the task identifier corresponding to the created task is needed in the process of creating the task flows, when a plurality of task flows are created, the task flows can adopt the same task identifier, and the task flows can be associated with the same task, namely, one task can be configured in the task configuration information, so that the utilization rate of the task is improved.

The embodiments of fig. 3 and fig. 4 described above introduce a task configuration procedure in which the first terminal transmits created task configuration information to the server, so that the server can issue the task configuration information, and the task issue procedure is described below by way of the embodiment shown in fig. 15.

Fig. 15 is a flowchart of a task publishing method according to an embodiment of the present application. The embodiment of the application is executed by a server. Referring to fig. 15, the method includes the steps of:

1501. the server obtains task configuration information.

The task configuration information acquired by the server is sent by the first terminal. The task configuration information is determined based on at least two tasks and a task flow, and is used for indicating to display the tasks according to the task flow, wherein the task flow comprises at least two task nodes corresponding to the at least two tasks and trigger conditions between any two task nodes, each two task nodes comprises a preceding task node and a subsequent task node, and the trigger conditions between the preceding task node and the subsequent task node indicate to execute the tasks corresponding to the subsequent task node under the condition that the tasks corresponding to the preceding task node meet the trigger conditions.

After the server acquires the task configuration information, the task configuration information is stored, so that the task can be conveniently issued based on the stored task configuration information.

1502. The server determines task configuration information matched with the trigger event based on the trigger event sent by the terminal, wherein the task configuration information is matched with the trigger event: the trigger event is a trigger event corresponding to a first task in the task configuration information, and the first task is a task corresponding to a first task node in the task configuration information.

1503. The server sends task configuration information matched with the trigger event to the terminal, and the terminal is used for displaying task content in at least one task according to task flow in the task configuration information.

In the embodiment of the application, the terminal is a terminal provided with a target application program corresponding to task configuration information, and the terminal is taken as a second terminal for example, the second terminal sends the trigger event to the server after detecting the trigger event, and the server determines matched task configuration information based on the trigger event and sends the matched task configuration information to the second terminal. The triggering event is an event detected by the second terminal, for example, the triggering event is a starting operation on a target application program, a switching operation on an interface in the target application program, a clicking operation on a control in the target application program, and the like.

The task configuration information comprises a plurality of tasks, wherein the tasks are displayed from the beginning when displayed, and then follow-up tasks corresponding to the trigger conditions are displayed according to whether the trigger conditions are met or not. Therefore, when determining whether the task configuration information is matched with the trigger event, determining whether the trigger event is a trigger event corresponding to the first task, and sending the task configuration information to the second terminal when the trigger event is the trigger event corresponding to the first task.

According to the method provided by the embodiment of the application, in the task release process, as the task flow associates a plurality of tasks, other tasks except the first task in the task flow can be continuously displayed under the condition that the first task is displayed, when determining which task configuration information is released, according to the characteristics of the task configuration information, only whether the trigger event corresponding to the first task in the task configuration information is consistent with the trigger event sent by the terminal is required to be determined, and the trigger event corresponding to each task is not required to be sequentially compared with the trigger event sent by the terminal, so that the release efficiency of the task configuration information is improved.

After the server issues the task configuration information to the terminal, the terminal can display the task based on the received task configuration information, and a task display process is described below through the embodiment of fig. 16.

Fig. 16 is a flowchart of a task display method according to an embodiment of the present application. The embodiment of the application is executed by the second terminal. Referring to fig. 16, the method includes the steps of:

1601. and the second terminal receives the task configuration information of the target application program.

Wherein the task configuration information is sent by the server. The task configuration information comprises at least two tasks and a task flow, wherein the task flow comprises at least two task nodes corresponding to the at least two tasks and trigger conditions between any two task nodes, each two task nodes comprise a preamble task node and a successor task node, and the trigger conditions between the preamble task node and the successor task node indicate that the task corresponding to the successor task node is executed under the condition that the task corresponding to the preamble task node meets the trigger conditions.

1602. And the second terminal displays task content in a first task according to the task flow, wherein the first task is a task corresponding to any task node in the task configuration information.

1603. And the second terminal displays task content in a second task corresponding to the target trigger condition when the first task meets any target trigger condition, wherein the target trigger condition is a trigger condition between the first task node corresponding to the first task and other task nodes in the task flow, and the second task is a task corresponding to a subsequent task node to which the target trigger condition belongs.

In the process of displaying the tasks based on the task configuration information, the second terminal starts to display from the first task in the task flow according to the task flow, and directly displays the task content in the first task when the first task is the first task, and displays the task content in the first task when the last task corresponding to the first task meets the target trigger condition, namely, the trigger condition between the task node corresponding to the first task and the front task node of the task node when the first task is not the first task.

After the second terminal displays the task content in the first task, the second terminal displays the task content in the second task when the first task meets any target trigger condition, and finishes displaying the task in the task configuration information when the first task does not meet any target trigger condition.

According to the method provided by the embodiment of the application, in the process of task display, task contents of tasks are sequentially displayed according to task flows in task configuration information, after a task is displayed, after the task meets the corresponding target trigger condition in the task flows, the subsequent tasks corresponding to the target trigger condition are continuously displayed, and the tasks to be displayed in the task configuration information are associated through the trigger condition among the tasks, so that the task is displayed according to the task flows, the association among the tasks is improved, the association among the tasks displayed in sequence is realized, and the display effect of the tasks is improved.

The embodiments of fig. 15 and 16 described above simply introduce a task issuing process and a task displaying process, respectively, in which interaction between the second terminal and the server is involved, and the task issuing process and the task displaying process are described in detail below through the embodiment shown in fig. 17.

Fig. 17 is a flowchart of a task display method according to an embodiment of the present application. The embodiment of the application is executed by the server and the second terminal. Referring to fig. 17, the method includes the steps of:

1701. the server obtains a plurality of task configuration information.

The server stores the plurality of task configuration information. The creation of the plurality of task configuration information is described in detail in the embodiment shown in fig. 4.

1702. The second terminal transmits a trigger event to the server in response to the trigger event detected based on the target application.

The triggering event is an event detected by the second terminal, for example, the triggering event is a starting operation on a target application program, a switching operation on an interface in the target application program, a clicking operation on a control in the target application program, and the like.

1703. The server determines and returns task configuration information matching the trigger event from among the plurality of task configuration information based on the trigger event.

In the embodiment of the application, the server stores the corresponding relation between the task and the release condition, wherein the release condition comprises at least one of the condition to be met by the terminal for receiving the task, the trigger event for indicating the release task, the condition to be met by the release object and the condition to be met by the release time. Therefore, the server can determine the task configuration information matched with the trigger event sent by the second terminal according to the trigger event sent by the second terminal and the trigger event corresponding to the first task in the task configuration information. In this case, matching task configuration information with a trigger event means: the trigger event is the trigger event corresponding to the first task in the task configuration information.

In one possible implementation, the server determines task configuration information matching the trigger event based on the trigger event and the terminal information sent by the second terminal. The terminal information refers to current attribute information of the terminal, and in this case, matching task configuration information with the trigger event refers to: the trigger event is a trigger event corresponding to a first task in the task configuration information, and the terminal information meets the release condition corresponding to the first task.

Optionally, the server first determines whether a trigger condition corresponding to a first task in the task configuration information is consistent with the trigger event, and if the trigger event corresponding to the first task is consistent with the trigger event, determines whether terminal information meets a terminal condition corresponding to the first task, and if the terminal information meets the terminal condition, determines that the task configuration information is matched with the trigger event.

In another possible implementation manner, the server determines task configuration information matched with the trigger event based on the trigger event sent by the second terminal and the current time point. In this case, matching task configuration information with a trigger event means: the trigger event is a trigger event corresponding to the first task in the task configuration information, and the current time point meets the condition that the release time corresponding to the first task needs to be met.

Optionally, the server first determines whether a trigger condition corresponding to a first task in the task configuration information is consistent with the trigger event, and if the trigger event corresponding to the first task is consistent with the trigger event, determines whether the release time meets a condition that the release time corresponding to the first task needs to be met, and if the release time meets a condition that the release time corresponding to the first task needs to be met, determines that the task configuration information is matched with the trigger event.

In another possible implementation manner, the server determines task configuration information matched with the trigger event based on the trigger event sent by the second terminal and the object account number of the login target application program. In this case, matching task configuration information with a trigger event means: the triggering event is a triggering event corresponding to a first task in the task configuration information, and the object account meets the condition that the release object corresponding to the first task needs to meet.

Optionally, the server first determines whether a trigger condition corresponding to a first task in the task configuration information is consistent with the trigger event, and if the trigger event corresponding to the first task is consistent with the trigger event, determines whether the object account meets a condition that a release object corresponding to the first task needs to be met, and if the object account meets a condition that a release object corresponding to the first task needs to be met, determines that the task configuration information is matched with the trigger event.

It should be noted that, in another embodiment, the above-described embodiments for determining the task configuration information of the trigger event matching can be combined with each other.

In one possible implementation manner, when the server determines that the plurality of task configuration information matched with the trigger event is determined by adopting the above embodiment, the server determines the priority of the first task in the plurality of task configuration information, and sends the task configuration information corresponding to the first task with the highest priority to the second terminal.

In the embodiment of the present application, the task configuration information that matches the trigger event is determined as an example, and in another embodiment, the server does not send the task configuration information to the second terminal when the task configuration information that matches the trigger event is not included in the plurality of task configuration information.

1704. And the server sends the task configuration information matched with the trigger event to the second terminal.

After the server determines the task configuration information, the task configuration information is sent to the second terminal. The task configuration information includes a task flow and a task, and the task includes a template identifier, but does not include a specific task template, so in one possible implementation manner, the server further stores the task template, and sends the task configuration information matched with the trigger event to the second terminal, where the task configuration information includes: determining a task template corresponding to the template identifier based on the template identifier in the task configuration information matched with the trigger event; and sending the task configuration information matched with the trigger event and the task template to the second terminal so that the second terminal displays the task content in the corresponding task according to the task template.

In one possible implementation, the server selects a target release channel from a plurality of release channels, and sends task configuration information matched with the trigger event to the terminal through the target release channel. The publishing channels comprise a first publishing channel, a second publishing channel and a third publishing channel, wherein the first publishing channel is used for publishing tasks based on the target application program, the second publishing channel is used for publishing tasks based on other application programs associated with the target application program, and the third publishing channel is used for publishing tasks based on an operating system of the terminal. Optionally, the server selects a release channel with the highest priority from the plurality of release channels as a target release channel according to the priority of each release channel; or, the server selects the publishing channel with the best communication state from the plurality of publishing channels as the target publishing channel according to the communication state of each publishing channel, and of course, other modes can be adopted to select the target publishing channel.

In one possible implementation manner, referring to the schematic diagram of the task display process shown in fig. 18, after the second terminal detects the trigger event, current terminal information is collected, the trigger event and the terminal information are sent to the server, the server screens task configuration information matched with the trigger event from multiple task configuration information, and the task display process is ended under the condition that the task configuration information matched with the trigger event is not screened; under the condition that the task configuration information matched with the trigger event is screened, the task configuration information matched with the trigger event and the release condition corresponding to the first task in the task configuration information matched with the trigger event are obtained, whether the terminal information meets the release condition is determined, under the condition that the terminal information also meets the release condition, the server sends the task configuration information matched with the trigger event to the second terminal, and under the condition that the terminal information does not meet the release condition, the task display process is ended.

In the embodiment of the present application, when the server sends the task configuration information to the second terminal, all tasks in the task configuration information are sent by the server as an example, in another embodiment, the server sends the task flow and the first task in the task configuration information to the second terminal, after the subsequent second terminal displays the first task and determines the task identifier corresponding to the next task based on the trigger condition, the second terminal sends the task identifier corresponding to the next task to the server, and the server sends the task corresponding to the task identifier to the second terminal based on the task identifier.

1705. And the second terminal displays the task content in the first task according to the task flow.

The first task is a task corresponding to any task node in the task configuration information.

In the case where the first task is the first task in the task flow: in one possible implementation manner, the second terminal obtains a first display number of the task content in the first task, where the first display number is a display number in a first reference duration before the current time point; and displaying the task content when the first display times do not exceed the first time number threshold. The first reference time period is any preset time period, for example, the first reference time period is 1 day, 2 days or other time periods, the first time threshold value is any preset value, for example, the first time threshold value is 5 times, 10 times or other values.

In another possible implementation manner, the second terminal obtains a second display frequency, where the second display frequency is a total frequency of task contents displayed in a second reference time period before the current time point; and displaying the task content under the condition that the second display times do not exceed the second time threshold. The second reference time period is any preset time period, for example, the second reference time period is 1 day, 2 days or other time periods, the second time threshold is any preset value, for example, the second time threshold is 5 times, 10 times or other values.

In order to avoid excessive display times of task content, the embodiment of the application needs to display the task content in the first task only when the display times of the task content are less, namely, when the first display times do not exceed the first time threshold or when the second display times do not exceed the second time threshold.

In a possible implementation manner, under the condition that the first task is any task, if a trigger event meeting any target trigger condition is not detected within a first time period after the display of the task content, the display of the task content is canceled; after the second period of time has elapsed after the display of the task content is canceled, the task content is displayed again. By the mode of displaying the task content for multiple times, the object is easier to trigger the task, and therefore task conversion is achieved.

In one possible implementation manner, under the condition that the second terminal receives the plurality of task configuration information, determining task configuration information with highest priority of the plurality of task configuration information; and displaying task content in the first task according to the task flow of the task configuration information with the highest priority, wherein the first task is any task in the task configuration information with the highest priority.

1706. And the second terminal displays the task content in the second task corresponding to the target trigger condition under the condition that the first task meets the target trigger condition until the task content in the last task in the task configuration information is displayed, or the current task does not meet any target trigger condition.

After the second terminal displays the task content in the first task, detecting a first trigger event executed on the task content, and displaying the task content in the second task corresponding to the target trigger condition under the condition that the first trigger event meets any target trigger condition. Since the trigger conditions between the task node corresponding to the first task and the plurality of subsequent task nodes are different, one second task meeting the conditions or a second task not meeting the conditions can be determined each time.

When each task in the task configuration information is displayed, a task template indicated by a template identification in the task can be displayed. For example, if the task template is displayed in a popup form in the application program, the task content in the task is displayed in a popup form, and the task content needs to be displayed in the task template according to the display position indicated by the template style in the task template.

In one possible implementation, referring to the task display procedure shown in fig. 19, a task object is initially set, which refers to displaying task content in the last task in the task configuration information. The method comprises the steps of triggering a task 1, namely a first task, in task configuration information, triggering a task 2 when the task 1 is converted, namely when the task 1 meets any target triggering condition, and displaying the task 1 again after a certain time interval when the task 1 is closed or ignored, namely when the task 1 does not meet any target triggering condition, wherein when the task 1 is closed, the task 1 is displayed again after waiting for a first interval, and when the task 1 is ignored, the task 1 is displayed again after waiting for a second interval. The same applies to the subsequent task 2 and the task n until the task content in the last task in the task configuration information is displayed.

Taking "robbery package" as an example, referring to the task display process shown in fig. 20, an interface 2001 is displayed first, a "new spring robbery package push" is displayed in the interface 2001, a click operation on the "new spring robbery package push" is responded, an interface 2002 is displayed in the interface 2002, a "robbery alarm clock" is displayed in the interface 2002, in the case that the "new spring robbery package push" is not clicked, an application icon corresponding to a mobile phone manager application program is replaced with a robbery package style in the interface 2003, in the case that the icon replacement is successful, a first page layout of the mobile phone manager application program is replaced with a new spring robbery package style in response to a starting operation on the mobile phone manager application program, an interface 2005 is displayed, a popup window of the first page is displayed, in response to the click operation on the popup window, an interface 2006 is displayed in the case that the popup window is not clicked, an unread message center of the mobile phone manager application program is pushed with a robbery message in the interface 2003, in response to the click operation on the interface 2007, and in response to the click operation on the interface 2007.

In addition, compared with the situation that a single task is displayed in the prior art and the tasks are not associated with each other, the task display mode provided by the embodiment of the application has the advantages that the exposure rate of the task is improved by 42%, the click rate of the task is improved by 91%, the negative feedback rate of the task is improved by 17%, and the exposure rate and the click rate are greatly improved under the condition that the negative feedback rate is not obviously improved, so that the display effect is effectively improved.

In the above embodiment, the task configuration process, the task release process, and the task display process are described separately, and all of these processes belong to the task management process, and the task management process is described below.

Fig. 21 is a flowchart of a task management method according to an embodiment of the present application. The embodiment of the application is executed by the first terminal, the server and the second terminal. Referring to fig. 21, the method includes the steps of:

2101. the first terminal creates at least two tasks and task flows of the target application program based on a task configuration interface corresponding to the target application program, wherein the task flows comprise at least two task nodes corresponding to the at least two tasks and trigger conditions between any two task nodes, each two task nodes comprise a preamble task node and a successor task node, and the trigger conditions between the preamble task node and the successor task node indicate that the task corresponding to the successor task node is executed under the condition that the task corresponding to the preamble task node meets the trigger conditions.

2102. The first terminal determines task configuration information of a target application program based on at least two tasks and task flows, and sends the task configuration information to the server, wherein the task configuration information is used for indicating to display tasks according to the task flows.

The implementation of steps 2101-2102 is the same as the implementation in the embodiments shown in fig. 3 and 4 and is not described in detail herein.

2103. The server determines task configuration information matched with the trigger event from a plurality of task configuration information based on the trigger event sent by the second terminal, and sends the task configuration information to the second terminal, wherein the task configuration information is matched with the trigger event: the trigger event is a trigger event corresponding to a first task in the task configuration information, and the first task is a task corresponding to a first task node in the task configuration information.

The implementation of step 2103 is the same as the implementation in the embodiment shown in fig. 15 and 17 and is not described here again.

2104. And the second terminal displays task content in at least one task according to the task flow in the task configuration information.

The implementation of step 2104 is the same as the implementation in the embodiment shown in fig. 16 and 17 and is not described here again.

The method provided by the embodiment of the application comprises the steps that a first terminal configures tasks, a task configuration interface is used for creating tasks and task flows, at least two tasks which are created are associated through the task nodes in the task flows and trigger conditions between the former task nodes and the latter task nodes, task configuration information is determined based on the at least two tasks and the task flows, the task configuration information is sent to a server, then the server sends the task configuration information to a second terminal after receiving a trigger event which is sent by the second terminal and is matched with the task configuration information, and the second terminal can display task content in at least one task according to the task flows in the task configuration information. In the whole task management process, each task is firstly associated through a task flow when the task is configured, so that the association between each task is improved, then when the task is issued, the association between each task displayed in sequence is considered, and the display effect of the task is improved by only determining whether the trigger event corresponding to the first task in the task configuration information is consistent with the received trigger event and not carrying out the corresponding operation on each task in the task configuration information, so that the issuing efficiency of the task configuration information is improved, and finally, when the task is displayed, the tasks are displayed according to the task flow, so that the association between each task displayed in sequence is improved.

In addition, in the task management process (operation process) provided by the embodiment of the application, the task management is realized through the mutual cooperation of the first terminal, the second terminal and the server, and the different devices realize the respective functions.

In one possible implementation, referring to fig. 22, the target application program interacts with the server based on a UI (User Interface) component, a persistence component, a core control component, an API (Application Programming Interface, application program Interface) component, and a service agent module to implement a task display process. The UI component comprises an intelligent combination display module, a UI communication module, a right management module and a customized UI module, wherein the intelligent combination display module is used for displaying a UI, the UI communication module is used for determining the communication mode of the UI and other devices or other modules, the right management module is used for managing the right of the UI, and the customized UI module is used for managing the customized specific UI. The persistence component comprises a terminal environment module, a configuration management module and a reporting management module, wherein the terminal environment module is used for detecting terminal environment information in real time, the configuration management module is used for managing the current configuration of the terminal, and the reporting management module is used for managing information reported to the server. The core control component comprises a logic control module and a network control module, wherein the logic control module is used for determining the operation logic of the terminal, and the network control module is used for managing the network state of the terminal. The API component comprises a service processing module, a data service module and a triggering module, wherein the service processing module is used for processing actual service, the data service module is used for managing data generated in the application running process and acquiring data from other devices, and the triggering module is used for detecting triggering events. The service agent module is used for determining a release channel adopted when the server issues the task.

In another possible implementation, referring to fig. 23, the second terminal includes a trigger management module, a data service module, a task processing module, and an interface display module. The trigger management module detects a trigger event, and after the trigger event is detected, the general policy configuration of the application program is executed to acquire relevant data such as service parameters, terminal information and the like required by communication with the server; and then, sending a trigger event and related data to the server through the data service module, receiving task configuration information issued by the server, determining whether to immediately display the task content through the task processing module according to the display condition of the current task content after receiving the task configuration information issued by the server, and acquiring the display times, the display time and the like of the task content in the second terminal. And after the task processing module determines to display the task content, displaying the task content through the interface display module. Of course, in one possible implementation, the server is also capable of periodically acquiring, through the data service module, the trigger event or related data of the second terminal.

Fig. 24 is a schematic structural diagram of a task configuration device according to an embodiment of the present application. Referring to fig. 24, the apparatus includes:

The interface display module 2401 is used for displaying a task configuration interface corresponding to the target application program;

a task creation module 2402 for creating at least two tasks of the target application based on the task configuration interface;

a process creation module 2403, configured to create a task process based on the task configuration interface, where the task process includes at least two task nodes corresponding to the at least two tasks and a trigger condition between any two task nodes, where each two task nodes includes a preceding task node and a subsequent task node, where the trigger condition between the preceding task node and the subsequent task node indicates that, when the task corresponding to the preceding task node meets the trigger condition, the task corresponding to the subsequent task node is executed;

the configuration information determining module 2404 is configured to determine task configuration information of the target application program based on the at least two tasks and the task flow, where the task configuration information is used to indicate that the tasks are displayed according to the task flow.

In the device provided by the embodiment of the application, in the task configuration process, the task and the task flow can be created through the task configuration interface of the target application program, the created at least two tasks are associated through the task node in the created task flow and the trigger condition between the former task node and the latter task node, the task configuration information is determined based on the at least two tasks and the task flow, the relevance between the tasks is improved, and the tasks in the task configuration information can be displayed subsequently based on the task flow in the task configuration information, so that the subsequently displayed tasks can be determined in real time based on the trigger condition in the task display process.

In one possible implementation manner, the task corresponding to the task node is a task indicated by a task identifier included in the task node, and the process creation module 2403 includes:

the task configuration interface comprises an identification input unit, a task configuration interface and a task configuration interface, wherein the identification input unit is used for inputting a first task identification corresponding to a first task in a first task node in the task configuration interface, and the first task node is any one of the task nodes displayed in the task configuration interface;

the node adding unit is used for responding to the triggering operation of the subsequent node adding control corresponding to the first task node and adding the subsequent task node of the first task node;

In another possible implementation, the identification input unit is configured to:

inputting a first task type in the first task node;

the first task identity is entered in the first task node in response to a selection operation of the first task identity of the at least one task identity.

displaying a preset triggering condition between the first task node and a subsequent task node of the first task node;

and in response to a selection operation of any one of the plurality of trigger conditions, replacing the preset trigger condition with the selected trigger condition.

In another possible implementation, the apparatus further includes:

In another possible implementation, the task creation module 2402 is configured to:

creating a task based on the template identification and the task content;

Displaying a template configuration interface;

creating the task template based on the template identification, the template style, and the display form;

the template style comprises at least one category and a display position corresponding to each category, the template style is used for determining that task content belonging to the category is filled in the display position in the task template, and the display form is used for determining the display position of the task template on the terminal when the terminal displays the task content according to the task template.

In another possible implementation, the apparatus further includes:

the issuing condition acquisition module is used for acquiring issuing conditions input in the task configuration interface, establishing a corresponding relation between the task and the issuing conditions, and indicating conditions which need to be met when task configuration information taking the task as a first task is issued, wherein the first task is a task corresponding to a first task node in the task configuration information;

In another possible implementation, the apparatus further includes:

the configuration information sending module is used for sending the task configuration information to a server corresponding to the target application program, and the server is used for sending the task configuration information to the terminal so that the terminal displays the task according to the task flow.

Any combination of the above optional solutions may be adopted to form an optional embodiment of the present application, which is not described herein.

It should be noted that: in the task configuration device provided in the above embodiment, when configuring tasks, only the division of the above functional modules is used for illustration, in practical application, the above functional allocation may be completed by different functional modules according to needs, that is, the internal structure of the terminal is divided into different functional modules, so as to complete all or part of the functions described above. In addition, the task configuration device and the task configuration method provided in the foregoing embodiments belong to the same concept, and detailed implementation processes of the task configuration device and the task configuration method are detailed in the method embodiments, which are not repeated herein.

Fig. 25 is a schematic structural diagram of a task display device according to an embodiment of the present application. Referring to fig. 25, the apparatus includes:

a configuration information receiving module 2501, configured to receive task configuration information of a target application, where the task configuration information includes at least two tasks and a task flow, the task flow includes at least two task nodes corresponding to the at least two tasks and a trigger condition between any two task nodes, each two task nodes includes a preceding task node and a subsequent task node, and the trigger condition between the preceding task node and the subsequent task node indicates that, when a task corresponding to the preceding task node meets the trigger condition, a task corresponding to the subsequent task node is executed;

the task display module 2502 is configured to display task content in a first task according to the task flow, where the first task is a task corresponding to any task node in the task configuration information;

the task display module 2502 is further configured to display task content in a second task corresponding to a target trigger condition when the first task meets the target trigger condition, where the target trigger condition is a trigger condition between a first task node corresponding to the first task and other task nodes in the task flow, and the second task is a task corresponding to a subsequent task node to which the target trigger condition belongs.

According to the device provided by the embodiment of the application, in the process of task display, task contents of tasks are sequentially displayed according to the task flow in the task configuration information, after a task is displayed, when the task meets the corresponding target trigger condition in the task flow, the subsequent tasks corresponding to the target trigger condition are continuously displayed, and the tasks to be displayed in the task configuration information are associated through the trigger condition among the tasks, so that the task is displayed according to the task flow, the association among the tasks is improved, the association among the tasks displayed in sequence is realized, and the display effect of the tasks is improved.

In one possible implementation, the configuration information receiving module 2501 includes:

the trigger event sending unit is used for responding to the trigger event detected by the target application program and sending the trigger event to a server corresponding to the target application program, and the server is used for determining and returning task configuration information matched with the trigger event from a plurality of task configuration information based on the trigger event;

wherein, the matching of the task configuration information and the trigger event means that: the trigger event is a trigger event corresponding to a first task in the task configuration information, and the first task is a task corresponding to a first task node in the task configuration information.

wherein, the matching of the task configuration information and the trigger event means that: the triggering event is a triggering event corresponding to the first task, and the terminal information meets the release condition corresponding to the first task.

In another possible implementation, the task display module 2502 is further configured to:

under the condition that the trigger event meeting any target trigger condition is not detected in a first time period after the task content is displayed, canceling to display the task content;

after a second period of time has elapsed after the display of the task content is canceled, the task content is displayed again.

In another possible implementation, the task display module 2502 is configured to:

and displaying the task content when the first display times do not exceed the first time number threshold.

and displaying the task content when the second display times do not exceed a second time threshold.

It should be noted that: in the task display device provided in the above embodiment, when displaying tasks, only the division of the above functional modules is used for illustration, in practical application, the above functional allocation may be completed by different functional modules according to needs, that is, the internal structure of the terminal is divided into different functional modules, so as to complete all or part of the functions described above. In addition, the task display device and the task display method embodiment provided in the foregoing embodiments belong to the same concept, and detailed implementation processes of the task display device and the task display method embodiment are detailed in the method embodiment, which is not repeated herein.

Fig. 26 is a schematic structural diagram of a task issuing device according to an embodiment of the present application. Referring to fig. 26, the apparatus includes:

the configuration information obtaining module 2601 is configured to obtain task configuration information, where the task configuration information is determined based on at least two tasks and a task flow, and is used to issue a task according to the task flow, where the task flow includes at least two task nodes corresponding to the at least two tasks and a trigger condition between any two task nodes, where each two task nodes includes a preceding task node and a subsequent task node, and the trigger condition between the preceding task node and the subsequent task node indicates that, when a task corresponding to the preceding task node meets the trigger condition, a task corresponding to the subsequent task node is executed;

the configuration information matching module 2602 is configured to determine, based on a trigger event sent by the terminal, task configuration information that matches the trigger event, where the task configuration information matches the trigger event is: the trigger event is a trigger event corresponding to a first task in the task configuration information, and the first task is a task corresponding to a first task node in the task configuration information;

the configuration information sending module 2603 is configured to send task configuration information matched with the trigger event to the terminal, where the terminal is configured to display task content in at least one task according to a task flow in the task configuration information.

In the device provided by the embodiment of the application, in the process of issuing the task, because the task flow associates a plurality of tasks, other tasks except the first task in the task flow can be continuously displayed under the condition that the first task is displayed, when determining which task configuration information is issued, according to the characteristics of the task configuration information, only whether the trigger event corresponding to the first task in the task configuration information is consistent with the trigger event sent by the terminal is required to be determined, and the trigger event corresponding to each task is not required to be sequentially compared with the trigger event sent by the terminal, thereby improving the issuing efficiency of the task configuration information.

In one possible implementation, the apparatus further includes:

the corresponding relation acquisition module is used for acquiring a corresponding relation between a task and a release condition, wherein the release condition comprises at least one of a condition to be met by a terminal for receiving the task, a trigger event for indicating release of the task, a condition to be met by a release object and a condition to be met by release time;

the configuration information matching module 2602 is configured to determine task configuration information that matches the trigger event based on the trigger event and the terminal information sent by the terminal, where the task configuration information matches the trigger event refers to: the triggering event is a triggering event corresponding to the first task, and the terminal information meets the release condition corresponding to the first task.

the system comprises a template acquisition module, a template display module and a display module, wherein the template acquisition module is used for acquiring a task template, the task template is created based on a template identifier, a template pattern and a display form, the template pattern comprises at least one category and a display position corresponding to each category, the template pattern is used for determining that task content belonging to the category is filled in the display position in the task template, and the display form is used for determining the display position of the task template on a terminal when the terminal displays the task content according to the task template;

the configuration information sending module 2603 is configured to:

In another possible implementation manner, the configuration information sending module 2603 is configured to:

It should be noted that: the task issuing device provided in the above embodiment only illustrates the division of the above functional modules when issuing tasks, and in practical application, the above functional allocation may be completed by different functional modules according to needs, that is, the internal structure of the server is divided into different functional modules to complete all or part of the functions described above. In addition, the task issuing device and the task issuing method provided in the foregoing embodiments belong to the same concept, and detailed implementation processes of the task issuing device and the task issuing method are detailed in the method embodiments and are not repeated here.

The embodiment of the application also provides a terminal, which comprises a processor and a memory, wherein at least one computer program is stored in the memory, and the at least one computer program is loaded and executed by the processor to realize the operation executed by the task configuration method or the task display method in the embodiment.

Fig. 27 is a schematic structural diagram of a terminal 2700 according to an embodiment of the present application. Terminal 2700 includes: a processor 2701 and a memory 2702.

Processor 2701 may include one or more processing cores, such as a 4-core processor, an 8-core processor, and the like. The processor 2701 may be implemented in at least one hardware form of DSP (Digital Signal Processing ), FPGA (Field-Programmable Gate Array, field programmable gate array), PLA (Programmable Logic Array ). The processor 2701 may also include a main processor, which is a processor for processing data in the awake state, also referred to as a CPU (Central Processing Unit ), and a coprocessor; a coprocessor is a low-power processor for processing data in a standby state. In some embodiments, the processor 2701 may integrate a GPU (Graphics Processing Unit, image processor) for taking care of rendering and drawing of content that the display screen is required to display. In some embodiments, the processor 2701 may also include an AI (Artificial Intelligence ) processor for processing computing operations related to machine learning.

Memory 2702 may include one or more computer-readable storage media, which may be non-transitory. Memory 2702 may also include high speed random access memory, as well as non-volatile memory, such as one or more magnetic disk storage devices, flash memory storage devices. In some embodiments, a non-transitory computer readable storage medium in memory 2702 is used to store at least one computer program for execution by processor 2701 to implement the task configuration method or the task display method provided by the method embodiments of the present application.

In some embodiments, terminal 2700 may optionally further include: peripheral interface 2703 and at least one peripheral. The processor 2701, the memory 2702, and the peripheral interface 2703 may be connected by a bus or signal lines. Individual peripheral devices may be connected to peripheral device interface 2703 by buses, signal lines or circuit boards. Specifically, the peripheral device includes: at least one of radio frequency circuit 2704, display 2705, camera assembly 2706, audio circuit 2707, and power supply 2708.

Peripheral interface 2703 may be used to connect at least one Input/Output (I/O) related peripheral device to processor 2701 and memory 2702. In some embodiments, processor 2701, memory 2702, and peripheral interface 2703 are integrated on the same chip or circuit board; in some other embodiments, any one or both of the processor 2701, the memory 2702, and the peripheral interface 2703 may be implemented on a separate chip or circuit board, which is not limited in this embodiment.

The Radio Frequency circuit 2704 is configured to receive and transmit RF (Radio Frequency) signals, also referred to as electromagnetic signals. The radio frequency circuit 2704 communicates with a communication network and other communication devices via electromagnetic signals. The radio frequency circuit 2704 converts an electrical signal into an electromagnetic signal for transmission, or converts a received electromagnetic signal into an electrical signal. Optionally, the radio frequency circuit 2704 includes: antenna systems, RF transceivers, one or more amplifiers, tuners, oscillators, digital signal processors, codec chipsets, subscriber identity module cards, and so forth. The radio frequency circuit 2704 may communicate with other terminals via at least one wireless communication protocol. The wireless communication protocol includes, but is not limited to: the world wide web, metropolitan area networks, intranets, generation mobile communication networks (2G, 3G, 4G, and 5G), wireless local area networks, and/or WiFi (Wireless Fidelity ) networks. In some embodiments, the radio frequency circuit 2704 may also include NFC (Near Field Communication ) related circuitry, which is not limiting of the application.

The display 2705 is used to display a UI (User Interface). The UI may include graphics, text, icons, video, and any combination thereof. When display 2705 is a touch display, display 2705 also has the ability to collect touch signals at or above the surface of display 2705. The touch signal may be input as a control signal to the processor 2701 for processing. At this point, the display 2705 may also be used to provide virtual buttons and/or virtual keyboards, also referred to as soft buttons and/or soft keyboards. In some embodiments, the display 2705 may be one, disposed on the front panel of the terminal 2700; in other embodiments, the display 2705 may be at least two, disposed on different surfaces of the terminal 2700 or in a folded design; in other embodiments, the display 2705 may be a flexible display disposed on a curved surface or a folded surface of the terminal 2700.

The camera assembly 2706 is used to capture images or video. Optionally, camera assembly 2706 includes a front camera and a rear camera. The front camera is arranged on the front panel of the terminal, and the rear camera is arranged on the back of the terminal. In some embodiments, the at least two rear cameras are any one of a main camera, a depth camera, a wide-angle camera and a tele camera, so as to realize that the main camera and the depth camera are fused to realize a background blurring function, and the main camera and the wide-angle camera are fused to realize a panoramic shooting and Virtual Reality (VR) shooting function or other fusion shooting functions.

Audio circuit 2707 may include a microphone and a speaker. The microphone is used for collecting sound waves of users and the environment, converting the sound waves into electric signals, and inputting the electric signals to the processor 2701 for processing, or inputting the electric signals to the radio frequency circuit 2704 for realizing voice communication.

The power supply 2708 is used to supply power to the various components in the terminal 2700. The power supply 2708 may be an alternating current, a direct current, a disposable battery, or a rechargeable battery. When power supply 2708 includes a rechargeable battery, the rechargeable battery may be a wired rechargeable battery or a wireless rechargeable battery.

It will be appreciated by those skilled in the art that the structure shown in fig. 27 is not limiting of the terminal 2700 and may include more or fewer components than shown, or may combine certain components, or may employ a different arrangement of components.

The embodiment of the application also provides a server, which comprises a processor and a memory, wherein at least one computer program is stored in the memory, and the at least one computer program is loaded and executed by the processor to realize the operation executed by the task issuing method of the embodiment.

Fig. 28 is a schematic structural diagram of a server provided in an embodiment of the present application, where the server 2800 may have a relatively large difference due to different configurations or performances, and may include one or more processors (Central Processing Units, CPU) 2801 and one or more memories 2802, where the memory 2802 stores at least one computer program, and the at least one computer program is loaded and executed by the processor 2801 to implement the methods provided in the foregoing method embodiments. Of course, the server may also have a wired or wireless network interface, a keyboard, an input/output interface, and other components for implementing the functions of the device, which are not described herein.

The embodiment of the application also provides a computer readable storage medium, wherein at least one computer program is stored in the computer readable storage medium, and the at least one computer program is loaded and executed by a processor to realize the operation executed by the task configuration method, the task display method or the task release method in the embodiment.

The embodiment of the application also provides a computer program product, which comprises a computer program, and the computer program realizes the operations executed by the task configuration method, the task display method or the task release method of the embodiment when being executed by a processor.

In some embodiments, a computer program according to an embodiment of the present application may be deployed to be executed on one computer device or on multiple computer devices located at one site, or on multiple computer devices distributed across multiple sites and interconnected by a communication network, where the multiple computer devices distributed across multiple sites and interconnected by a communication network may constitute a blockchain system.

It will be understood by those skilled in the art that all or part of the steps for implementing the above embodiments may be implemented by hardware, or may be implemented by a program for instructing relevant hardware, where the program may be stored in a computer readable storage medium, and the above storage medium may be a read-only memory, a magnetic disk or an optical disk, etc.

The foregoing is merely an alternative embodiment of the present application and is not intended to limit the embodiment of the present application, and any modifications, equivalent substitutions, improvements, etc. made within the spirit and principle of the embodiment of the present application should be included in the protection scope of the present application.

Claims

1. A method of task management, the method performed by a task management system comprising a first terminal, a server, and a second terminal, the method comprising:

2. The method of claim 1, wherein the task corresponding to the task node is a task indicated by a task identifier included in the task node, and the first terminal creates a task flow based on a task configuration interface corresponding to a target application program, including:

the first terminal inputs a first task identifier corresponding to a first task in a first task node in the task configuration interface, wherein the first task node is any task node displayed in the task configuration interface;

the first terminal responds to the triggering operation of adding a control to a successor node corresponding to the first task node, and adds the successor task node of the first task node;

The first terminal adds a triggering condition between the first task node and a subsequent task node of the first task node;

and the first terminal inputs a second task identifier corresponding to a second task in a subsequent task node of the first task node.

3. The method of claim 2, wherein the first terminal inputs a first task identifier corresponding to a first task in a first task node in the task configuration interface, and the method comprises:

the first terminal inputs a first task type in the first task node;

the first terminal displays a task identifier corresponding to at least one task belonging to the first task type;

the first terminal responds to the selection operation of the first task identifier in at least one task identifier, and inputs the first task identifier in the first task node.

4. The method according to claim 2, wherein the first terminal adds a trigger condition between the first task node and a subsequent task node of the first task node, comprising:

the first terminal displays a preset trigger condition between the first task node and a subsequent task node of the first task node;

The first terminal responds to the selection operation of the preset trigger conditions and displays a plurality of trigger conditions;

and the first terminal responds to the selection operation of any trigger condition in the plurality of trigger conditions, and replaces the preset trigger condition with the selected trigger condition.

5. The method according to claim 1, wherein the method further comprises:

and the first terminal responds to the deleting operation of any task node displayed in the task configuration interface, and deletes the task node and the subsequent task nodes of the task node.

6. The method according to any of claims 1-5, wherein the first terminal creating at least two tasks of the target application based on the task configuration interface comprises:

the first terminal acquires a template identifier and task content input in the task configuration interface;

the first terminal creates a task based on the template identification and the task content;

7. The method of claim 6, wherein before the first terminal obtains the template identifier and the task content input in the task configuration interface, the method further comprises:

the first terminal displays a template configuration interface;

the first terminal obtains an input template identifier, a template style and a display form based on the template configuration interface;

the first terminal creates the task template based on the template identifier, the template style and the display form, and sends the task template to the server; the template style comprises at least one category and a display position corresponding to each category, the template style is used for determining that task contents belonging to the category are filled in the display position in the task template, and the display form is used for determining the display position of the task template on a second terminal when the second terminal displays the task contents according to the task template;

the server sends the task configuration information to the second terminal, including:

and the server sends the task configuration information and a task template corresponding to the task in the task configuration information to the second terminal.

8. The method of claim 6, wherein after the first terminal creates a task based on the template identification and the task content, the method further comprises:

the first terminal acquires a release condition input in the task configuration interface, and establishes a corresponding relation between the task and the release condition, wherein the release condition indicates a condition which needs to be met when task configuration information taking the task as a first task is released, and the first task is a task corresponding to a first task node in the task configuration information;

the first terminal sends the corresponding relation between the task and the release condition to the server;

9. The method of claim 1, wherein the server determining task configuration information matching the trigger event based on the trigger event sent by the second terminal comprises:

the second terminal sends the trigger event and the terminal information of the second terminal to the server;

The server determines and returns task configuration information matched with the trigger event and the terminal information from the plurality of task configuration information based on the trigger event; wherein, the matching of the task configuration information with the trigger event means that: the triggering event is a triggering event corresponding to the first task, and the terminal information meets the release condition corresponding to the first task.

10. The method of claim 1, wherein the second terminal displays task content in at least one task according to a task flow in the task configuration information, including:

the second terminal displays task content in a first task according to a task flow in the task configuration information, wherein the first task is a task corresponding to any task node in the task configuration information;

and the second terminal displays task content in a second task corresponding to a target trigger condition when the first task meets the target trigger condition, wherein the target trigger condition is a trigger condition between a first task node corresponding to the first task and other task nodes in the task flow, and the second task is a task corresponding to a subsequent task node to which the target trigger condition belongs.

11. A method of task configuration, the method comprising:

12. A method of task display, the method comprising:

13. A method of task publication, the method comprising:

14. A task configuration device, the device comprising:

15. A task display device, the device comprising:

16. A task issuing apparatus, characterized in that the apparatus comprises:

17. A terminal comprising a processor and a memory, wherein the memory stores at least one computer program that is loaded and executed by the processor to implement the operations performed by the task configuration method of claim 11 or to implement the operations performed by the task display method of claim 12.

18. A server comprising a processor and a memory, wherein the memory stores at least one computer program that is loaded and executed by the processor to perform the operations performed by the task issuing method of claim 13.

19. A computer-readable storage medium, in which at least one computer program is stored, the at least one computer program being loaded and executed by a processor to implement the operations performed by the task configuration method of claim 11, or to implement the operations performed by the task display method of claim 12, or to implement the operations performed by the task distribution method of claim 13.

20. A computer program product comprising a computer program which, when executed by a processor, implements the operations performed by the task allocation method of claim 11, or the operations performed by the task display method of claim 12, or the operations performed by the task distribution method of claim 13.