Task data processing method and device, storage medium and electronic equipment

Abstract

The invention discloses a task data processing method and device, a storage medium and electronic equipment. The method comprises the steps that a first task event set and a first task set are obtained, a mapping relation is preset between one task event in the first task event set and at least one task in the first task set, and under the condition that a trigger task event list comprises a target task event, the task event list comprises the target task event; according to the target task event, through the first task event set and the first task set, searching for a target task, and determining a matching state of the target task, the matching state being used for representing whether the task events having the mapping relationship with the target task are all triggered, and under the condition that the task events having the mapping relationship with the target task are all triggered, determining the completion state of the target task according to the task condition parameters of the target task and the task event parameters of the target task events. The technical problem that the task data processing efficiency is low in the prior art is solved.

Description

Technical Field

[0001] The present application relates to the field of computers, and in particular to a method and device for processing task data, a storage medium, and an electronic device. Background Art

[0002] In the prior art, when a task event is triggered, it is necessary to traverse each task to determine whether each task is completed. Since tasks that are not related to the triggered task event will be traversed, and traversing such tasks is essentially invalid, it increases the consumption of system computing resources. In addition, as more and more tasks are under development, more and more task conditions need to be traversed each time an event is triggered, and more and more invalid task conditions will be present, and the system calculation will become heavier and heavier.

[0003] That is, there is a technical problem in the related technology that the processing efficiency of task data is low.

[0004] To address the above-mentioned problems, no effective solution has been proposed yet. Summary of the invention

[0005] The embodiments of the present application provide a method and device for processing task data, a storage medium, and an electronic device, so as to at least solve the technical problem of low task data processing efficiency in the related art.

[0006] According to one aspect of an embodiment of the present application, a method for processing task data is provided, including: acquiring a first task event set and a first task set, wherein a task event in the first task event set is pre-set with a mapping relationship with at least one task in the first task set; in a case where a triggering task event list includes a target task event, searching for a target task through the first task event set and the first task set according to the target task event, and determining a matching status of the target task, wherein the target task event has the mapping relationship with the target task, the triggering task event list includes currently triggered task events, and the matching status is used to indicate whether all task events having the mapping relationship with the target task have been triggered; in a case where all task events having the mapping relationship with the target task have been triggered, determining a completion status of the target task according to task condition parameters of the target task and task event parameters of the target task event.

[0007] According to another aspect of an embodiment of the present application, a task data processing device is also provided, including: an acquisition module, used to acquire a first task event set and a first task set, wherein a task event in the first task event set is pre-set with a mapping relationship with at least one task in the first task set; a search module, used to search for a target task through the first task event set and the first task set according to the target task event when a triggering task event list includes a target task event, and determine a matching status of the target task, wherein the target task event has the mapping relationship with the target task, the triggering task event list includes currently triggered task events, and the matching status is used to indicate whether all task events having the mapping relationship with the target task have been triggered; a determination module, used to determine the completion status of the target task according to the task condition parameters of the target task and the task event parameters of the target task event when all task events having the mapping relationship with the target task have been triggered.

[0008] Optionally, the device is used to search for the target task through the first task event set and the first task set according to the target task event and determine the matching status of the target task in the following manner when the triggering task event list includes the target task event: determine the target statistical parameters of the target task according to the first task event set and the first task set, wherein the target statistical parameters are used to represent the total number of task events having the mapping relationship with the target task; determine the target counting parameters of the target task when the triggering task event list includes the target task event, wherein the target counting parameters are used to represent the number of the target task events; determine the matching status of the target task according to the target statistical parameters and the target counting parameters.

[0009] Optionally, the device is used to determine the matching status of the target task according to the target statistical parameter and the target counting parameter in the following manner: when the values ​​of the target statistical parameter and the target counting parameter are the same, the matching status of the target task is determined as all task events having the mapping relationship with the target task have been triggered; when the value of the target counting parameter is less than the target statistical parameter, the matching status of the target task is determined as there are untriggered task events having the mapping relationship with the target task.

[0010] Optionally, the device is used to determine the matching state of the target task according to the target statistical parameter and the target counting parameter in the following manner: when the triggering task event list includes a first task event and a second task event, and the first task set includes a first task and a second task, obtain a first statistical parameter corresponding to the first task and a second statistical parameter corresponding to the second task, wherein the target statistical parameter includes the first statistical parameter and the second statistical parameter, and the first task and the second task are tasks obtained by searching the first task event and the second task event through the mapping relationship; determine a first counting parameter of the first task and a second counting parameter of the second task according to the mapping relationship, wherein the target counting parameter includes the first counting parameter and the second counting parameter; when the task event having the mapping relationship with the first task does not include other task events except the first task event and the second task event, determine that the matching state of the first task is that all the task events having the mapping relationship with the first task have been triggered; when the task event having the mapping relationship with the second task also includes other task events except the first task event and the second task event, determine that the matching state of the second task is that there is an untriggered task event having the mapping relationship with the second task.

[0011] Optionally, the device is used to determine the target statistical parameters of the target task based on the first task event set and the first task set in the following manner: searching for the target task in the first task set; when the target task is found, determining the number of task events in the first task event set that have the mapping relationship with the target task based on the mapping relationship, and determining the number of task events as the target statistical parameters.

[0012] Optionally, the device is used to determine the target count parameter of the target task when the trigger task event list includes the target task event in the following manner: in the process of processing the target task event, adding the target task event to the trigger task event list; when the trigger task event list includes the target task event, determining the target count parameter of the target task according to the number of target task events in the trigger task event list.

[0013] Optionally, the device is used to obtain a first task event set and a first task set in the following manner: obtain a pre-configured second task event set and a second task set; establish an inverse relationship between the second task event set and the second task set, wherein the inverse relationship includes a correspondence between a task event in the second task event set and a task subset in the second task set; deduplicate task identifiers in multiple task subsets according to the inverse relationship to determine a target task data organization structure, wherein the target task data organization structure includes the first task event set, the first task set and the mapping relationship, and each task identifier in the target task data organization structure is unique.

[0014] Optionally, the device is used to determine the completion status of the target task according to the task condition parameters of the target task and the task event parameters of the target task event when all task events having the mapping relationship with the target task have been triggered in the following manner: obtaining the task condition parameters and the task event parameters; determining that the target task is completed when the task event parameters satisfy the task conditions indicated by the task condition parameters; and determining that the target task is not completed when the task event parameters do not satisfy the task conditions indicated by the task condition parameters.

[0015] Optionally, the device is used to determine that the target task has been completed when the task event parameter satisfies the task condition indicated by the task condition parameter in at least one of the following ways: when the task condition parameter indicates that the value of the first business parameter needs to satisfy a first preset condition, determine whether the value of the first business parameter in the task event parameter satisfies the first preset condition, wherein the business parameters generated by the target task event include the first business parameter; when the first business parameter in the task event parameter satisfies the first preset condition, determine that the target task has been completed; when the task condition parameter indicates that the type of the second business parameter needs to satisfy a second preset condition, determine that the task event whether the type of the second business parameter in the parameter satisfies the second preset condition, wherein the business parameters generated by the target task event include the second business parameter; when the second business parameter in the task event parameter satisfies the second preset condition, it is determined that the target task has been completed; when the task condition parameter indicates that the object to which the third business parameter belongs needs to satisfy the third preset condition, it is determined whether the object to which the third business parameter in the task event parameter belongs satisfies the third preset condition, wherein the business parameters generated by the target task event include the third business parameter; when the third business parameter in the task event parameter satisfies the third preset condition, it is determined that the target task has been completed.

[0016] Optionally, the device is used to determine that the target task has been completed when the task event parameter satisfies the task condition indicated by the task condition parameter in the following manner: when the task condition parameter indicates that the value of the first business parameter needs to satisfy a first preset condition, determine whether the value of the first business parameter in the task event parameter satisfies the first preset condition, wherein the business parameters generated by the target task event include the first business parameter; when the task condition parameter indicates that the type of the second business parameter needs to satisfy a second preset condition, determine whether the type of the second business parameter in the task event parameter satisfies the second preset condition, wherein the business parameters generated by the target task event include the second business parameter; when the task condition parameter indicates that the object to which the third business parameter belongs needs to satisfy a third preset condition, determine whether the object to which the third business parameter belongs in the task event parameter satisfies the third preset condition, wherein the business parameters generated by the target task event include the third business parameter; when the first business parameter in the task event parameter satisfies the first preset condition, the second business parameter satisfies the second preset condition, and the third business parameter satisfies the third preset condition, determine that the target task has been completed.

[0017] Optionally, the device is used to determine that the target task has been completed when the task event parameters satisfy the task conditions indicated by the task condition parameters in at least one of the following ways: when the target task is a game task and the task condition parameters indicate that the virtual level of the virtual operation object needs to meet a preset virtual level, determine whether the target virtual level of the target virtual operation object in the task event parameters meets the preset level; when the target virtual level meets the preset virtual level, determine that the target task has been completed; when the target task is a game task and the task condition parameters indicate that the number of virtual resources held by the virtual operation object needs to meet a preset number of virtual resources, determine whether the target number of virtual resources held by the target virtual operation object in the task event parameters meets the preset number of virtual resources; when the target virtual level meets the preset number of virtual resources When the quantity meets the preset virtual resource quantity, it is determined that the target task has been completed; when the target task is a game task and the task condition parameter indicates that the virtual ranking held by the virtual operation object needs to meet the preset virtual ranking, it is determined whether the target virtual ranking held by the target virtual operation object in the task event parameter meets the preset virtual ranking; when the target virtual ranking meets the preset virtual ranking, it is determined that the target task has been completed; when the target task is a game task and the task condition parameter indicates that the virtual game duration of the virtual operation object needs to meet the preset virtual game duration, it is determined whether the target virtual game duration of the target virtual operation object in the task event parameter meets the preset virtual game duration; when the target virtual game duration meets the preset virtual game duration, it is determined that the target task has been completed.

[0018] According to another aspect of the embodiments of the present application, a computer-readable storage medium is provided, in which a computer program is stored, wherein the computer program is configured to execute the above-mentioned task data processing method when running.

[0019] According to another aspect of the embodiment of the present application, a computer program product or a computer program is provided, the computer program product or the computer program includes computer instructions, and the computer instructions are stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device performs the above task data processing method.

[0020] According to another aspect of an embodiment of the present application, there is also provided an electronic device, including a memory and a processor, wherein the memory stores a computer program, and the processor is configured to execute the above-mentioned task data processing method through the computer program.

[0021] In an embodiment of the present application, a first task event set and a first task set are obtained, wherein a task event in the first task event set is pre-set with a mapping relationship with at least one task in the first task set, and when the triggering task event list includes a target task event, the target task is searched for through the first task event set and the first task set according to the target task event, and a matching status of the target task is determined, wherein the target task event has a mapping relationship with the target task, the triggering task event list includes the currently triggered task events, and the matching status is used to indicate whether all task events having a mapping relationship with the target task have been triggered, and when all task events having a mapping relationship with the target task have been triggered, the completion status of the target task is determined according to the task condition parameters of the target task and the task event parameters of the target task event. By organizing and managing task data in an inverted index manner, the processing efficiency of task data can be improved, thereby achieving the purpose of avoiding invalid tasks from being traversed multiple times.

[0022] In addition, by adopting a two-layer data plane structure, it supports rapid judgment of whether a task has reached completion status, thereby achieving the purpose of optimizing the task status judgment process, thereby achieving the technical effect of improving the processing efficiency of task data and reducing the processing resource overhead of task data, thereby solving the technical problem of low processing efficiency of task data in related technologies. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0024] Figure 1 is a schematic diagram of an application environment of an optional task data processing method according to an embodiment of the present application;

[0025] Figure 2 is a flowchart of an optional task data processing method according to an embodiment of the present application;

[0026] Figure 3 is a schematic diagram of an optional task data processing method according to an embodiment of the present application;

[0027] Figure 4 is a schematic diagram of another optional method for processing task data according to an embodiment of the present application;

[0028] Figure 5 is a schematic diagram of another optional method for processing task data according to an embodiment of the present application;

[0029] Figure 6is a schematic diagram of another optional task data processing method according to an embodiment of the present application;

[0030] Figure 7 is a schematic diagram of another optional method for processing task data according to an embodiment of the present application;

[0031] Figure 8 is a schematic diagram of another optional task data processing method according to an embodiment of the present application;

[0032] Fig. 9 is a schematic diagram of another optional method for processing task data according to an embodiment of the present application;

[0033] Fig.10 is a schematic diagram of another optional method for processing task data according to an embodiment of the present application;

[0034] Fig.11 is a schematic diagram of another optional method for processing task data according to an embodiment of the present application;

[0035] Fig.12 is a schematic diagram of another optional task data processing method according to an embodiment of the present application;

[0036] Fig.13 is a schematic structural diagram of an optional task data processing device according to an embodiment of the present application;

[0037] Fig.14 is a schematic diagram of the structure of an optional task data processing product according to an embodiment of the present application;

[0038] Fig.15 It is a schematic diagram of the structure of an optional electronic device according to an embodiment of the present application. DETAILED DESCRIPTION

[0039] In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present application.

[0040] It should be noted that the terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments of the present application described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device comprising a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0041] First, some nouns or terms that appear in the description of the embodiments of the present application are subject to the following interpretation:

[0042] A task condition consists of explicit constraints on a specific game event and certain specified characteristics when the event is triggered.

[0043] The present application is described below in conjunction with embodiments:

[0044] According to one aspect of an embodiment of the present application, a method for processing task data is provided. Optionally, in this embodiment, the method for processing task data can be applied to: Figure 1 In the hardware environment composed of the server 101 and the terminal device 103 shown in FIG. Figure 1As shown, the server 101 is connected to the terminal 103 via a network, and can be used to provide services for the terminal device or the application installed on the terminal device. The application can be a video application, an instant messaging application, a browser application, an educational application, a game application, etc. A database 105 may be set up on the server or independently of the server to provide data storage services for the server 101, for example, a game data storage server. The above-mentioned network may include, but is not limited to, a wired network and a wireless network, wherein the wired network includes, a local area network, a metropolitan area network and a wide area network; the wireless network includes, Bluetooth, WIFI and other networks that implement wireless communication; the terminal device 103 may be a terminal configured with an application, and may include, but is not limited to, at least one of the following: a mobile phone (such as an Android phone, an iOS phone, etc.), a laptop computer, a tablet computer, a PDA, a MID (Mobile Internet Devices), a PAD, a desktop computer, a smart TV, an intelligent voice interaction device, a smart home appliance, a vehicle-mounted terminal, an aircraft, a virtual reality (VR) terminal, an augmented reality (AR) terminal, a mixed reality (MR) terminal and other computer devices; the above-mentioned server may be a single server, a server cluster consisting of multiple servers, or a cloud server.

[0045] Combination Figure 1 As shown, the above-mentioned task data processing method can be implemented in the terminal device 103 through the following steps:

[0046] S1, obtaining a first task event set and a first task set on the terminal device 103, wherein a mapping relationship is preset between a task event in the first task event set and at least one task in the first task set;

[0047] S2, in the case where the triggering task event list includes the target task event, searching for the target task through the first task event set and the first task set according to the target task event on the terminal device 103, and determining the matching status of the target task, wherein the target task event has a mapping relationship with the target task, the triggering task event list includes the currently triggered task events, and the matching status is used to indicate whether all the task events having a mapping relationship with the target task have been triggered;

[0048] S3, when all the task events having a mapping relationship with the target task have been triggered, the completion status of the target task is determined on the terminal device 103 according to the task condition parameters of the target task and the task event parameters of the target task event.

[0049] Optionally, in this embodiment, the above task data processing method can also be implemented by a server, for example, Figure 1 It is implemented in the server 101 shown; or it is implemented by the terminal device and the server together.

[0050] The above is only an example and is not specifically limited in this embodiment.

[0051] Optionally, as an optional implementation, as Figure 2 As shown, the method for processing the above task data includes:

[0052] S202, acquiring a first task event set and a first task set, wherein a mapping relationship is preset between a task event in the first task event set and at least one task in the first task set;

[0053] Optionally, in this embodiment, the above-mentioned task data processing method can be applied to task data processing scenarios including but not limited to various application programs.

[0054] Exemplarily, it may include but is not limited to game application scenarios, instant messaging application scenarios, e-commerce application scenarios, etc.

[0055] Optionally, in this embodiment, the above-mentioned task event can be understood to include but is not limited to a task event triggered by a user's operation or a task event generated by the server according to the running status of the application program.

[0056] In an exemplary embodiment, taking the game application scenario as an example, the above-mentioned task events may include but are not limited to the start or end of a game, the user controlling the virtual operation object to complete the attack or treatment of other virtual operation objects, the user opening the game mall, and other task events.

[0057] In another exemplary embodiment, taking an e-commerce application scenario as an example, the above-mentioned task events may include but are not limited to task events such as a user initiating a purchase request, a merchant initiating a delisting request, and the platform settling related orders.

[0058] In another exemplary embodiment, taking the instant messaging application scenario as an example, the above task events may include but are not limited to task events such as a user initiating a voice call request, a server initiating a media information push request to a user, and an instant messaging application generating an update request.

[0059] For example, Figure 3 is a schematic diagram of an optional task data processing method according to an embodiment of the present application, such as Figure 3As shown, when the user drags a control in the application program to a preset target area, it can be understood that one event in the first task event set is triggered.

[0060] For example, Figure 4 is a schematic diagram of another optional task data processing method according to an embodiment of the present application, such as Figure 4 As shown, the user is playing a game through a game application. When the game ends, the server automatically responds by displaying the game end screen and record information, which can be understood as triggering an event in the above-mentioned first task event set.

[0061] Optionally, in this embodiment, the above-mentioned task can be understood as a set of task conditions pre-configured for each task event.

[0062] In an exemplary embodiment, taking a game application scenario as an example, the above task conditions may include but are not limited to the ranking conditions of the target account, the virtual life value conditions of the target account, the quantity conditions of the virtual resources held by the target account, etc. The above different task conditions together constitute a task. When the event parameters in the task event meet all the above task conditions, it can be understood that the above task is in a completed state.

[0063] In another exemplary embodiment, taking an e-commerce application scenario as an example, the above task conditions may include but are not limited to the purchase frequency conditions of the target account, the inventory conditions of the merchant, the transaction volume conditions of the trading platform, etc. The above different task conditions together constitute a task. When the event parameters in the task event meet all the above task conditions, it can be understood that the above task is in a completed state.

[0064] In another exemplary embodiment, taking the instant messaging application scenario as an example, the above task conditions may include but are not limited to the number of friends of the target account, the number of groups joined by the target account, the number of online users on the instant messaging application related platform, etc. The above different task conditions together constitute a task. When the event parameters in the task event meet all the above task conditions, it can be understood that the above task is in a completed state.

[0065] For example, Figure 5 is a schematic diagram of another optional task data processing method according to an embodiment of the present application, such as Figure 5 As shown, taking the game application as an example, it can be set that the user's virtual level exceeds level 20 and the virtual gold coin holdings exceed 50. Then the above task includes two task conditions. The task condition that the virtual gold coin holdings exceed 50 can be Figure 5 The task condition 10011 shown, the task condition virtual level exceeds 20 levels can be Figure 5Task condition 10012 is shown.

[0066] It should be noted that a mapping relationship is pre-set between a task event in the first task event set and at least one task in the first task set, which can be understood as pre-setting one or more tasks corresponding to each task event.

[0067] For example, Figure 6 is a schematic diagram of another optional task data processing method according to an embodiment of the present application, such as Figure 6 As shown, the first task event set is a task event set consisting of task event 501, task event 502, task event 503 and task event 504, and the first task set is a task set consisting of task 1001, task 1002 and task 1003.

[0068] Among them, task event 501 has the above-mentioned mapping relationship with task 1001 and task 1002, task event 502 has the above-mentioned mapping relationship with task 1001, task 1002 and task 1003, task event 503 has the above-mentioned mapping relationship with task 1001, task 1002 and task 1003, and task event 504 has the above-mentioned mapping relationship with task 1002.

[0069] S204, in the case where the triggering task event list includes the target task event, searching for the target task through the first task event set and the first task set according to the target task event, and determining a matching state of the target task, wherein the target task event has a mapping relationship with the target task, the triggering task event list includes currently triggered task events, and the matching state is used to indicate whether all task events having a mapping relationship with the target task have been triggered;

[0070] Optionally, in this embodiment, the above-mentioned triggered task event list is used to record the currently triggered task events. The triggering method of the above-mentioned task events is as mentioned above and will not be repeated here.

[0071] It should be noted that, whenever a task event in the first task event set is triggered, the task event needs to be added to the above-mentioned triggered task event list.

[0072] Optionally, in this embodiment, the above-mentioned target task event can be understood as any one or more task events in the above-mentioned triggering task event list. When the above-mentioned target task event is detected in the triggering task event list, the target task having the above-mentioned mapping relationship with the above-mentioned target task event can be found through the above-mentioned first task event set and the above-mentioned first task set.

[0073] For example, Figure 7is a schematic diagram of another optional task data processing method according to an embodiment of the present application, such as Figure 7 As shown, the first task event set includes task event 501, task event 502, task event 503 and task event 504, and the first task set includes task 1001, task 1002 and task 1003. When the triggered task event list includes task event 502 and task event 503, task 1001 and task 1003 having a mapping relationship with task event 502, and task 1001 and task 1003 having a mapping relationship with task event 503 can be found according to the above mapping relationship. At this time, the target task events are task event 502 and task event 503, and the target tasks are task 1001 and task 1003.

[0074] Optionally, in this embodiment, the above matching status may include but is not limited to matching or not matching, or a matching level corresponding to a matching degree.

[0075] In an exemplary embodiment, the above matching status includes matching, which means that all task events having a mapping relationship with the target task have been triggered, such as Figure 7 As shown, the task events concerned by task 1003 include task event 502 and task event 503, but do not include task event 501 and task event 504. At this time, it can be understood that all task events with mapping relationships for task 1003 have been triggered.

[0076] In another exemplary embodiment, the above matching state includes mismatch, which indicates that there is an untriggered task event having a mapping relationship with the target task, such as Figure 7 As shown, the task events concerned by task 1001 include task event 501, task event 502 and task event 503, but do not include task event 504. At this time, it can be understood that task 1001 has an untriggered task event 501 with a mapping relationship.

[0077] In another exemplary embodiment, the above-mentioned matching level corresponding to the matching degree can be understood as determining the matching level according to the matching degree. The matching degree may include but is not limited to the ratio of the number of untriggered task events that have a mapping relationship with the target task to the number of all task events that have a mapping relationship. Based on this ratio, the target task can be divided into different matching levels, and different matching levels correspond to different subsequent processing strategies.

[0078] In other words, when the number of task events with a mapping relationship is very large, and the number of untriggered task events with a mapping relationship with the target task is very small, this situation can also be approximately regarded as representing a matching level for subsequent processing. Of course, the application scenario of this exemplary embodiment is generally used in scenarios where the processing accuracy of task data is required to be lower than that of the aforementioned exemplary embodiments. By appropriately relaxing the accuracy limit, the processing speed of the task can be accelerated.

[0079] It should be noted that the present application does not impose any specific limitation on the above exemplary embodiments.

[0080] S206 , when all the task events having a mapping relationship with the target task have been triggered, determining the completion status of the target task according to the task condition parameters of the target task and the task event parameters of the target task event.

[0081] Optionally, in this embodiment, the above-mentioned task condition parameters may include but are not limited to task conditions pre-configured for the target task.

[0082] For example, the organization format of tasks and task conditions is:

[0083] Task1001=Conditon_10011+Condition_10012;

[0084] Task1002=Condition_10021+Condition_10022+Condition_10023+Condition_10024;

[0085] Task1003=Condition_10031+Condition_10032.

[0086] Among them, Task1001, Task1002, and Task1003 are the expressions of the above-mentioned target tasks, Conditon_10011+Condition_10012 are the task conditions corresponding to Task1001, and each task condition includes corresponding task condition parameters.

[0087] In an exemplary embodiment, taking the above Task 1001 as an example, it includes:

[0088] Condition10011 = {Event_501, CoinNum> = 50}, 501 represents the game login event, and requires that the number of virtual coins held by the player at this time is greater than or equal to 50;

[0089] Condition10012={Event_502, Level=20}, 502 represents the player's current level event, and requires that the player's current virtual level is 20.

[0090] In an exemplary embodiment, each task condition contained in the above task must be fully met before it can be determined to be in a completed state. For example, for Task 1001, task conditions 10011 and task conditions 10012 must all be met before Task 1001 should be determined to be in a completed state.

[0091] In another exemplary embodiment, if any task condition contained in the above task is met, it can be determined to be in the completed state. For example, for Task 1001, if any of the task conditions 10011 and 10012 are met, Task 1001 can be determined to be in the completed state.

[0092] In another exemplary embodiment, some of the task conditions contained in the above task must be met, and some of the task conditions may not be met, and may also be determined to be in a completed state. For example: for Task1001, task condition 10011 is a task condition that must be met, and task condition 10012 is a task condition that does not have to be met. When task condition 10011 is met, regardless of whether task condition 10012 is met, Task1001 can be determined to be in a completed state. When task condition 10011 is not met, regardless of whether task condition 10012 is met, Task1001 is determined to be in an unfinished state.

[0093] It should be noted that the above completion status may include but is not limited to completed and uncompleted states, and may also include but is not limited to other completion states such as partially completed.

[0094] For example, Figure 8 is a schematic diagram of another optional task data processing method according to an embodiment of the present application, such as Figure 8 As shown, by first obtaining the triggered task event list and using the inverted index method to organize and manage task data, it is possible to determine task events 501, 502, and 503 that the target task Task1001 is concerned about. Then, by judging that all the task events that Task1001 is concerned about are in the triggered task event list (belonging to triggered task events), the task event parameters of the task events are compared with the corresponding task conditions. When all the comparisons are correct, task Task1001 is a completed task, that is, the completion status of Task1001 is determined, which can improve the processing efficiency of task data and achieve the purpose of avoiding invalid tasks from being traversed multiple times.

[0095] Through this embodiment, a first task event set and a first task set are obtained, wherein a task event in the first task event set is pre-set with a mapping relationship with at least one task in the first task set. When the triggering task event list includes a target task event, the target task is searched for through the first task event set and the first task set according to the target task event, and the matching status of the target task is determined, wherein the target task event has a mapping relationship with the target task, the triggering task event list includes the currently triggered task events, and the matching status is used to indicate whether all the task events having a mapping relationship with the target task have been triggered. When all the task events having a mapping relationship with the target task have been triggered, the completion status of the target task is determined according to the task condition parameters of the target task and the task event parameters of the target task event. By organizing and managing task data in an inverted index manner, the processing efficiency of task data can be improved, and the purpose of avoiding invalid tasks from being traversed multiple times is achieved, thereby achieving the technical effect of improving the processing efficiency of task data and reducing the processing resource overhead of task data, thereby solving the technical problem of low processing efficiency of task data in related technologies.

[0096] As an optional scheme, when the triggering task event list includes the target task event, the target task is searched for through the first task event set and the first task set according to the target task event, and the matching status of the target task is determined, including: determining the target statistical parameters of the target task according to the first task event set and the first task set, wherein the target statistical parameters are used to represent the total number of task events that have a mapping relationship with the target task; when the triggering task event list includes the target task event, determining the target counting parameters of the target task, wherein the target counting parameters are used to represent the number of target task events; and determining the matching status of the target task according to the target statistical parameters and the target counting parameters.

[0097] Optionally, in this embodiment, the above target statistical parameter can be understood as the total number of task events concerned by the target task, that is, the total number of task events having the above mapping relationship with the target task.

[0098] Optionally, in this embodiment, the target counting parameter may be understood as the total number of task events in the triggering task event list among the task events concerned by the target task, that is, the number of target task events.

[0099] Through this embodiment, in the process of processing task events, each time a task event is processed, the count of each task event mapping is determined, and the counting parameters of each found task are obtained by calculation and compared with their corresponding statistical parameters. When the counting parameters and statistical parameters are the same, it can be determined that the current task event list meets the event set required for task processing, and it is worth conducting a more detailed parameter comparison later.

[0100] As an optional scheme, the matching status of the target task is determined according to the target statistical parameter and the target counting parameter, including: when the values ​​of the target statistical parameter and the target counting parameter are the same, determining that the matching status of the target task is that all task events having a mapping relationship with the target task have been triggered; when the value of the target counting parameter is less than the target statistical parameter, determining that the matching status of the target task is that there are untriggered task events having a mapping relationship with the target task.

[0101] Optionally, in this embodiment, the same values ​​of the target statistical parameter and the target counting parameter can be understood as the task events concerned by the target task have been triggered, and the value of the target counting parameter is less than the target statistical parameter can be understood as the target task has an untriggered task event with a mapping relationship.

[0102] As an optional scheme, determining the matching status of the target task according to the target statistical parameters and the target counting parameters includes: when the triggering task event list includes the first task event and the second task event, and the first task set includes the first task and the second task, obtaining the first statistical parameter corresponding to the first task and the second statistical parameter corresponding to the second task, wherein the target statistical parameter includes the first statistical parameter and the second statistical parameter, and the first task and the second task are tasks obtained by searching through the mapping relationship according to the first task event and the second task event; determining the first counting parameter of the first task and the second counting parameter of the second task according to the mapping relationship, wherein the target counting parameter includes the first counting parameter and the second counting parameter; when the task event having a mapping relationship with the first task does not include other task events except the first task event and the second task event, determining the matching status of the first task is that all the task events having a mapping relationship with the first task have been triggered; when the task event having a mapping relationship with the second task also includes other task events except the first task event and the second task event, determining the matching status of the second task is that there are untriggered task events having a mapping relationship with the second task.

[0103] Optionally, in this embodiment, the first task and the second task may be two tasks found by a task event in a triggering task event list.

[0104] In an exemplary embodiment, Figure 7As shown, the first task is illustrated task 1003, the second task is illustrated task 1001, the task events concerned by task 1003 include task event 502 and task event 503, excluding task event 501 and task event 504. At this time, it can be understood that all task events with mapping relationships for task 1003 have been triggered, and the task events concerned by task 1001 include task event 501, task event 502 and task event 503, excluding task event 504. At this time, it can be understood that task 1001 has a task event 501 with a mapping relationship that has not been triggered.

[0105] As an optional scheme, the target statistical parameters of the target task are determined based on the first task event set and the first task set, including: searching for the target task in the first task set; when the target task is found, determining the number of task events in the first task event set that have a mapping relationship with the target task based on the mapping relationship, and determining the number of task events as the target statistical parameters.

[0106] Optionally, in this embodiment, searching for the target task in the first task set may be understood as filtering the target task from the first task set according to a task identifier of the target task. The task identifier may include but is not limited to a digital identifier, a text identifier, and the like.

[0107] It should be noted that the above-mentioned determination of the number of task events in the first task event set that have a mapping relationship with the target task according to the mapping relationship, and determination of the number of task events as the target statistical parameter may include but is not limited to directly obtaining the number of task events that need to be paid attention to for each task, marked as: Task-Event-Cfg (task ID) (corresponding to the aforementioned target statistical parameter). For example:

[0108] Task-Event-Cfg(1001)=3, indicating that the number of task events that task 1001 pays attention to is 3;

[0109] Task-Event-Cfg(1002)=4, indicating that the number of task events that task 1002 pays attention to is 4;

[0110] Task-Event-Cfg(1003)=2, indicating that the number of task events that task 1003 pays attention to is 2.

[0111] As an optional scheme, when the trigger task event list includes the target task event, the target count parameter of the target task is determined, including: in the process of processing the target task event, adding the target task event to the trigger task event list; when the trigger task event list includes the target task event, determining the target count parameter of the target task according to the number of target task events in the trigger task event list.

[0112] It should be noted that in the process of processing task events, each time a task event is processed, the count (Event-Task-Count) of each task event mapping can be increased by 1. After all task event lists are processed, if the values ​​of Event-Task-Cfg and Event-Task-Count are exactly the same, it can be determined that the current task event list meets the event set required for task processing.

[0113] For example, Fig. 9 is a schematic diagram of another optional task data processing method according to an embodiment of the present application, such as Fig. 9 As shown, the set of events triggered simultaneously is: 502 and 503, and the inverse mapping table of tasks and events is analyzed to update the statistical counts of each task respectively.

[0114] For task 1001, it is only triggered once by 502, count + 1, Task-Event-Count = 2; 1002 is triggered twice by 502 and 503, count + 1, Task-Event-Count = 2; 1003 is triggered twice by 502 and 503, count + 1, Task-Event-Count = 2. Task-Event-Count is the same as Task-Event-Cfg count, which can determine that the number of task events required is basically matched with the number of events included in the event list.

[0115] Obviously, only the two counts of task 1003 are the same, that is, only 1003 needs to perform a detailed comparison of the task condition information and event parameters.

[0116] As an optional scheme, obtaining a first task event set and a first task set includes: obtaining a pre-configured second task event set and a second task set; establishing an inverse relationship between the second task event set and the second task set, wherein the inverse relationship includes a corresponding relationship between a task event in the second task event set and a task subset in the second task set; deduplicating task identifiers in multiple task subsets according to the inverse relationship to determine a target task data organization structure, wherein the target task data organization structure includes the first task event set, the first task set, and a mapping relationship, and each task identifier in the target task data organization structure is unique.

[0117] Optionally, in this embodiment, the second task event set and the second task set are initially set task event set and task set that require data processing.

[0118] In an exemplary embodiment, Fig.10is a schematic diagram of another optional task data processing method according to an embodiment of the present application, such as Fig.10 As shown, the second task event set and the second task set are pre-set to be arranged in a positive row mapping manner. Fig.10 In the three-level task data organization structure shown, the second-level structure task conditions actually exist as an intermediate state. Task conditions are a conceptual encapsulation of the third-level event and parameter rule details. For example: {501, CoinNum>=50} and {501, CoinNum>=40}, the biggest difference between these two task conditions is the requirement for the characteristic parameter range, and the other events and characteristic parameters are exactly the same. If the explicit requirement for characteristic parameters is abandoned, the mapping relationship between the first level and the third level can be directly established.

[0119] After removing the original second-level data plane, a direct mapping relationship is established between the first and third levels. This mapping method is usually "positive order". Positive order cannot improve the system processing efficiency when processing task events. Therefore, if the task list associated with the task event can be directly found when the task event is triggered, the search speed of the task list can be significantly improved. This mapping method between events and tasks is called establishing a reverse order relationship. Fig.11 is a schematic diagram of another optional task data processing method according to an embodiment of the present application, such as Fig.11 As shown, by searching for tasks by task events, it can be represented as establishing an inverse relationship between the second task event set and the second task set.

[0120] In an exemplary embodiment, Fig.12 is a schematic diagram of another optional task data processing method according to an embodiment of the present application, in which an inverse relationship is established between more tasks and events, such as Fig.12 By replacing the forward order relationship between tasks and events with the reverse order relationship, it is possible to find the task list that meets the completion conditions more quickly. Compared with the forward order traversal, the number of searches is greatly reduced.

[0121] As an optional solution, step S206, when all task events having a mapping relationship with the target task have been triggered, determining the completion status of the target task according to the task condition parameters of the target task and the task event parameters of the target task event, includes:

[0122] S2062, obtaining task condition parameters and task event parameters;

[0123] S2064, when the task event parameter satisfies the task condition indicated by the task condition parameter, determining that the target task has been completed;

[0124] S2066: When the task event parameter does not satisfy the task condition indicated by the task condition parameter, determine that the target task is not completed.

[0125] As an optional solution, in step S2064, when the task event parameter satisfies the task condition indicated by the task condition parameter, determining that the target task has been completed includes at least one of the following:

[0126] In the case where the task condition parameter indicates that the value of the first business parameter needs to meet the first preset condition, determining whether the value of the first business parameter in the task event parameter meets the first preset condition, wherein the business parameter generated by the target task event includes the first business parameter; in the case where the first business parameter in the task event parameter meets the first preset condition, determining that the target task has been completed;

[0127] In the case where the task condition parameter indicates that the type of the second business parameter needs to meet the second preset condition, determining whether the type of the second business parameter in the task event parameter meets the second preset condition, wherein the business parameter generated by the target task event includes the second business parameter; in the case where the second business parameter in the task event parameter meets the second preset condition, determining that the target task has been completed;

[0128] When the task condition parameter indicates that the object to which the third business parameter belongs needs to meet the third preset condition, determine whether the object to which the third business parameter in the task event parameter belongs meets the third preset condition, wherein the business parameters generated by the target task event include the third business parameter; when the third business parameter in the task event parameter meets the third preset condition, determine that the target task has been completed.

[0129] Optionally, in this embodiment, the above-mentioned first business parameter can be understood as a partial business attribute parameter, for example, virtual life value, virtual gold coins, transaction volume, number of messages, etc., and the above-mentioned first preset condition can be understood as a preset threshold. When the value of the above-mentioned first business parameter is greater than the above-mentioned preset threshold, the first preset condition is met, or, when the value of the above-mentioned first business parameter is equal to the above-mentioned preset threshold, the first preset condition is met, or, when the value of the above-mentioned first business parameter is less than the above-mentioned preset threshold, the first preset condition is met. At this time, it is determined that the target task has been completed.

[0130] Optionally, in this embodiment, the above-mentioned second business parameter can be understood as a partial business type parameter, for example, game type, transaction type, contact type, etc., and the above-mentioned second preset condition can be understood as a preset type. When the above-mentioned second business parameter is the same as the above-mentioned preset type, the second preset condition is met, and at this time, it is determined that the target task has been completed.

[0131] Optionally, in this embodiment, the third business parameter can be understood as the object to which some businesses belong, for example, a virtual camp, a transaction source, a contact group, etc., and the third preset condition can be understood as the preset object. When the object indicated by the third business parameter is the same as the preset object, the third preset condition is met, and at this time, it is determined that the target task has been completed.

[0132] As an optional scheme, when the task event parameters satisfy the task conditions indicated by the task condition parameters, it is determined that the target task has been completed, including: when the task condition parameters indicate that the value of the first business parameter needs to satisfy the first preset condition, determining whether the value of the first business parameter in the task event parameters satisfies the first preset condition, wherein the business parameters generated by the target task event include the first business parameter; when the task condition parameters indicate that the type of the second business parameter needs to satisfy the second preset condition, determining whether the type of the second business parameter in the task event parameters satisfies the second preset condition, wherein the business parameters generated by the target task event include the second business parameter; when the task condition parameters indicate that the object to which the third business parameter belongs needs to satisfy the first preset condition, determining whether the object to which the third business parameter in the task event parameters belongs meets the third preset condition, wherein the business parameters generated by the target task event include the third business parameter; when the first business parameter in the task event parameters satisfies the first preset condition, the second business parameter satisfies the second preset condition, and the third business parameter satisfies the third preset condition, it is determined that the target task has been completed.

[0133] It should be noted that, in this embodiment, the first preset condition, the second preset condition and the third preset condition must all be met, and only then will it be determined that the target task has been completed.

[0134] As an optional solution, when the task event parameter satisfies the task condition indicated by the task condition parameter, determining that the target task has been completed includes at least one of the following:

[0135] When the target task is a game task and the task condition parameter indicates that the virtual level of the virtual operation object needs to meet a preset virtual level, determining whether the target virtual level of the target virtual operation object in the task event parameter meets the preset level; and determining that the target task has been completed when the target virtual level meets the preset virtual level;

[0136] When the target task is a game task and the task condition parameter indicates that the number of virtual resources held by the virtual operation object needs to meet the preset number of virtual resources, determining whether the target number of virtual resources held by the target virtual operation object in the task event parameter meets the preset number of virtual resources; when the target number of virtual resources meets the preset number of virtual resources, determining that the target task has been completed;

[0137] When the target task is a game task and the task condition parameter indicates that the virtual ranking held by the virtual operation object needs to meet the preset virtual ranking, determining whether the target virtual ranking held by the target virtual operation object in the task event parameter meets the preset virtual ranking; when the target virtual ranking meets the preset virtual ranking, determining that the target task has been completed;

[0138] When the target task is a game task and the task condition parameter indicates that the virtual game duration of the virtual operation object needs to meet the preset virtual game duration, determine whether the target virtual game duration of the target virtual operation object in the task event parameter meets the preset virtual game duration; when the target virtual game duration meets the preset virtual game duration, determine that the target task has been completed.

[0139] The following is a further explanation of this application with reference to specific examples:

[0140] This application introduces a method of organizing and managing task condition data by using an inverted index, which replaces the method of organizing task condition data management based on a linked list in the related art. Through a two-layer data plane structure, it supports quickly judging whether a task has reached a completed state.

[0141] In an exemplary embodiment, when applied to a game scenario, a task usually includes multiple task conditions, and each task condition mainly includes specific requirements for a certain parameter range in a specified game event.

[0142] The organizational format of tasks and task conditions is:

[0143] Task1001=Conditon_10011+Condition_10012+Condition_10013;

[0144] Task1002=Condition_10021+Condition_10022+Condition_10023+Condition_10024;

[0145] Task1003=Condition_10031+Condition_10032.

[0146] When a task is completed, all the task conditions contained in the task must be met. For example, for Task 1001, task conditions 10011, 10012, and 10013 must all be met before Task 1001 can be considered completed.

[0147] The organization format of task conditions and game events is:

[0148] Condition10011 = {Event_501, CoinNum> = 50}, 501 represents the game login event, and the number of gold coins at this time is required to be greater than or equal to 50;

[0149] Condition10012 = {Event_502, Level = 20}, 502 represents the player's current level event, and the current level is required to be 20;

[0150] Condition10031 = {Event_502, CoinNum> = 100}, 501, represents the current level event, and requires that the number of gold coins at this time is greater than or equal to 100;

[0151] Condition10032 = {Event_503, Rank = 1}, represents a game settlement event, and the game ranking is first;

[0152] A task condition consists of explicit constraints on a specific game event and certain specified characteristics when the event is triggered.

[0153] Currently, game task data is generally organized in a linked list. When a game event is triggered, all open tasks are traversed to determine whether each task condition under the task is met. When each task event is triggered, all task conditions contained in each open task are judged and decided.

[0154] This application implements a fast task data processing process through the following steps:

[0155] S1, inverted index:

[0156] S1-1, establish a direct mapping relationship between tasks and events:

[0157] A completed task information is actually maintained by three layers of data. For example:

[0158] Task1001=Conditon_10011+Condition_10012+Condition_10013;

[0159] Condition10011={Event_501,CoinNum>=50};

[0160] Condition10012={Event_502,Level=20};

[0161] Condition10013={Event_503,Rank>=4}.

[0162] In this three-level task data organization structure, the second-level structure task conditions actually exist as an intermediate state. Task conditions are a conceptual encapsulation of the third-level event and parameter rule details. For example: {501, CoinNum>=50} and {501, CoinNum>=40}, the biggest difference between these two task conditions is the requirement for the characteristic parameter range, and the other events and characteristic parameters are exactly the same. If you give up the explicit requirement for characteristic parameters, you can directly establish the mapping relationship between the first level and the third level.

[0163] S1-2, establish the inverse relationship between tasks and events:

[0164] After removing the original second-level data plane, a direct mapping relationship is established between the first and third levels. This mapping method is usually "positive order". When processing task events, the positive order still uses the method of traversing one by one, which cannot improve the system processing efficiency. If the task list associated with the task event can be directly found when the task event is triggered, the search speed of the task list can be significantly improved. This mapping method between events and tasks is called "reverse order".

[0165] By replacing the forward order relationship between tasks and events with the reverse order relationship, you can more quickly find a list of tasks that meet the completion conditions. Compared with traversing the forward order item by item, the number of searches is greatly reduced.

[0166] S1-3, game ID is globally unique:

[0167] In the inverse relationship between tasks and events, there are still a lot of duplications when it comes to task ID management. At the same time, this duplication is not conducive to subsequent task condition detection. You can try to deduplicate task IDs globally and reorganize the inverse relationship between tasks and events.

[0168] S1-4, calculate the number of events that the task focuses on:

[0169] After the tasks are globally deduplicated, the number of task events that need to be paid attention to for each task can be directly obtained, marked as: Task-Event-Cfg (task ID). For example:

[0170] Task-Event-Cfg(1001)=3, indicating that the number of task events that task 1001 pays attention to is 3;

[0171] Task-Event-Cfg(1002)=4, indicating that the number of task events that task 1002 pays attention to is 4;

[0172] Task-Event-Cfg(1003)=2, indicating that the number of task events that task 1003 pays attention to is 2;

[0173] S1-5, filter tasks that meet the task event quantity requirements:

[0174] In the process of processing task events, each time a task event is processed, the count of each task event mapping (Event-Task-Count) is increased by 1. After all task event lists are processed, if the values ​​of Event-Task-Cfg and Event-Task-Count are exactly the same, it can be determined that the current task event list meets the event set required for task processing, and it is worthwhile to conduct a more detailed parameter comparison later.

[0175] An example of updating the task event map count is as follows:

[0176] In the above example, the set of events triggered simultaneously is: 502 and 503, and the inverted mapping table of tasks and events is analyzed to update the statistical counts of each task respectively.

[0177] For task 1001, it is only triggered once by 502, count + 1, Task-Event-Count = 2; 1002 is triggered twice by 502 and 503, count + 1, Task-Event-Count = 2; 1003 is triggered twice by 502 and 503, count + 1, Task-Event-Count = 2. Task-Event-Count is the same as Task-Event-Cfg count, which can determine that the number of task events required is basically matched with the number of events included in the event list.

[0178] Obviously, only the two counts of task 1003 are the same, that is, only 1003 needs to perform a detailed comparison of the task condition information and event parameters.

[0179] S2, detailed comparison of task condition parameters and event parameters:

[0180] The task obtained through the above calculation process has been satisfied in terms of the number of events that the task focuses on. For example, when 1003 focuses on events 502 and 503, and both 502 and 503 exist in the event list, the requirement of 1003 on the number of events is satisfied. Next, it is necessary to compare the characteristic parameter information attached to the event with the parameter information of the task condition one by one.

[0181] The detailed requirements in the condition list of Task 1003 are:

[0182] Condition10031 = {Event_502, Level> = 100}, simplified as: Task (1003). Level> = 100;

[0183] Condition10032={Event_503, Rank=1}, simplified as: Task(1003).Rank=1.

[0184] Now let's take two groups of event parameter lists as an example to illustrate:

[0185] Event parameter list 1: {Event502.Level=101, Event503.Rank=1}. The relationship between this task event parameter list and Task(1003) is: Task(1003).Level<=Event502.Level and Task(1003).Level==Event503.Level. Both task condition parameters meet the requirements. This event list can meet the requirements for triggering the completion of Task(1003).

[0186] Event parameter list 2: {Event502.Level=50,Event503.Rank=1}. The relationship between this task event parameter list and Task(1003) is: Task(1003).Level<=Event502.Level is not true, Task(1003).Rank==Event503.Rank is true. The parameters of one of the events do not meet the requirements of the task conditions and the task completion requirements cannot be met.

[0187] Through this embodiment, the task condition data is organized and managed in an inverted index manner instead of the method of organizing the task condition data based on a linked list, thereby improving the processing efficiency of the task data, and by adopting a two-layer data plane structure, it is possible to support rapid judgment of the task's completion status, further improving the processing efficiency of the task data.

[0188] It is understandable that in the specific implementation of this application, related data such as user information is involved. When the above embodiments of this application are applied to specific products or technologies, user permission or consent is required, and the collection, use and processing of relevant data need to comply with relevant laws, regulations and standards of relevant countries and regions.

[0189] It should be noted that, for the aforementioned method embodiments, for the sake of simplicity, they are all expressed as a series of action combinations, but those skilled in the art should be aware that the present application is not limited by the described order of actions, because according to the present application, certain steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also be aware that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily required by the present application.

[0190] According to another aspect of the embodiment of the present application, a task data processing device for implementing the above-mentioned task data processing method is also provided. Fig.13 As shown, the device comprises:

[0191] An acquisition module 1302 is used to acquire a first task event set and a first task set, wherein a task event in the first task event set is pre-set with at least one task in the first task set.

[0192] A search module 1304 is used for searching the target task through the first task event set and the first task set according to the target task event, and determining a matching state of the target task, when the trigger task event list includes the target task event, wherein the target task event has a mapping relationship with the target task, the trigger task event list includes the currently triggered task events, and the matching state is used to indicate whether all the task events having a mapping relationship with the target task have been triggered;

[0193] The determination module 1306 is used to determine the completion status of the target task according to the task condition parameters of the target task and the task event parameters of the target task event when all the task events having a mapping relationship with the target task have been triggered.

[0194] As an optional scheme, the above-mentioned device is used to search for the target task through the first task event set and the first task set according to the target task event and determine the matching status of the target task in the following manner when the triggering task event list includes the target task event: determine the target statistical parameters of the target task according to the first task event set and the first task set, wherein the target statistical parameters are used to represent the total number of task events that have a mapping relationship with the target task; when the triggering task event list includes the target task event, determine the target counting parameters of the target task, wherein the target counting parameters are used to represent the number of target task events; determine the matching status of the target task according to the target statistical parameters and the target counting parameters.

[0195] As an optional scheme, the above-mentioned device is used to determine the matching status of the target task according to the target statistical parameter and the target counting parameter in the following manner: when the values ​​of the target statistical parameter and the target counting parameter are the same, the matching status of the target task is determined as all task events having a mapping relationship with the target task have been triggered; when the value of the target counting parameter is less than the target statistical parameter, the matching status of the target task is determined as there are untriggered task events having a mapping relationship with the target task.

[0196] As an optional solution, the above-mentioned device is used to determine the matching state of the target task according to the target statistical parameter and the target counting parameter in the following manner: when the triggering task event list includes the first task event and the second task event, and the first task set includes the first task and the second task, obtain the first statistical parameter corresponding to the first task and the second statistical parameter corresponding to the second task, wherein the target statistical parameter includes the first statistical parameter and the second statistical parameter, and the first task and the second task are tasks obtained by searching through the mapping relationship according to the first task event and the second task event; determine the first counting parameter of the first task and the second counting parameter of the second task according to the mapping relationship, wherein the target counting parameter includes the first counting parameter and the second counting parameter; when the task event having a mapping relationship with the first task does not include other task events except the first task event and the second task event, determine the matching state of the first task as that all the task events having a mapping relationship with the first task have been triggered; when the task event having a mapping relationship with the second task also includes other task events except the first task event and the second task event, determine the matching state of the second task as that there is an untriggered task event having a mapping relationship with the second task.

[0197] As an optional scheme, the above-mentioned device is used to determine the target statistical parameters of the target task based on the first task event set and the first task set in the following manner: searching for the target task in the first task set; when the target task is found, determining the number of task events in the first task event set that have a mapping relationship with the target task based on the mapping relationship, and determining the number of task events as the target statistical parameters.

[0198] As an optional scheme, the above-mentioned device is used to determine the target counting parameters of the target task when the triggering task event list includes the target task event in the following manner: in the process of processing the target task event, the target task event is added to the triggering task event list; when the triggering task event list includes the target task event, the target counting parameters of the target task are determined according to the number of target task events in the triggering task event list.

[0199] As an optional scheme, the above-mentioned device is used to obtain the first task event set and the first task set in the following manner: obtain a pre-configured second task event set and a second task set; establish an inverse relationship between the second task event set and the second task set, wherein the inverse relationship includes a corresponding relationship between a task event in the second task event set and a task subset in the second task set; perform a deduplication operation on task identifiers in multiple task subsets according to the inverse relationship to determine a target task data organization structure, wherein the target task data organization structure includes the first task event set, the first task set and a mapping relationship, and each task identifier in the target task data organization structure is unique.

[0200] As an optional scheme, the above-mentioned device is used to determine the completion status of the target task according to the task condition parameters of the target task and the task event parameters of the target task event when all task events having a mapping relationship with the target task have been triggered in the following manner: obtaining the task condition parameters and the task event parameters; when the task event parameters meet the task conditions indicated by the task condition parameters, determining that the target task has been completed; when the task event parameters do not meet the task conditions indicated by the task condition parameters, determining that the target task has not been completed.

[0201] As an optional solution, the above-mentioned device is used to determine that the target task has been completed when the task event parameter satisfies the task condition indicated by the task condition parameter in at least one of the following ways: when the task condition parameter indicates that the value of the first business parameter needs to meet the first preset condition, determine whether the value of the first business parameter in the task event parameter meets the first preset condition, wherein the business parameter generated by the target task event includes the first business parameter; when the first business parameter in the task event parameter meets the first preset condition, determine that the target task has been completed; when the task condition parameter indicates that the type of the second business parameter needs to meet the second preset condition, determine whether the type of the second business parameter in the task event parameter meets the second preset condition, wherein the business parameter generated by the target task event includes the second business parameter; when the second business parameter in the task event parameter meets the second preset condition, determine that the target task has been completed; when the task condition parameter indicates that the object to which the third business parameter belongs needs to meet the third preset condition, determine whether the object to which the third business parameter belongs in the task event parameter meets the third preset condition, wherein the business parameter generated by the target task event includes the third business parameter; when the third business parameter in the task event parameter meets the third preset condition, determine that the target task has been completed.

[0202] As an optional solution, the above-mentioned device is used to determine that the target task has been completed in the following manner when the task event parameter satisfies the task condition indicated by the task condition parameter: when the task condition parameter indicates that the value of the first business parameter needs to satisfy the first preset condition, determine whether the value of the first business parameter in the task event parameter satisfies the first preset condition, wherein the business parameters generated by the target task event include the first business parameter; when the task condition parameter indicates that the type of the second business parameter needs to satisfy the second preset condition, determine whether the type of the second business parameter in the task event parameter satisfies the second preset condition, wherein the business parameters generated by the target task event include the second business parameter; when the task condition parameter indicates that the object to which the third business parameter belongs needs to satisfy the third preset condition, determine whether the object to which the third business parameter belongs in the task event parameter satisfies the third preset condition, wherein the business parameters generated by the target task event include the third business parameter; when the first business parameter in the task event parameter satisfies the first preset condition, the second business parameter satisfies the second preset condition, and the third business parameter satisfies the third preset condition, determine that the target task has been completed.

[0203] As an optional solution, the above-mentioned device is used to determine that the target task has been completed when the task event parameters meet the task conditions indicated by the task condition parameters in at least one of the following ways: when the target task is a game task, and the task condition parameters indicate that the virtual level of the virtual operation object needs to meet the preset virtual level, determine whether the target virtual level of the target virtual operation object in the task event parameters meets the preset level; when the target virtual level meets the preset virtual level, determine that the target task has been completed; when the target task is a game task, and the task condition parameters indicate that the number of virtual resources held by the virtual operation object needs to meet the preset number of virtual resources, determine whether the target number of virtual resources held by the target virtual operation object in the task event parameters meets the preset number of virtual resources; When the number of virtual resources meets the preset number of virtual resources, it is determined that the target task has been completed; when the target task is a game task, and the task condition parameter indicates that the virtual ranking held by the virtual operation object needs to meet the preset virtual ranking, it is determined whether the target virtual ranking held by the target virtual operation object in the task event parameter meets the preset virtual ranking; when the target virtual ranking meets the preset virtual ranking, it is determined that the target task has been completed; when the target task is a game task, and the task condition parameter indicates that the virtual game duration of the virtual operation object needs to meet the preset virtual game duration, it is determined whether the target virtual game duration of the target virtual operation object in the task event parameter meets the preset virtual game duration; when the target virtual game duration meets the preset virtual game duration, it is determined that the target task has been completed.

[0204] Regarding the device in the above embodiment, the specific manner in which each module performs operations has been described in detail in the embodiment of the method, and will not be elaborated here.

[0205] According to one aspect of the present application, a computer program product is provided, the computer program product comprising a computer program / instruction, the computer program / instruction comprising a program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network via a communication section 1409, and / or installed from a removable medium 1411. When the computer program is executed by a central processor 1401, various functions provided in the embodiments of the present application are executed.

[0206] The serial numbers of the above-mentioned embodiments of the present application are for description only and do not represent the advantages or disadvantages of the embodiments.

[0207] Fig.14 The structure block diagram of a computer system for implementing an electronic device according to an embodiment of the present application is schematically shown.

[0208] It should be noted that Fig.14 The computer system 1400 of the electronic device shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present application.

[0209] like Fig.14 As shown, the computer system 1400 includes a central processing unit 1401 (CPU), which can perform various appropriate actions and processes according to the program stored in the read-only memory 1402 (ROM) or the program loaded from the storage part 1408 to the random access memory 1403 (RAM). Various programs and data required for system operation are also stored in the random access memory 1403. The central processing unit 1401, the read-only memory 1402 and the random access memory 1403 are connected to each other through a bus 1404. An input / output interface 1405 (Input / Output interface, i.e., I / O interface) is also connected to the bus 1404.

[0210] The following components are connected to the input / output interface 1405: an input section 1406 including a keyboard, a mouse, etc.; an output section 1407 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, etc.; a storage section 1408 including a hard disk, etc.; and a communication section 1409 including a network interface card such as a LAN card, a modem, etc. The communication section 1409 performs communication processing via a network such as the Internet. A drive 1410 is also connected to the input / output interface 1405 as needed. A removable medium 1411, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 1410 as needed so that a computer program read therefrom is installed into the storage section 1408 as needed.

[0211] In particular, according to an embodiment of the present application, the process described in each method flow chart can be implemented as a computer software program. For example, an embodiment of the present application includes a computer program product, which includes a computer program carried on a computer readable medium, and the computer program contains a program code for executing the method shown in the flow chart. In such an embodiment, the computer program can be downloaded and installed from the network through the communication part 1409, and / or installed from the removable medium 1411. When the computer program is executed by the central processor 1401, various functions defined in the system of the present application are executed.

[0212] According to another aspect of the embodiment of the present application, an electronic device for implementing the above-mentioned task data processing method is also provided. The electronic device may be Figure 1 The terminal device or server shown in the figure. This embodiment is described by taking the electronic device as a terminal device as an example. Fig.15 As shown, the electronic device includes a memory 1502 and a processor 1504. The memory 1502 stores a computer program, and the processor 1504 is configured to execute the steps in any of the above method embodiments through the computer program.

[0213] Optionally, in this embodiment, the electronic device may be located in at least one network device among a plurality of network devices of a computer network.

[0214] Optionally, in this embodiment, the processor may be configured to perform the following steps through a computer program:

[0215] S1, obtaining a first task event set and a first task set, wherein a task event in the first task event set is pre-set with at least one task in the first task set.

[0216] S2, in the case where the triggering task event list includes the target task event, searching for the target task through the first task event set and the first task set according to the target task event, and determining a matching state of the target task, wherein the target task event has a mapping relationship with the target task, the triggering task event list includes the currently triggered task events, and the matching state is used to indicate whether all the task events having a mapping relationship with the target task have been triggered;

[0217] S3, when all the task events having a mapping relationship with the target task have been triggered, determining the completion status of the target task according to the task condition parameters of the target task and the task event parameters of the target task event.

[0218] Alternatively, a person skilled in the art may understand that: Fig.15 The structure shown is for illustration only, and the electronic device may also be a smart phone (such as an Android phone, an iOS phone, etc.), a tablet computer, a PDA, a mobile Internet device (MID), a PAD, and other terminal devices. Fig.15 The electronic device and the electronic equipment described above are not limited in structure. Fig.15 More or fewer components (such as network interfaces, etc.) as shown in, or with Fig.15 Different configurations are shown.

[0219] Among them, the memory 1502 can be used to store software programs and modules, such as the program instructions / modules corresponding to the method and device for processing task data in the embodiments of the present application. The processor 1504 executes various functional applications and data processing by running the software programs and modules stored in the memory 1502, that is, realizing the above-mentioned method for processing task data. The memory 1502 may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory 1502 may further include a memory remotely located relative to the processor 1504, and these remote memories may be connected to the terminal via a network. Examples of the above-mentioned networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof. Among them, the memory 1502 may be specifically, but not limited to, used to store task events and task information. As an example, such as Fig.15 As shown, the memory 1502 may include but is not limited to the acquisition module 1302, search module 1304 and determination module 1306 in the task data processing device. In addition, it may also include but is not limited to other module units in the task data processing device, which will not be repeated in this example.

[0220] Optionally, the transmission device 1506 is used to receive or send data via a network. Specific examples of the above-mentioned network may include a wired network and a wireless network. In one example, the transmission device 1506 includes a network adapter (Network Interface Controller, NIC), which can be connected to other network devices and routers via a network cable so as to communicate with the Internet or a local area network. In one example, the transmission device 1506 is a radio frequency (RF) module, which is used to communicate with the Internet wirelessly.

[0221] In addition, the electronic device further includes: a display 1508 for displaying the mapping relationship between the task events and the tasks; and a connection bus 1510 for connecting the various module components in the electronic device.

[0222] In other embodiments, the terminal device or server may be a node in a distributed system, wherein the distributed system may be a blockchain system, and the blockchain system may be a distributed system formed by connecting the multiple nodes through network communication. Among them, the nodes may form a peer-to-peer (P2P, Peer To Peer) network, and any form of computing device, such as a server, terminal and other electronic devices, may become a node in the blockchain system by joining the peer-to-peer network.

[0223] According to one aspect of the present application, a computer-readable storage medium is provided, and a processor of a computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device executes the task data processing method provided in various optional implementations of the above-mentioned task data processing.

[0224] Optionally, in this embodiment, the computer-readable storage medium may be configured to store a computer program for performing the following steps:

[0225] S1, obtaining a first task event set and a first task set, wherein a task event in the first task event set is pre-set with at least one task in the first task set.

[0226] S2, in the case where the triggering task event list includes the target task event, searching for the target task through the first task event set and the first task set according to the target task event, and determining a matching state of the target task, wherein the target task event has a mapping relationship with the target task, the triggering task event list includes the currently triggered task events, and the matching state is used to indicate whether all the task events having a mapping relationship with the target task have been triggered;

[0227] S3, when all the task events having a mapping relationship with the target task have been triggered, determining the completion status of the target task according to the task condition parameters of the target task and the task event parameters of the target task event.

[0228] Optionally, in this embodiment, a person of ordinary skill in the art may understand that all or part of the steps in the various methods of the above embodiments may be completed by instructing hardware related to the terminal device through a program, and the program may be stored in a computer-readable storage medium, and the storage medium may include: a flash drive, a read-only memory (ROM), a random access memory (RAM), a disk or an optical disk, etc.

[0229] The serial numbers of the above-mentioned embodiments of the present application are for description only and do not represent the advantages or disadvantages of the embodiments.

[0230] If the integrated units in the above embodiments are implemented in the form of software functional units and sold or used as independent products, they can be stored in the above computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for enabling one or more computer devices (which may be personal computers, servers, or network devices, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present application.

[0231] In the above embodiments of the present application, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, please refer to the relevant description of other embodiments.

[0232] In the several embodiments provided in the present application, it should be understood that the disclosed client can be implemented in other ways. Among them, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of units or modules, which can be electrical or other forms.

[0233] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0234] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0235] The above is only a preferred implementation of the present application. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles of the present application. These improvements and modifications should also be regarded as the scope of protection of the present application.

Claims

1. A method for processing task data, characterized in that: include: Acquire a first task event set and a first task set, wherein a mapping relationship is preset between a task event in the first task event set and at least one task in the first task set; In the case where the triggering task event list includes a target task event, searching for a target task through the first task event set and the first task set according to the target task event, and determining a matching status of the target task, wherein the target task event has the mapping relationship with the target task, the triggering task event list includes currently triggered task events, and the matching status is used to indicate whether all task events having the mapping relationship with the target task have been triggered; In a case where all the task events having the mapping relationship with the target task have been triggered, the completion status of the target task is determined according to the task condition parameter of the target task and the task event parameter of the target task event.

2. The method according to claim 1, characterized in that In the case where the triggering task event list includes a target task event, searching for a target task through the first task event set and the first task set according to the target task event, and determining a matching state of the target task, comprises: Determine a target statistical parameter of the target task according to the first task event set and the first task set, wherein the target statistical parameter is used to represent the total number of task events having the mapping relationship with the target task; In a case where the triggering task event list includes the target task event, determining a target count parameter of the target task, wherein the target count parameter is used to represent the number of the target task events; A matching status of the target task is determined according to the target statistical parameter and the target counting parameter.

3. The method according to claim 2, characterized in that The determining the matching status of the target task according to the target statistical parameter and the target counting parameter includes: In the case where the target statistical parameter and the target counting parameter have the same value, determining that the matching state of the target task is that all task events having the mapping relationship with the target task have been triggered; When the value of the target counting parameter is less than the target statistical parameter, it is determined that the matching state of the target task is that there is an untriggered task event having the mapping relationship with the target task.

4. The method according to claim 3, characterized in that The determining the matching status of the target task according to the target statistical parameter and the target counting parameter includes: In the case where the triggering task event list includes a first task event and a second task event, and the first task set includes a first task and a second task, obtaining a first statistical parameter corresponding to the first task and a second statistical parameter corresponding to the second task, wherein the target statistical parameter includes the first statistical parameter and the second statistical parameter, and the first task and the second task are tasks obtained by searching the first task event and the second task event through the mapping relationship; Determine a first counting parameter of the first task and a second counting parameter of the second task according to the mapping relationship, wherein the target counting parameter includes the first counting parameter and the second counting parameter; In a case where the task events having the mapping relationship with the first task do not include other task events except the first task event and the second task event, determining that the matching state of the first task is that all the task events having the mapping relationship with the first task have been triggered; When the task event having the mapping relationship with the second task also includes other task events except the first task event and the second task event, the matching state of the second task is determined as the existence of an untriggered task event having the mapping relationship with the second task.

5. The method according to claim 2, characterized in that: The step of determining the target statistical parameter of the target task according to the first task event set and the first task set includes: Searching for the target task in the first task set; When the target task is found, the number of task events in the first task event set that have the mapping relationship with the target task is determined according to the mapping relationship, and the number of task events is determined as the target statistical parameter.

6. The method according to claim 2, characterized in that In the case where the triggering task event list includes the target task event, determining the target counting parameter of the target task includes: In the process of processing the target task event, adding the target task event to the trigger task event list; In a case where the triggering task event list includes the target task event, the target counting parameter of the target task is determined according to the number of the target task events in the triggering task event list.

7. The method according to claim 1, characterized in that The obtaining of the first task event set and the first task set includes: Obtain a preconfigured second task event set and a second task set; Establishing an inverse relationship between the second task event set and the second task set, wherein the inverse relationship includes a corresponding relationship between a task event in the second task event set and a task subset in the second task set; Deduplication operations are performed on the task identifiers in the multiple task subsets according to the inverse relationship to determine a target task data organization structure, wherein the target task data organization structure includes the first task event set, the first task set and the mapping relationship, and each task identifier in the target task data organization structure is unique.

8. The method according to claim 1, characterized in that The step of determining the completion status of the target task according to the task condition parameter of the target task and the task event parameter of the target task event when all the task events having the mapping relationship with the target task have been triggered includes: Acquire the task condition parameter and the task event parameter; In the case where the task event parameter satisfies the task condition indicated by the task condition parameter, determining that the target task has been completed; When the task event parameter does not satisfy the task condition indicated by the task condition parameter, it is determined that the target task is not completed.

9. The method according to claim 8, characterized in that When the task event parameter satisfies the task condition indicated by the task condition parameter, determining that the target task has been completed includes at least one of the following: In the case where the task condition parameter indicates that the value of the first business parameter needs to meet the first preset condition, determining whether the value of the first business parameter in the task event parameter meets the first preset condition, wherein the business parameter generated by the target task event includes the first business parameter; in the case where the first business parameter in the task event parameter meets the first preset condition, determining that the target task has been completed; In a case where the task condition parameter indicates that the type of the second business parameter needs to meet the second preset condition, determining whether the type of the second business parameter in the task event parameter meets the second preset condition, wherein the business parameter generated by the target task event includes the second business parameter; and in a case where the second business parameter in the task event parameter meets the second preset condition, determining that the target task has been completed; When the task condition parameter indicates that the object to which the third business parameter belongs needs to meet the third preset condition, determine whether the object to which the third business parameter in the task event parameter belongs meets the third preset condition, wherein the business parameters generated by the target task event include the third business parameter; when the third business parameter in the task event parameter meets the third preset condition, determine that the target task has been completed.

10. The method according to claim 8, characterized in that The step of determining that the target task has been completed when the task event parameter satisfies the task condition indicated by the task condition parameter includes: In the case where the task condition parameter indicates that the value of the first business parameter needs to meet the first preset condition, determining whether the value of the first business parameter in the task event parameter meets the first preset condition, wherein the business parameter generated by the target task event includes the first business parameter; In the case where the task condition parameter indicates that the type of the second business parameter needs to meet a second preset condition, determining whether the type of the second business parameter in the task event parameter meets the second preset condition, wherein the business parameter generated by the target task event includes the second business parameter; In the case where the task condition parameter indicates that the object to which the third business parameter belongs needs to meet the third preset condition, determining whether the object to which the third business parameter belongs in the task event parameter meets the third preset condition, wherein the business parameter generated by the target task event includes the third business parameter; When the first business parameter in the task event parameter satisfies the first preset condition, the second business parameter satisfies the second preset condition, and the third business parameter satisfies the third preset condition, it is determined that the target task has been completed.

11. The method according to any one of claims 1 to 10, characterized in that When the task event parameter satisfies the task condition indicated by the task condition parameter, determining that the target task has been completed includes at least one of the following: When the target task is a game task and the task condition parameter indicates that the virtual level of the virtual operation object needs to meet a preset virtual level, determining whether the target virtual level of the target virtual operation object in the task event parameter meets the preset level; When the target virtual level meets the preset virtual level, determining that the target task has been completed; When the target task is a game task and the task condition parameter indicates that the number of virtual resources held by the virtual operation object needs to meet the preset number of virtual resources, determining whether the target number of virtual resources held by the target virtual operation object in the task event parameter meets the preset number of virtual resources; When the target virtual resource quantity meets the preset virtual resource quantity, determining that the target task has been completed; When the target task is a game task and the task condition parameter indicates that the virtual ranking held by the virtual operation object needs to meet a preset virtual ranking, determining whether the target virtual ranking held by the target virtual operation object in the task event parameter meets the preset virtual ranking; When the target virtual ranking satisfies the preset virtual ranking, determining that the target task has been completed; When the target task is a game task and the task condition parameter indicates that the virtual game duration of the virtual operation object needs to meet the preset virtual game duration, determining whether the target virtual game duration of the target virtual operation object in the task event parameter meets the preset virtual game duration; When the target virtual game duration meets the preset virtual game duration, it is determined that the target task has been completed.

12. A task data processing device, characterized in that: include: An acquisition module, used for acquiring a first task event set and a first task set, wherein a mapping relationship is preset between a task event in the first task event set and at least one task in the first task set; A search module, used for searching for a target task through the first task event set and the first task set according to the target task event, and determining a matching status of the target task when the triggering task event list includes a target task event, wherein the target task event has the mapping relationship with the target task, the triggering task event list includes currently triggered task events, and the matching status is used to indicate whether all task events having the mapping relationship with the target task have been triggered; The determination module is used to determine the completion status of the target task according to the task condition parameters of the target task and the task event parameters of the target task event when all the task events having the mapping relationship with the target task have been triggered.

13. A computer-readable storage medium, characterized in that: The computer-readable storage medium includes a stored program, wherein the program can be executed by a terminal device or a computer to execute the method described in any one of claims 1 to 11.

14. A computer program product comprising a computer program / instructions, characterized in that When the computer program / instructions are executed by a processor, the steps of the method described in any one of claims 1 to 11 are implemented.

15. An electronic device comprising a memory and a processor, characterized in that: A computer program is stored in the memory, and the processor is configured to execute the method according to any one of claims 1 to 11 through the computer program.

Images