Task processing method, apparatus, device, storage medium, and product

Abstract

The application discloses a task processing method and device, equipment, storage medium and product, and belongs to the computer technical field. The method comprises the following steps: acquiring task configuration information; in response to a task issuing instruction for a target client, acquiring task attribute information corresponding to a target serial task from the task configuration information; determining a subtask corresponding to the target serial task according to the task attribute information; generating task taking information corresponding to the target serial task based on the subtask; and sending the task taking information to the target client. In the technical scheme provided by the application, for each serial task, the subtask corresponding to the serial task can be determined according to the task attribute information of the serial task in the task configuration information, and then the task taking information of the serial task is generated according to the subtask and sent to the client, so that the client takes the serial task. Through the universal task processing process, the program logic development and planning configuration work of the task system are separated, and the application development efficiency is improved.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular to a task processing method, apparatus, device, storage medium, and product. Background Technology

[0002] In recent years, with the rapid development of the Internet and computer technology, video games have become increasingly popular among users, the variety of game products has become more and more abundant, and the task of game development has become more and more demanding.

[0003] In related technologies, when developing a game, game designers usually need to design and arrange game tasks. After the game designers design the game task plan, the game developers determine the program code to implement the various game tasks based on the task plan. After debugging and acceptance, the developed game is then put into use.

[0004] However, during game development, game task requirements change frequently. Using the above development process requires frequent modifications to the overall game program code, which increases the probability of errors, makes the game development workload heavy, and reduces game development efficiency. Summary of the Invention

[0005] This application provides a task processing method, apparatus, device, storage medium, and product that can separate the program logic development and planning configuration work of a task system, avoid unnecessary runtime errors, reduce the workload of game development tasks, and improve the overall application development efficiency and task processing efficiency.

[0006] According to one aspect of the embodiments of this application, a task processing method is provided, the method comprising:

[0007] Get task configuration information;

[0008] In response to a task instruction issued to a target client, the task attribute information corresponding to the target chain task is obtained from the task configuration information. The target chain task refers to any chain task in at least one chain task. The chain task refers to a chain task composed of at least two sub-tasks.

[0009] Based on the task attribute information, determine the sub-tasks corresponding to the target chain task;

[0010] Based on the sub-tasks, generate task acceptance information corresponding to the target chain task;

[0011] Send the task acceptance information to the target client.

[0012] According to one aspect of the embodiments of this application, a task processing apparatus is provided, the apparatus comprising:

[0013] The configuration information acquisition module is used to acquire task configuration information;

[0014] The task attribute determination module is used to respond to the task issuance instruction for the target client and obtain the task attribute information corresponding to the target chain task from the task configuration information. The target chain task refers to any chain task in at least one chain task. The chain task refers to a chain task composed of at least two sub-tasks.

[0015] The subtask determination module is used to determine the subtasks corresponding to the target chain task based on the task attribute information.

[0016] The task information generation module is used to generate task acceptance information corresponding to the target chain task based on the sub-task;

[0017] The task information delivery module is used to send the task acceptance information to the target client.

[0018] According to one aspect of the embodiments of this application, a computer device is provided, the computer device including a processor and a memory, the memory storing at least one instruction, at least one program, code set or instruction set, the at least one instruction, the at least one program, the code set or instruction set being loaded and executed by the processor to implement the above-described task processing method.

[0019] According to one aspect of the embodiments of this application, a computer-readable storage medium is provided, wherein the storage medium stores at least one instruction, at least one program, code set, or instruction set, wherein the at least one instruction, the at least one program, the code set, or the instruction set is loaded and executed by a processor to implement the above-described task processing method.

[0020] According to one aspect of the embodiments of this application, a computer program product is provided, the computer program product including computer instructions stored in a computer-readable storage medium, a processor of a computer device reading the computer instructions from the computer-readable storage medium, and the processor executing the computer instructions to cause the computer device to perform the above-described task processing method.

[0021] The technical solution provided in this application can bring the following beneficial effects:

[0022] By abstracting a general chain task processing mechanism, tasks are flexibly managed through configuration. For each chain task, the corresponding subtasks can be determined based on the task attribute information of the chain task in the task configuration information. Then, task acceptance information for the chain task is generated based on the subtasks and sent to the client, allowing the client to accept the corresponding chain task. In this way, even if task requirements change, only the corresponding task configuration information needs to be modified, without adjusting the overall application program code. This effectively separates the program logic development of the task system from the planning and configuration work, avoiding unnecessary runtime errors, reducing the workload of game development tasks, and improving the overall application development efficiency and task processing efficiency. Attached Figure Description

[0023] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0024] Figure 1 This is a schematic diagram of an application runtime environment provided in one embodiment of this application;

[0025] Figure 2 This is a flowchart of a task processing method provided in one embodiment of this application. Figure 1 ;

[0026] Figure 3 This is a flowchart of a task processing method provided in one embodiment of this application. Figure 2 ;

[0027] Figure 4 This is a flowchart of a task processing method provided in one embodiment of this application. Figure 3 ;

[0028] Figure 5 An example is shown in the flowchart of randomly issuing loop tasks based on task selection conditions;

[0029] Figure 6 An exemplary flowchart illustrating the process of determining subtasks within a ring task is provided.

[0030] Figure 7 An exemplary flowchart is shown for determining the ring task in a ring chain task;

[0031] Figure 8 This is a flowchart of a task processing method provided in one embodiment of this application. Figure 4 ;

[0032] Figure 9This example illustrates a schematic diagram of the user's interaction flow when accepting a task in a game application;

[0033] Figure 10 This is a block diagram of a task processing apparatus provided in one embodiment of this application;

[0034] Figure 11 This is a structural block diagram of a computer device provided in one embodiment of this application. Detailed Implementation

[0035] To make the objectives, technical solutions, and advantages of this application clearer, the embodiments of this application will be described in further detail below with reference to the accompanying drawings.

[0036] Please refer to Figure 1 This diagram illustrates an application runtime environment provided in one embodiment of this application. The application runtime environment may include: terminal 10 and server 20.

[0037] Terminal 10 can be an electronic device such as a mobile phone, tablet computer, game console, e-book reader, multimedia playback device, wearable device, PC (Personal Computer), intelligent voice interaction device, smart home appliance, or in-vehicle terminal. Application clients can be installed on terminal 10.

[0038] In this embodiment, the application can be any application that loads application tasks. Typically, the application is a game application, such as a multiplayer online battle arena (MOBA) game, a battle royale (BR) game, a third-person shooter (TPS) game, a first-person shooter (FPS) game, and a multiplayer shooting survival game, etc. Of course, in addition to game applications, other types of applications can also load application tasks. For example, news applications, social applications, interactive entertainment applications, browser applications, shopping applications, content sharing applications, virtual reality (VR) applications, augmented reality (AR) applications, etc., which are not limited in this embodiment. Optionally, the terminal 10 runs a client of the above-mentioned application.

[0039] Server 20 provides background services to clients of applications in terminal 10. For example, server 20 can be a background server for the aforementioned applications. Server 20 can be a standalone physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server providing basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDN (Content Delivery Network), and big data and artificial intelligence platforms. Optionally, server 20 can simultaneously provide background services to applications in multiple terminals 10.

[0040] Optionally, terminal 10 and server 20 can communicate with each other via network 30. Terminal 10 and server 20 can be directly or indirectly connected via wired or wireless communication, which is not limited herein.

[0041] Please refer to Figure 2 It illustrates the flow of a task processing method provided in one embodiment of this application. Figure 1 This method can be applied to computer devices, which refer to electronic devices with data computing and processing capabilities. For example, the entity executing each step can be... Figure 1 The application runtime environment shown is a terminal 10 or a server 20. The method may include the following steps (210-250).

[0042] Step 210: Obtain task configuration information.

[0043] The aforementioned task configuration information includes configuration information corresponding to at least one task in the target application. This task configuration information is stored in at least one task configuration table.

[0044] The aforementioned tasks include, but are not limited to, single tasks and chained tasks. A single task refers to a standalone task. A chained task refers to a set of tasks consisting of at least two sub-tasks.

[0045] The aforementioned chain tasks include, but are not limited to, ring tasks and chained tasks. A ring task refers to a chain of tasks consisting of at least two individual tasks. Optionally, a ring task is a series of sub-tasks flexibly configured and executed by the planner, which can be completed a limited number of times or in an infinite loop. A chained task refers to a chain of tasks including at least one ring task; that is, the sub-tasks of a chained task include at least one ring task, forming a complex, nested chain task. Optionally, a chained task is a series of ring tasks flexibly configured and executed by the planner based on a ring task, where each ring task consists of multiple sub-tasks.

[0046] In an exemplary embodiment, the task configuration information includes task attribute information corresponding to at least one task. The task attribute information includes various attribute data corresponding to the task. Optionally, the task attribute information includes attribute data such as task identifier, task type, task name, task content, task location, and task pool identifier.

[0047] In one example, the target application mentioned above is a game application. Correspondingly, the task mentioned above is a game task. Table 1 below exemplarily shows a task attribute table corresponding to a game task in a game application. In Table 1, the task with task identifier 298300 is a shell task of a ring task. A ring task consists of at least two individual tasks, and the shell task represents the ring task logically and holistically. The shell task identifier (Shell_ID(Identity Document)) corresponding to the shell task is the ring task identifier. Random task pool identifier 64 is the task pool identifier corresponding to shell task 298300. The above task pool identifier can be randomly generated during logical processing, and therefore can be called a random task pool identifier in Table 1, belonging to one type of task pool identifier. The task pool identifier can also be fixedly configured; this application embodiment does not limit this. Tasks 298301 to 298354 shown in Table 1 are all tasks of ring tasks, corresponding to the corresponding shell task 298300. Additionally, the maximum number of tasks per round for shell task 298300 in Table 1 is 13, which refers to the maximum number of individual tasks in a single round of ring tasks. This can be configured according to specific application scenarios. The task type, task panel category, task description (task interface), and ring task sequence pool identifier in Table 1 are all task attribute data corresponding to the task in the application. Since task 298300 is a shell task of a ring task, it may not have a corresponding ring task sequence pool identifier. Similar to ring tasks, ring tasks also correspond to a shell task. The shell task identifier (CycleChain_ID) of a ring task is the ring task identifier of the ring task. The ring task sequence pool identifier mentioned above is the task pool identifier corresponding to the shell task of the ring task.

[0048] Table 1

[0049]

[0050] In an exemplary embodiment, the task configuration information includes task pool information, which indicates task information corresponding to at least one task pool. At least one task in the target application can be divided into different task pools for management, facilitating task retrieval during task processing and eliminating the need to operate from all tasks, thus improving the flexibility and efficiency of task processing.

[0051] Optionally, the task pool information mentioned above includes the task pool identifier, task pool type, and some or all of the task attribute data of the tasks contained in each task pool, such as task identifier, task level, and other task attribute data.

[0052] In the previous example where the target application was a game application, the task configuration information also included a task pool information table. Table 2 below exemplifies a task pool information table in a game application. Table 2 below is the task pool information table corresponding to the task pool with random task pool identifier 64. The task pool identifier corresponding to 298300 in Table 1 above is a random task pool identifier encoded as 64. Therefore, the task pool information table shown in Table 2 below can be determined through the above encoding 64. Table 2 includes task pool attribute data, such as task pool identifier and task pool type. The ring task sequence pool is the task pool corresponding to the ring task. In addition to the task pool attribute data, Table 2 also includes task information for each subtask in the ring task corresponding to shell task 298300. For example, task identifier, the number of rings in the ring task, the configuration probability corresponding to the task, task name, task level range, and task group identifier, etc.

[0053] Optionally, the task information of the subtasks corresponding to the chain tasks can be configured in the task pool information table.

[0054] Table 2

[0055]

[0056]

[0057] In an exemplary embodiment, the task configuration information also includes resource information corresponding to the task. This resource information refers to the attribute information of the resources sent to the client after the task execution is completed. The storage format of this resource information includes a resource information table.

[0058] In the previous example where the target application was a game application, the task configuration information also included a resource information table. Table 3 below exemplifies a resource information table in a game application. In a game application, the resources issued can be virtual resources, including but not limited to virtual items. Correspondingly, the resource information table can also be called a task reward table, in which chain tasks can be configured, specifically configuring the issuance of rewards on certain links of the chain tasks. In the table below, reward identifier 1, reward identifier 2, and additional reward identifier are the reward resources corresponding to the task. Optionally, the resource information corresponding to the additional reward identifier is only issued to specific objects. In addition, the minimum level and maximum level in Table 3 are the restriction levels corresponding to the reward issuance.

[0059] Table 3

[0060]

[0061]

[0062]

[0063] By configuring the task identifier and corresponding task pool of the chain task in the task configuration information, and selecting the subtasks of the chain task from the task pool, the flexible configuration of the chain task can be effectively supported. The task system can call the task configuration information at any time to generate and issue different chain tasks.

[0064] Step 220: In response to the task instruction issued to the target client, obtain the task attribute information corresponding to the target chain task from the task configuration information.

[0065] A target chain task refers to any one of the chain tasks in at least one chain task. A chain task refers to a chain task consisting of at least two sub-tasks.

[0066] The target client mentioned above is any client logged into with any account of the target application. Any client can accept the chain of tasks.

[0067] In one possible implementation, the user performs a corresponding operation on the client, triggering the task conditions for accepting a series of tasks. The client can send a task acceptance request to the server, and upon receiving the request, the server can generate the task issuance instruction. It should be noted that there are various ways to generate the task issuance instruction; it can also be generated when the task execution progress reaches a target position or time reaches a target time. This embodiment of the application does not limit this approach.

[0068] Upon detecting the aforementioned task issuance instruction, the task attribute information corresponding to the target chain task is obtained from the task configuration information. Optionally, the aforementioned task attribute information is stored in a task attribute information table. The task attribute information table is determined from at least one task configuration table, and subsequent operations can be performed based on the task attribute information of the target chain task.

[0069] The aforementioned task attribute information includes, but is not limited to, the task identifier, subtask identifier, task level, task group, and task chain position.

[0070] Step 230: Based on the task attribute information, determine the sub-tasks corresponding to the target chain task.

[0071] After obtaining the above task attribute information, the sub-tasks corresponding to the target chain task can be determined based on the various attribute data of the target chain task.

[0072] Based on the task attribute information above, the task type of the target chain task can be determined. These task types include loop tasks and chained tasks.

[0073] Optionally, the task attribute information mentioned above includes a task type field. If the task type field is the type field corresponding to a loop task, then the target loop task can be determined to be a loop task; if the task type field is the type field corresponding to a chain task, then the target loop task can be determined to be a chain task.

[0074] In an exemplary embodiment, the target chain task is a ring task, which refers to a chain of tasks consisting of at least two individual tasks. The task attribute information includes the ring task identifier corresponding to the ring task. Accordingly, such as Figure 3 As shown, the implementation process of step 230 above includes the following steps (231-232). Figure 3 The flowchart of a task processing method provided in one embodiment of this application is shown. Figure 2 .

[0075] Step 231: If the target chain task is a ring task, determine the task set corresponding to the ring task based on the ring task identifier.

[0076] In the aforementioned task attribute information, the task identifier of the shell task corresponding to the ring task is obtained, and the task identifier of the shell task can be used as the ring task identifier. In one possible implementation, the ring task identifier is Shell_ID, which can be used as the primary key of the ring task to distinguish different ring tasks.

[0077] Based on the task identifier of the aforementioned shell task, the set of tasks corresponding to that task identifier can be determined. This set of tasks refers to the set corresponding to some or all tasks in the target application.

[0078] By setting a ring task identifier for the ring task in the task configuration information, the task system can easily obtain the ring task identifier to determine the task set of the ring task. In the task processing scenario, each ring task can be called according to a ring task identifier, avoiding the need to modify the entire program code.

[0079] In an exemplary embodiment, the task configuration information includes task pool information, which indicates task information corresponding to at least one task pool. Accordingly, such as... Figure 4 As shown, step 231 above can be replaced by the following steps (231a to 231c). Figure 4 The flowchart of a task processing method provided in one embodiment of this application is shown. Figure 3 .

[0080] Step 231a: If the target chain task is a ring task, obtain the task pool identifier corresponding to the ring task identifier.

[0081] In one possible implementation, the task configuration information pre-configures a corresponding task pool for the ring task, so the task pool identifier corresponding to the ring task identifier can be determined based on the ring task identifier.

[0082] In another possible implementation, the task pool identifier is a randomly generated identifier code. In the example where the target application is a game application, the task pool identifier can be a random task pool identifier from Table 1 above.

[0083] Optionally, the number of task pool identifiers mentioned above is greater than or equal to 1, that is, the ring task identifier corresponds to at least one task pool identifier.

[0084] Step 231b: Determine the task pool corresponding to the ring task based on the task pool identifier and task pool information.

[0085] The task pool information mentioned above includes task information for each task pool. Therefore, based on the task pool identifier, the task pool corresponding to that identifier, and the task information of the tasks contained in that task pool, can be determined.

[0086] Step 231c: Identify the tasks corresponding to the task pool as tasks in the task set.

[0087] By determining the task pool corresponding to the chain task in the task configuration information and selecting the sub-tasks of the chain task from the task pool, different chain tasks can be managed in a unified manner. Even if the chain tasks are changed, added or deleted, the above chain task determination process can still be applied, ensuring the separation between task planning and configuration and program logic development.

[0088] In one possible implementation, all tasks in the task pool are subtasks of the aforementioned ring task.

[0089] In another possible implementation, the subtasks of the aforementioned ring task can be selected from the aforementioned task pool, thereby enabling flexible configuration of the ring task. In the event of task changes, there is no need to modify the underlying application code and task flow system; only the task configuration information needs to be adjusted to adjust the tasks contained in the task pool, thus enabling flexible configuration of the ring task.

[0090] Step 232: Filter the tasks in the task set that meet the task filtering conditions to obtain the subtasks corresponding to the ring task.

[0091] Based on the preset task filtering conditions, the tasks in the above task set are filtered out, and the tasks that do not meet the task filtering conditions are removed. The tasks that meet the task filtering conditions can be used as the sub-tasks corresponding to the above ring tasks.

[0092] In an exemplary embodiment, the task configuration information includes at least one task level, task group, and task chain position corresponding to a task, and the task filtering conditions include at least one of task level conditions, task grouping conditions, and task chain position conditions.

[0093] Among them, the task level condition is that the task level belongs to the target level, the task grouping condition is that the task group belongs to the target group, and the task position condition is that the task chain position is in the target position.

[0094] When the task filtering criteria include a task level condition, tasks in the task set whose task level does not belong to the target level are filtered out, and tasks whose task level belongs to the target level are obtained and treated as subtasks corresponding to the loop tasks. Optionally, the aforementioned target level is a preset level.

[0095] When the task filtering criteria include task grouping criteria, tasks in the task set whose task group does not belong to the target group are filtered out, and tasks whose task group belongs to the target group are obtained and treated as subtasks corresponding to the loop tasks. Optionally, the aforementioned target group is a preset task group.

[0096] When the task filtering criteria include task location, tasks whose task chain position is not at the target position are filtered out from the task set, leaving tasks whose task chain position is at the target position, and these are taken as subtasks corresponding to the ring task. Optionally, the target position is a preset task chain position. The task chain position can be the ring number of the task within the ring task.

[0097] It should be noted that the task filtering conditions include, but are not limited to, the three filtering conditions mentioned above. In specific application scenarios, the three conditions can be randomly combined, and conditions can be added according to actual needs. This application embodiment does not limit this.

[0098] In one example, such as Figure 5 As shown, it exemplifies a flowchart of randomly issuing loop tasks based on task selection conditions. Figure 5 The steps for randomly issuing loop tasks based on task selection conditions, as shown, include the following steps S1 to S10.

[0099] S1, the client initiates a request to accept the task.

[0100] S2 retrieves the task pool identifier, current account level, current task group, and current task chain number.

[0101] S3. Determine if a task pool corresponding to the task pool identifier exists. If yes, proceed to step S4; otherwise, proceed to step S10.

[0102] S4. Determine if there is a task in the task pool that corresponds to the current account level. If yes, proceed to step S5; otherwise, proceed to step S10.

[0103] The current account level can be used as a condition for setting the target level for tasks, thereby filtering tasks in the task pool.

[0104] S5. Determine if there is a task corresponding to the current task group. If yes, proceed to step S7; otherwise, proceed to step S6.

[0105] The current task group can be used as a target group to form task grouping conditions, thereby filtering tasks in the task pool.

[0106] S6: Randomly select a group of tasks with the same task group from the multiple tasks that have been found so far.

[0107] If there are no tasks in the current task group in the task pool, tasks in the same group can be randomly selected from the task pool to ensure that the selected tasks are from the same group.

[0108] S7. Determine if a task corresponding to the current task chain cycle number exists. If yes, proceed to step S8; otherwise, proceed to step S10.

[0109] The current task chain number can be used as a condition for determining the target location and thus filtering tasks in the task pool.

[0110] S8: Among the multiple tasks that meet the current task selection criteria, randomly determine the target subtask in the ring task according to the configuration probability corresponding to each task.

[0111] The aforementioned configuration probabilities can be preset probability values ​​used to determine the target subtask in the ring task. The target subtask can be any subtask within the ring task. Since the ring task typically executes each subtask sequentially, the target subtask can be sent to the client for processing first, without needing to send all subtasks at once. Furthermore, the subtasks of the ring task are flexibly configurable; the next subtask can be determined based on the execution result of the previous subtask.

[0112] S9 sends the task acceptance information for the target subtask to the client.

[0113] The task information of the target subtask is sent to the client as task acceptance information.

[0114] S10, End.

[0115] By filtering tasks in the task pool using task filtering criteria, different combinations of chain tasks can be obtained. When the requirements of chain tasks change and reconfiguration is required, the chain tasks can be configured simply by adjusting the task filtering criteria in the task configuration information, without modifying the program code, thus reducing the repetitive development process.

[0116] In one example, such as Figure 6 As shown, this example illustrates a flowchart for determining subtasks within a ring task. The client triggers task conditions, accepts the ring task, and sends a task acceptance request to the server. The server generates a corresponding ring task pool identifier (iPool_ID) using a ring task identifier, i.e., the ring task's shell task ID. Based on the task filtering conditions configured by the planner, a series of subtasks meeting the filtering conditions are selected from the corresponding ring task pool, such as... Figure 6 The diagram shows subtasks 1, 2, and 3. Simultaneously, a successful task acceptance reply message is sent to the client, at which point the client accepts the ring task. The ring task identifier Shell_ID serves as the primary key for distinguishing different ring tasks; the ring task pool identifier iPool_ID is used to determine the task pool corresponding to the ring task.

[0117] In an exemplary embodiment, the target chain task is a ring-chain task, which refers to a chain of tasks including at least one ring task. The task attribute information includes the ring-chain task identifier corresponding to the ring-chain task. Accordingly, such as Figure 3 As shown, the implementation process of step 230 above also includes the following steps (233 to 236).

[0118] Step 233: If the target chain task is a chain task, determine the task set corresponding to the chain task based on the chain task identifier.

[0119] From the aforementioned task attribute information, the task identifier of the shell task corresponding to the aforementioned ring task is obtained, i.e., the ring task identifier. In one possible implementation, the ring task identifier is CycleChain_ID, which can serve as the primary key of the ring task to distinguish different ring tasks.

[0120] Based on the aforementioned ring-chain task identifier, the task set corresponding to that identifier can be determined. This task set refers to the set corresponding to some or all tasks in the target application. The task set includes both ring tasks and individual tasks.

[0121] In an exemplary embodiment, the ring task pool identifier corresponding to the ring chain task identifier is obtained; based on the ring task pool identifier and task pool information, the ring task pool corresponding to the ring chain task is determined; and the task corresponding to the ring task pool is identified as a task in the task set. The aforementioned ring task pool refers to a task pool that simultaneously contains ring tasks and individual tasks.

[0122] In one possible implementation, the task configuration information pre-configures a corresponding ring task pool for the ring task, so the ring task pool identifier corresponding to the ring task identifier can be determined based on the ring task identifier.

[0123] In another possible implementation, the ring task pool identifier is a randomly generated identifier code. In the example where the target application is a game application, the ring task pool identifier can be the ring chain task sequence pool identifier in Table 1 above. Optionally, the number of ring task pool identifiers is greater than or equal to 1, that is, the ring chain task identifier corresponds to at least one ring task pool identifier.

[0124] The aforementioned task pool information includes task information for each task pool, including task information for ring task pools. Therefore, based on the aforementioned ring task pool identifier, the ring task pool corresponding to that identifier, as well as the task information of the tasks contained in that ring task pool, can be determined.

[0125] In one possible implementation, the ring tasks and individual tasks in the ring task pool are all sub-tasks of the ring chain task.

[0126] In another possible implementation, the subtasks of the aforementioned chain task can be selected from the chain tasks and individual tasks in the task pool, thereby enabling flexible configuration of the chain task. In the event of task changes, there is no need to modify the underlying application code and task flow system; only the task configuration information needs to be adjusted to adjust the tasks contained in the task pool, thus enabling flexible configuration of the chain task.

[0127] Step 234: Filter the ring tasks in the task set that meet the task filtering conditions to obtain the ring tasks corresponding to the ring chain tasks.

[0128] The task selection criteria have been explained above and will not be repeated here. After filtering out ring tasks that do not meet the selection criteria, the remaining ring tasks that do meet the criteria can be considered as the ring tasks corresponding to the ring chain tasks. The ring tasks corresponding to the aforementioned ring chain tasks include ring tasks whose task level belongs to the target level, ring tasks whose task group belongs to the target group, and ring tasks whose task chain position is at the target position, etc. This application embodiment does not impose restrictions on the task selection criteria.

[0129] By configuring the ring task identifier and the corresponding ring task task pool in the task configuration information, different ring tasks can be implemented, which can meet the management needs of complex nested chain tasks. No matter how complex the ring task is, it can be successfully implemented through the above general ring task subtask determination process. When the ring task changes, the program code can be kept universal and the code duplication can be avoided.

[0130] In one example, such as Figure 7 As shown, this example illustrates a flowchart for determining ring tasks within a chain of tasks. The client triggers task conditions, accepts the chain task, and sends a task acceptance request to the server. The server generates a corresponding chain task pool identifier, iChainPool_ID, using a chain task identifier, i.e., the shell task identifier (CycleChain_ID). Based on the task filtering conditions configured by the planner, a series of ring tasks meeting the conditions are selected from the corresponding chain task pool, such as... Figure 7 As shown in the diagram, ring tasks 1, 2, and 3 are assigned. Simultaneously, a successful task acceptance reply message is sent to the client, thus allowing the client to accept the ring chain tasks. The ring chain task identifier, CycleChain_ID, serves as the primary key for distinguishing different ring chain tasks; the ring chain task pool, iChainPool_ID, is used to identify the corresponding ring chain task pool.

[0131] Step 235: Determine the subtasks corresponding to each ring task in the ring chain task.

[0132] For any ring task in the ring task corresponding to the ring task, the execution starts from the step of determining the task set corresponding to the ring task based on the ring task identifier, and then determines the subtasks corresponding to each ring task in the ring task.

[0133] For each subtask in the chain task, the execution begins with the step of determining the task set corresponding to the chain task based on the chain task identifier. That is, the task set corresponding to each chain task is determined based on the chain task identifier; tasks that meet the task filtering conditions in the task set are filtered to obtain the subtask corresponding to each chain task.

[0134] In one possible implementation, the task pool identifier corresponding to the ring task identifier of each ring task is obtained; based on the task pool identifier and task pool information corresponding to each ring task, the task pool corresponding to each ring task is determined; the tasks corresponding to the task pool are determined as tasks in the task set corresponding to each ring task; the tasks in the task set that meet the task filtering conditions are filtered to obtain the sub-tasks corresponding to each ring task.

[0135] Step 236: Take the subtask corresponding to each ring task in the ring task as the subtask corresponding to the ring task.

[0136] In an exemplary embodiment, such as Figure 3 As shown, the steps following step 233 are as follows (237-238).

[0137] Step 237: Filter individual tasks in the task set that meet the task filtering criteria to obtain the individual tasks corresponding to the chain tasks.

[0138] In some possible implementations, a ring chain task can be a chain of tasks composed of individual tasks and ring tasks. This means that the subtasks of a ring chain task are not only ring tasks, but may also include individual tasks as a link in the task chain. Through step 237, the corresponding individual tasks in the ring chain task can be determined.

[0139] Step 238: Treat the individual tasks corresponding to the chain task as subtasks corresponding to the chain task.

[0140] Step 240: Based on the subtasks, generate task acceptance information corresponding to the target chain tasks.

[0141] Optionally, the above subtasks include each subtask under a ring task, as well as each ring task and individual task under a ring chain task.

[0142] The aforementioned task acceptance information refers to the response information indicating that the target chain task has been assigned to the target client for execution. In some possible implementations, the target chain tasks are processed and executed sequentially, and the client side will not complete the subtasks in the target chain task simultaneously. Therefore, the aforementioned task acceptance information indicates that the target chain task has been assigned to the target client, instructing the target client to accept and execute the chain task.

[0143] In one possible implementation, the next subtask is determined by configuring the probabilities of each subtask. These configuration probabilities can be preset probability values ​​used to identify the target subtask within the chain of tasks. Optionally, the task information of the current subtask is added to the task acceptance information and sent to the client all at once. The client can then process and complete the next subtask. The client does not need to process all the subtasks in the chain of tasks at once, and the subtasks in the chain of tasks are flexibly configured, allowing the next subtask to be determined based on the execution result of the previous subtask.

[0144] Step 250: Send task acceptance information to the target client.

[0145] In an exemplary embodiment, the task configuration information includes resource information corresponding to the target chain task. Accordingly, such as... Figure 8 As shown, after step 250, the method further includes the following steps (260-270). Figure 8The flowchart of a task processing method provided in one embodiment of this application is shown. Figure 4 .

[0146] Step 260: In response to the task completion instruction of the target subtask in the target chain task, determine the resource information corresponding to the target subtask from the resource information.

[0147] The aforementioned target subtask refers to any subtask in a chain of target tasks.

[0148] Optionally, the resource identifier corresponding to the target subtask can be determined from the resource information table based on the task identifier corresponding to the target subtask.

[0149] Step 270: Send the resource information corresponding to the target subtask to the target client.

[0150] Optionally, the resource information corresponding to the above resource identifier can be sent to the target client, or bound to the target account logged into the target client.

[0151] In one example, such as Figure 9 As shown, it exemplifies the interactive flow diagram of a user accepting a task in a game application. Figure 9 In the interactive flow shown, the user performs actions on the game client. When the client-side meets the task triggering conditions, it triggers the task acceptance mechanism, sending a request to the server to accept the task. Task triggering conditions include, but are not limited to, conditional triggering, regular triggering, random triggering, and chain task formats. Task triggering methods include, but are not limited to, non-player character triggering, area triggering, and time triggering. Non-player character triggering means the user receives the task from a non-player character; area triggering means the task is triggered upon the user entering a specific area; and time triggering means the user receives the task after a preset time.

[0152] After a user accepts a sub-task, the client can synchronize the task progress with the server during the user's operation and request task updates at any time. Correspondingly, the server, upon receiving the request, will send an updated task response to the client until the user achieves the completion objectives corresponding to the chain of tasks. At this point, the server issues a task completion response and distributes the task rewards. Task completion conditions include, but are not limited to, reaching a certain number of virtual objects killed, completing the task within the set time, clearing the entire dungeon, and collecting virtual items to meet the task requirements. Task completion methods include, but are not limited to, combat, item collection, quest exploration, and dialogue.

[0153] In summary, the technical solution provided in this application, through an abstracted and general chain task processing mechanism, flexibly manages tasks through configuration. For each chain task, the corresponding subtasks can be determined based on the task attribute information of the chain task in the task configuration information. Then, task acceptance information for the chain task is generated based on the subtasks and sent to the client, enabling the client to accept the corresponding chain task. Thus, even if task requirements change, only the corresponding task configuration information needs to be modified, without adjusting the overall application code. This effectively separates the program logic development and planning configuration work of the task system, avoiding unnecessary runtime errors, reducing the workload of game development tasks, and improving overall application development efficiency and task processing efficiency.

[0154] This application involves a typical application scenario in game development. The following further explains the aforementioned beneficial effects in the context of game development. During game development, game product designers typically only define a set of related task design schemes for programmers to implement the task flow. Game product designers cannot independently modify the gameplay process, and sometimes they even have to write game scripts. The diversity and variability of tasks in game applications necessitate the abstraction of a universal mechanism. Therefore, the technical solution provided in this application provides a universal task flow framework for game loop tasks and chain tasks. Numerous tasks are flexibly managed through configuration. Only task configuration information needs to be configured to implement a series of loop tasks and chain tasks. The task flow is designed using a task flow approach. Tasks in the task pool are effectively combined using task configuration information to obtain chain tasks. Existing or newly added tasks can be combined in different ways and placed on the task flow, executed sequentially by the loop task system. All task flows are then presented to the player through the task system, tips system, and universal interaction system, making the entire task flow intuitive, controllable, and flexible. This approach expresses any cyclic task process, creating a stable driving framework that can be nested within loops. Sub-processes can be initiated within the flow, and the specific gameplay depends on the game designer's configuration. By configuring the game designer's design process, various task flows can be loaded, effectively separating the program logic development of the task system from the design configuration work. This allows program developers to focus on developing the game task logic, while game product designers can focus on configuring cyclic tasks and chained tasks suitable for different situations using configuration data, avoiding adjustments to the overall program code and reducing redundant development processes.

[0155] The following are embodiments of the apparatus of this application, which can be used to execute embodiments of the method of this application. For details not disclosed in the apparatus embodiments of this application, please refer to the embodiments of the method of this application.

[0156] Please refer to Figure 10 This diagram illustrates a block diagram of a task processing apparatus according to an embodiment of this application. The apparatus has the function of implementing the above-described task processing method; this function can be implemented in hardware or by hardware executing corresponding software. The apparatus 1000 can be a computer device or can be installed within a computer device. The apparatus 1000 may include: a configuration information acquisition module 1010, a task attribute determination module 1020, a subtask determination module 1030, a task information generation module 1040, and a task information distribution module 1050.

[0157] The configuration information acquisition module 1010 is used to acquire task configuration information.

[0158] The task attribute determination module 1020 is used to respond to the task issuance instruction for the target client and obtain the task attribute information corresponding to the target chain task from the task configuration information. The target chain task refers to any chain task in at least one chain task, and the chain task refers to a chain task composed of at least two sub-tasks.

[0159] The subtask determination module 1030 is used to determine the subtasks corresponding to the target chain task based on the task attribute information.

[0160] The task information generation module 1040 is used to generate task acceptance information corresponding to the target chain task based on the sub-task.

[0161] The task information distribution module 1050 is used to send the task acceptance information to the target client.

[0162] In an exemplary embodiment, the target chain task is a ring task, which refers to a chain task composed of at least two individual tasks. The task attribute information includes the ring task identifier corresponding to the ring task. The subtask determination module 1030 includes: a task set determination unit and a task filtering unit.

[0163] The ring task set determination unit is used to determine the task set corresponding to the ring task based on the ring task identifier when the target chain task is the ring task.

[0164] The subtask filtering unit is used to filter tasks in the task set that meet the task filtering conditions to obtain the subtasks corresponding to the ring task.

[0165] In an exemplary embodiment, the task configuration information includes task pool information, which is used to indicate task information corresponding to at least one task pool. The task set determination unit includes: a task pool identifier acquisition subunit, a task pool identifier determination subunit, and a task determination subunit.

[0166] The task pool identifier acquisition subunit is used to acquire the task pool identifier corresponding to the ring task identifier when the target chain task is the ring task.

[0167] The task pool identifier determination subunit determines the task pool corresponding to the ring task based on the task pool identifier and the task pool information.

[0168] The task determination subunit determines the tasks corresponding to the task pool as tasks in the task set.

[0169] In an exemplary embodiment, the target chain task is a ring chain task, which refers to a chain task including at least one of the ring tasks. The task attribute information includes the ring chain task identifier corresponding to the ring chain task. The subtask determination module 1030 further includes: a ring chain task set determination unit, a ring chain task filtering unit, a subtask determination unit, and a ring chain task determination unit.

[0170] The chain task set determination unit is used to determine the task set corresponding to the chain task based on the chain task identifier when the target chain task is the chain task.

[0171] The ring task filtering unit is used to filter the ring tasks in the task set that meet the task filtering conditions, and obtain the ring tasks corresponding to the ring tasks.

[0172] The subtask determination unit is used to determine the subtask corresponding to each ring task in the ring chain task, starting from the step of determining the task set corresponding to the ring task based on the ring task identifier, for any ring task in the ring chain task.

[0173] The ring task determination unit is used to determine the subtask corresponding to each ring task in the ring task as the subtask corresponding to the ring task.

[0174] In an exemplary embodiment, the ring chain task filtering unit is further configured to filter individual tasks in the task set that meet the task filtering conditions, thereby obtaining the individual tasks corresponding to the ring chain tasks.

[0175] The ring chain task determination unit is further configured to treat the individual task corresponding to the ring chain task as the sub-task corresponding to the ring chain task.

[0176] In an exemplary embodiment, the task configuration information includes at least one task level, task group, and task chain position corresponding to a task, and the task filtering conditions include at least one of task level conditions, task group conditions, and task chain position conditions.

[0177] The task level condition is that the task level belongs to the target level, the task grouping condition is that the task group belongs to the target group, and the task location condition is that the task chain location is at the target location.

[0178] In an exemplary embodiment, the task configuration information includes resource information corresponding to the target chain task, and the device 1000 further includes: a resource determination module and a resource sending module.

[0179] The resource determination module is used to determine the resource information corresponding to the target sub-task from the resource information in response to the task completion instruction of the target sub-task in the target chain task.

[0180] The resource sending module is used to send the resource information corresponding to the target subtask to the target client.

[0181] In summary, the technical solution provided in this application, through an abstracted and general chain task processing mechanism, flexibly manages tasks through configuration. For each chain task, the corresponding subtasks can be determined based on the task attribute information of the chain task in the task configuration information. Then, task acceptance information for the chain task is generated based on the subtasks and sent to the client, enabling the client to accept the corresponding chain task. Thus, even if task requirements change, only the corresponding task configuration information needs to be modified, without adjusting the overall application code. This effectively separates the program logic development and planning configuration work of the task system, avoiding unnecessary runtime errors, reducing the workload of game development tasks, and improving overall application development efficiency and task processing efficiency.

[0182] It should be noted that the apparatus provided in the above embodiments is only illustrated by the division of the above functional modules when implementing its functions. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above. In addition, the apparatus and method embodiments provided in the above embodiments belong to the same concept, and the specific implementation process can be found in the method embodiments, which will not be repeated here.

[0183] Please refer to Figure 11 This diagram illustrates a structural block diagram of a computer device according to an embodiment of this application. The computer device can be either a terminal or a server, used to execute the aforementioned task processing method. Specifically:

[0184] Computer device 1100 includes a central processing unit (CPU) 1101, a system memory 1104 including random access memory (RAM) 1102 and read-only memory (ROM) 1103, and a system bus 1105 connecting the system memory 1104 and the CPU 1101. Computer device 1100 also includes a basic input / output system (I / O system) 1106 that facilitates information transfer between various devices within the computer, and a mass storage device 1107 for storing the operating system 1113, application programs 1114, and other program modules 1115.

[0185] The basic input / output system 1106 includes a display 1108 for displaying information and an input device 1109 for user input, such as a mouse or keyboard. Both the display 1108 and the input device 1109 are connected to the central processing unit 1101 via an input / output controller 1110 connected to the system bus 1105. The basic input / output system 1106 may also include the input / output controller 1110 for receiving and processing input from multiple other devices such as a keyboard, mouse, or electronic stylus. Similarly, the input / output controller 1110 also provides output to a display screen, printer, or other types of output devices.

[0186] Mass storage device 1107 is connected to central processing unit 1101 via a mass storage controller (not shown) connected to system bus 1105. Mass storage device 1107 and its associated computer-readable media provide non-volatile storage for computer device 1100. That is, mass storage device 1107 may include computer-readable media (not shown) such as hard disk or CD-ROM (Compact Disc Read-Only Memory) drive.

[0187] Without loss of generality, computer-readable media can include computer storage media and communication media. Computer storage media includes volatile and non-volatile, removable and non-removable media implemented using any method or technology for storing information such as computer-readable instructions, data structures, program modules, or other data. Computer storage media includes RAM, ROM, EPROM (Erasable Programmable Read Only Memory), EEPROM (Electrically Erasable Programmable Read Only Memory), flash memory or other solid-state storage technologies, CD-ROM, DVD (Digital Video Disc) or other optical storage, magnetic tape cassettes, magnetic tape, disk storage, or other magnetic storage devices. Of course, those skilled in the art will recognize that computer storage media are not limited to the above-mentioned types. The system memory 1104 and mass storage device 1107 described above can be collectively referred to as memory.

[0188] According to various embodiments of this application, the computer device 1100 can also be connected to a remote computer on a network, such as the Internet. That is, the computer device 1100 can be connected to the network 1112 via the network interface unit 1111 connected to the system bus 1105, or the network interface unit 1111 can be used to connect to other types of networks or remote computer systems (not shown).

[0189] The memory also includes a computer program stored in the memory and configured to be executed by one or more processors to implement the above-described task processing method.

[0190] In an exemplary embodiment, a computer-readable storage medium is also provided, the storage medium storing at least one instruction, at least one program, code set, or instruction set, wherein the at least one instruction, the at least one program, the code set, or the instruction set, when executed by a processor, implements the above-described task processing method.

[0191] Optionally, the computer-readable storage medium may include: ROM (Read Only Memory), RAM (Random Access Memory), SSD (Solid State Drives), or optical disc, etc. The random access memory may include ReRAM (Resistance Random Access Memory) and DRAM (Dynamic Random Access Memory).

[0192] In an exemplary embodiment, a computer program product or computer program is also provided, which includes computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the task processing method described above.

[0193] It should be understood that "multiple" as used herein refers to two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship. Furthermore, the step numbers described herein are merely illustrative of one possible execution order. In some other embodiments, the steps may not be executed in numerical order, such as two steps with different numbers being executed simultaneously, or two steps with different numbers being executed in the reverse order of the illustration. This application does not limit this.

[0194] The above description is merely an exemplary embodiment of this application and is not intended to limit this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the protection scope of this application.

Claims

1. A task processing method, characterized in that, The method includes: Get task configuration information; In response to a task command issued to a target client, the task attribute information corresponding to the target chain task is obtained from the task configuration information. The target chain task refers to any chain task in at least one chain task, and the chain task refers to a chain task composed of at least two sub-tasks. The task attribute information includes task pool identifier, task level, task group, and task chain position. Based on the task attribute information, the sub-tasks corresponding to the target chain task are determined, including: Determine whether a task pool corresponding to the task pool identifier exists. If a task pool corresponding to the task pool identifier exists, then determine whether there is a task in the task pool that corresponds to the current account level. If there are tasks in the task pool that correspond to the current account level, then determine whether there are tasks that correspond to the current task group; If there is a task corresponding to the current task group, then determine if there is a task corresponding to the current task chain ring number; if there is a task corresponding to the current task chain ring number, then among the multiple tasks that meet the current task filtering conditions, the target sub-task in the ring task is randomly determined according to the configuration probability corresponding to each task. If there is no task corresponding to the current task group, then randomly select a group of tasks with the same task group from the multiple tasks that have been found so far, and determine whether there is a task corresponding to the current task chain ring number; if there is a task corresponding to the current task chain ring number, then randomly determine the target subtask in the ring task from the multiple tasks that meet the task filtering conditions, according to the configuration probability corresponding to each task. Based on the sub-tasks, generate task acceptance information corresponding to the target chain task; Send the task acceptance information to the target client.

2. The method according to claim 1, characterized in that, The target chain task is a ring task, which refers to a chain task consisting of at least two individual tasks. The task attribute information includes the ring task identifier corresponding to the ring task. Determining the sub-tasks corresponding to the target chain task based on the task attribute information includes: If the target chain task is the chain task, determine the task set corresponding to the chain task based on the chain task identifier; By filtering the tasks in the task set that meet the task filtering criteria, the subtasks corresponding to the ring task are obtained.

3. The method according to claim 2, characterized in that, When the target chain of tasks is the chain task, determining the task set corresponding to the chain task based on the chain task identifier includes: If the target chain task is the chain task, obtain the task pool identifier corresponding to the chain task identifier; Based on the task pool identifier and task pool information, the task pool corresponding to the ring task is determined; The tasks corresponding to the task pool are identified as tasks in the task set.

4. The method according to claim 2 or 3, characterized in that, The target chain task is a ring-chain task, which refers to a chain of tasks including at least one of the ring tasks. The task attribute information includes the ring-chain task identifier corresponding to the ring task. Determining the sub-tasks corresponding to the target chain task based on the task attribute information further includes: If the target chain task is the chain task, the task set corresponding to the chain task is determined according to the chain task identifier; Filter the ring tasks in the task set that meet the task filtering conditions to obtain the ring tasks corresponding to the ring chain tasks; For any ring task in the ring task corresponding to the ring chain task, execution starts from the step of determining the task set corresponding to the ring task based on the ring task identifier, and determines the sub-task corresponding to each ring task in the ring chain task; Each subtask corresponding to a ring task in the ring chain task is taken as the subtask corresponding to the ring chain task.

5. The method according to claim 4, characterized in that, When the target chain task is the chain task, after determining the task set corresponding to the chain task based on the chain task identifier, the method further includes: Filter individual tasks in the task set that meet the task filtering conditions to obtain the individual tasks corresponding to the chain task; The individual tasks corresponding to the ring chain tasks are treated as subtasks corresponding to the ring chain tasks.

6. The method according to claim 1, characterized in that, The task configuration information includes resource information corresponding to the target chain of tasks, and the method further includes: In response to the task completion instruction of the target subtask in the target chain task, the resource information corresponding to the target subtask is determined from the resource information; Send the resource information corresponding to the target subtask to the target client.

7. A task processing device, characterized in that, The device includes: The configuration information acquisition module is used to acquire task configuration information; The task attribute determination module is used to respond to a task issuance command for a target client and obtain the task attribute information corresponding to the target chain task from the task configuration information. The target chain task refers to any chain task in at least one chain task, and the chain task refers to a chain task composed of at least two sub-tasks. The task attribute information includes task pool identifier, task level, task group, and task chain position. The subtask determination module is used to determine the subtasks corresponding to the target chain task based on the task attribute information, including: determining whether a task pool corresponding to the task pool identifier exists; if a task pool corresponding to the task pool identifier exists, determining whether a task corresponding to the current account level exists in the task pool; if a task corresponding to the current account level exists in the task pool, determining whether a task corresponding to the current task group exists; if a task corresponding to the current task group exists, determining whether a task corresponding to the current task chain number exists; if a task corresponding to the current task chain number exists, randomly determining the target subtask in the chain task from among the multiple tasks that currently meet the task filtering conditions, based on the configuration probability corresponding to each task; if no task corresponding to the current task group exists, randomly selecting a group of tasks with the same task group from among the multiple tasks that have been found, and determining whether a task corresponding to the current task chain number exists; if a task corresponding to the current task chain number exists, randomly determining the target subtask in the chain task from among the multiple tasks that currently meet the task filtering conditions, based on the configuration probability corresponding to each task. The task information generation module is used to generate task acceptance information corresponding to the target chain task based on the sub-task; The task information delivery module is used to send the task acceptance information to the target client.

8. The task processing apparatus according to claim 7, characterized in that, The target chain task is a ring task, which refers to a chain task composed of at least two individual tasks. The task attribute information includes the ring task identifier corresponding to the ring task. The subtask determination module includes: a task set determination unit and a task filtering unit. The task set determination unit is used to determine the task set corresponding to the ring task based on the ring task identifier when the target chain task is the ring task. The task filtering unit is used to filter tasks in the task set that meet the task filtering conditions to obtain the sub-tasks corresponding to the ring task.

9. The apparatus according to claim 8, characterized in that, The task set determination unit includes: The task pool identifier acquisition subunit is used to acquire the task pool identifier corresponding to the ring task identifier when the target chain task is the ring task. The task pool identifier determination subunit is used to determine the task pool corresponding to the ring task based on the task pool identifier and task pool information. The task determination subunit is used to determine the tasks corresponding to the task pool as tasks in the task set.

10. The apparatus according to claim 8 or 9, characterized in that, The target chain task is a ring-chain task, which refers to a chain of tasks including at least one of the ring tasks. The task attribute information includes the ring-chain task identifier corresponding to the ring task. The subtask determination module further includes: A chain task set determination unit is used to determine the task set corresponding to the chain task based on the chain task identifier when the target chain task is the chain task. A ring task filtering unit is used to filter ring tasks in the task set that meet the task filtering conditions, and obtain the ring tasks corresponding to the ring tasks. The subtask determination unit is used to determine the subtask corresponding to each ring task in the ring chain task for any ring task in the ring chain task, starting from the step of determining the task set corresponding to the ring task based on the ring task identifier. The ring task determination unit is used to determine the subtask corresponding to each ring task in the ring task as the subtask corresponding to the ring task.

11. The apparatus according to claim 10, characterized in that, The ring chain task filtering unit is also used for: Filter individual tasks in the task set that meet the task filtering conditions to obtain the individual tasks corresponding to the chain task; The individual tasks corresponding to the ring chain tasks are treated as subtasks corresponding to the ring chain tasks.

12. The apparatus according to claim 7, characterized in that, The task configuration information includes resource information corresponding to the target chain task, and the device further includes: The resource determination module is used to determine the resource information corresponding to the target sub-task from the resource information in response to the task completion instruction of the target sub-task in the target chain task; The resource sending module is used to send the resource information corresponding to the target subtask to the target client.

13. A computer device, characterized in that, The computer device includes a processor and a memory, the memory storing at least one instruction, at least one program, a code set, or an instruction set, the at least one instruction, the at least one program, the code set, or the instruction set being loaded and executed by the processor to implement the task processing method as described in any one of claims 1 to 6.

14. A computer-readable storage medium, characterized in that, The storage medium stores at least one instruction, at least one program, code set, or instruction set, wherein the at least one instruction, the at least one program, the code set, or the instruction set is loaded and executed by a processor to implement the task processing method as described in any one of claims 1 to 6.

15. A computer program product, characterized in that, The computer program product includes computer instructions stored in a computer-readable storage medium, wherein a processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions to cause the computer device to perform the task processing method as described in any one of claims 1 to 6.

Images