Task Control Method, Device and Storage Medium

Abstract

This application relates to a task control method, device, and storage medium. In the embodiments of this application, a second type of team is generated as an opponent for a partial team composed of users, and second type user information in the second type of team and multiple task data that the second type user information needs to complete are created. The multiple task data that the second type user information needs to complete are allocated to multiple task periods. For each task period, a random task execution time is set for the task data allocated to that task period, so that the time for the second type user information to execute the task data is no longer fixed. The second type user information can execute the task data at random time points, improving the user experience and the interest of the task, and increasing the user activity and platform stickiness.

Description

Technical Field

[0001] This application relates to the technical field of data processing, and in particular, to a task control method, device, and storage medium. Background Art

[0002] On some social platforms, in order to increase user activity and platform stickiness, competitive online game activities are provided. Users need to form teams with friends and compete with other teams through the teams. Members in each team accumulate points for their own teams by completing tasks in the activities. When the competition ends, the team with the higher score wins and obtains reward resources.

[0003] To ensure a good experience for users, when matching opponents for users, matching teams with comparable strength can give users a better gaming experience. For some novice players or players who cannot match a suitable team, a team can be created as an opponent for the team formed by the user. The user accounts in the team as an opponent adopt a global and static behavior strategy and compete with the team formed by the user. However, the user accounts created by the system cannot meet the competition interests of users, affecting user activity and platform stickiness. Summary of the Invention

[0004] This application provides a task control method, device, and storage medium to at least solve the problem that the user accounts created by the system cannot meet the competition interests of users, affecting user activity and platform stickiness.

[0005] The technical solution of this application is as follows:

[0006] According to the first aspect of the embodiments of this application, a task control method is provided, including: in response to a trigger operation for a first type of object group to participate in a task, generating a second type of object group and N sub-tasks that the second type of object group needs to complete, where the second type of object group has a competitive relationship with the first type of object group and includes at least one second type of resource account, N is a positive integer and N≥2; determining multiple task periods during the task execution according to the duration of the task, and establishing a corresponding relationship among at least one second type of resource account, N sub-tasks, and multiple task periods; for any second type of resource account, determining the target task period and target sub-task corresponding to any second type of resource account according to the corresponding relationship, randomly determining the target time point in the target task period, executing the target sub-task when the target time point arrives, and updating the resource data in any second type of resource account according to the execution result of the target sub-task.

[0007] According to a second aspect of the embodiments of the present application, a task control device is provided, including: a memory and a processor; the memory is used to store a computer program; the processor is coupled with the memory and is used to execute the computer program to: in response to a trigger operation of a first type of object group participating in a task, generate a second type of object group and N subtasks that the second type of object group needs to complete, where the second type of object group has a competitive relationship with the first type of object group and includes at least one second type of resource account, N is a positive integer and N≥2; determine multiple task periods during the execution of the task according to the duration of the task, and establish a corresponding relationship among at least one second type of resource account, N subtasks, and multiple task periods; for any second type of resource account, determine the target task period and target subtask corresponding to any second type of resource account according to the corresponding relationship, randomly determine the target time point in the target task period, execute the target subtask when the target time point arrives, and update the resource data in any second type of resource account according to the execution result of the target subtask.

[0008] According to a third aspect of the embodiments of the present application, a computer-readable storage medium is provided, which, when the computer program is executed by a processor, causes the processor to implement the steps in the task control method provided by the embodiments of the present application.

[0009] According to a fourth aspect of the embodiments of the present application, a computer program product is provided, including computer program / instructions, which, when the computer program / instructions are executed by a processor, cause the processor to implement the steps in the task control method provided by the embodiments of the present application.

[0010] The technical solutions provided by the embodiments of the present application at least bring the following beneficial effects:

[0011] In the embodiments of the present application, a second type of object group with a competitive relationship is generated for the first type of object group composed of users, and a second type of resource account in the second type of object group and N subtasks that the second type of resource account needs to complete are created. The N subtasks that the second type of resource account needs to complete are assigned to multiple task periods. For each task period, a random task execution time is set for the subtasks assigned to that task period, so that the time for the second type of resource account to execute the subtasks is no longer fixed. The second type of resource account can execute task data at random time points, improving the user experience and the interest of the task, and increasing the user activity and platform stickiness.

[0012] It should be understood that the above general description and the following detailed description are only exemplary and explanatory, and cannot limit the present application. Description of the Drawings

[0013] The accompanying drawings here are incorporated into and form a part of this specification, showing embodiments consistent with this application, and are used together with the specification to explain the principles of this application, and do not constitute an undue limitation on this application.

[0014] Figure 1 is a schematic flowchart of a task control method shown according to an exemplary embodiment;

[0015] Figure 2 is a flowchart of allocating task data and task time periods for a second type of user information shown according to an exemplary embodiment;

[0016] Figure 3 is a flowchart of increasing second type of task data shown according to an exemplary embodiment;

[0017] Figure 4 is a structural diagram of a task control device shown according to an exemplary embodiment. Detailed implementation manners

[0018] To enable those of ordinary skill in the art to better understand the technical solutions of this application, the technical solutions in the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings.

[0019] It should be noted that the terms "first", "second", etc. in the specification and claims of this application and the above accompanying drawings are used to distinguish similar objects, and do not necessarily have to be used to describe a specific order or sequence. It should be understood that such used data may be interchanged under appropriate circumstances so that the embodiments of this application described here can be implemented in an order different from those illustrated or described here. The implementation manners described in the following exemplary embodiments do not represent all implementation manners consistent with this application. On the contrary, they are merely examples of devices and methods consistent with some aspects of this application as detailed in the appended claims.

[0020] In the prior art, the behavior strategies of the second - type resource accounts are global and static. The behavior time of the second - type resource accounts is completely fixed, and the behaviors of the second - type resource accounts are the same. This greatly dampens the users' interest in competitions, affecting the users' activity and platform stickiness. In the embodiments of the present application, a second - type object group with a competitive relationship is generated for a first - type object group composed of users, and second - type resource accounts in the second - type object group and N sub - tasks that the second - type resource accounts need to complete are created. The N sub - tasks that the second - type resource accounts need to complete are allocated to multiple task periods. For each task period, a random task execution time is set for the sub - tasks allocated to that task period, so that the time for the second - type resource accounts to execute sub - tasks is no longer fixed. The second - type resource accounts can execute task data at random time points, improving the user experience and the fun of the tasks, and increasing the users' activity and platform stickiness.

[0021] The following will, with reference to the accompanying drawings, elaborate on the technical solutions provided by the embodiments of the present application.

[0022] Figure 1 It is a schematic flowchart of a task control method provided by an exemplary embodiment of the present application; as Figure 1 shown, the method includes:

[0023] 101. In response to a trigger operation for a first - type object group to participate in a task, generate a second - type object group and N sub - tasks that the second - type object group needs to complete. The second - type object group has a competitive relationship with the first - type object group and includes at least one second - type resource account. N is a positive integer and N≥2;

[0024] 102. According to the duration of the task, determine multiple task periods during the task execution process, and establish a corresponding relationship among at least one second - type resource account, N sub - tasks, and multiple task periods;

[0025] 103. For any second - type resource account, determine the target task period and target sub - task corresponding to the second - type resource account according to the corresponding relationship, randomly determine the target time point in the target task period, execute the target sub - task when the target time point arrives, and update the resource data in any second - type resource account according to the execution result of the target sub - task.

[0026] In this embodiment, in order to increase the activity of users on the social platform and the platform stickiness, some tasks can be provided on the social platform, such as competitive tasks. Competitive tasks require at least two teams to be opponents of each other. During the execution of the competitive tasks, players in the teams need to complete some tasks. For each task completed, corresponding scores and reward resources can be obtained. The scores obtained by players in the same team are accumulated to get the score of the team. Finally, the team or teams with the highest score win.

[0027] In this embodiment, an interactive interface for users to participate in tasks can be provided through a social APP on a terminal device or a web page on a browser. Users can invite friends and form an object group with their friends to participate in the task. For the convenience of description and distinction, the team composed of users is called the first type of object group, and the users in the first type of object group are called the first type of resource accounts. Among them, a trigger operation for the first type of object group to participate in the task can be initiated. For this trigger operation, another first type of object group composed of the first type of resource accounts can be matched for the first type of object group, and there is a competitive relationship between the other first type of object group and the first type of object group composed of users; alternatively, a second type of object group can also be matched for the first type of object group. The second type of object group includes at least one second type of resource account. The second type of resource account can be created by the social platform, and the second type of resource account is different from the first type of resource account created by users. The team composed of the second type of resource accounts is called the second type of object group. After the second type of object group is created, at least one second type of resource account in the second type of object group executes subtasks, thereby establishing a competitive relationship between the second type of object group and the first type of object group.

[0028] Specifically, in the case of matching a second type of object group with a competitive relationship for the first type of object group, a trigger operation for the first type of object group to participate in the task can be responded to, and a second type of object group and N subtasks that the second type of object group needs to complete can be generated. Among them, the second type of object group includes at least one second type of resource account, and the second type of resource account needs to complete N subtasks. A subtask is an operation that a second type of resource account or a first type of resource account needs to execute. The resource data corresponding to the corresponding resource account can be updated according to the execution result of the subtask executed by the second type of resource account or the first type of resource account. The resource data can be scores or rewards that can be obtained by executing the subtask. Among them, in the case where the task is implemented as a competitive game on a social platform, the subtask can be operations such as signing in, providing assistance, watching short videos, following new users, or posting videos.

[0029] In this embodiment, multiple task time periods during the task execution process can be determined according to the duration of the task. The duration of the task can be 13 hours, one day, one week, etc., and there is no limitation in this regard. For example, if the duration of the task is 13 hours, the start time of the task can be 9:00 am, and the end time of the task can be 10:00 pm. The lengths of the multiple task time periods are not limited either. For example, the duration of the task can be evenly divided into multiple task time periods, and the multiple task time periods have the same duration. Another example is that the duration of the task is 12 hours, and the start time and end time of the task are 9:00 and 21:00 in a day respectively. Then the duration of the task is divided into three task time periods. For example, the period from 9:00 to 12:00 is used as the first task time period, the period from 12:00 to 18:00 is used as the second task time period, and the period from 18:00 to 21:00 is used as the third task time period. The durations of different task time periods can be the same or different. After determining the multiple task time periods, a corresponding relationship can be established among at least one second-type resource account in the second-type object group, the N sub-tasks that the second-type object group needs to complete, and the multiple task time periods. Among them, the sub-tasks that the second-type resource account in each second-type object group needs to complete can correspond to all of the multiple task time periods or only to some of the multiple task time periods. For example, if there are 3 multiple task time periods, the sub-tasks that the second-type resource account needs to complete can be assigned to 3 task time periods, or to one or two task time periods.

[0030] In this embodiment, for any second-type resource account, the target task time period and the target sub-task corresponding to the second-type resource account can be determined according to the above corresponding relationship. The target task time period is any one of the task time periods corresponding to the second-type resource account, and the target sub-task is any one of the sub-tasks that the second-type resource account needs to complete. In addition, the target time point in the target task time period can be randomly determined. When the target time point arrives, control the second-type resource account to execute the target sub-task, and update the resource data in the second-type resource account according to the execution result of the target sub-task.

[0031] In the embodiment of the present application, a second-type object group with a competitive relationship is generated for the first-type object group composed of users, and second-type resource accounts in the second-type object group and the N sub-tasks that the second-type resource accounts need to complete are created. The N sub-tasks that the second-type resource accounts need to complete are assigned to multiple task time periods. For each task time period, a random task execution time is set for the sub-tasks assigned to this task time period, so that the time for the second-type resource account to execute the sub-tasks is no longer fixed. The second-type resource account can execute task data at random time points, improving the user experience and the interest of the task, and increasing the user activity and platform stickiness.

[0032] In an alternative embodiment, there is no limitation on the implementation manner of generating the second type of object group and the N subtasks that the second type of object group needs to complete in response to the trigger operation of the first type of object group participating in the task. The following provides an implementation manner of generating the second type of object group and the N subtasks that the second type of object group needs to complete in response to the trigger operation of the first type of object group participating in the task, including: For the first type of object group that participates in the task not for the first time, the second type of object group and the N subtasks that the second type of object group needs to complete can be generated according to the information of the historical subtasks of the first type of object group. Specifically, in response to the trigger operation of the first type of object group participating in the task, the information of the historical subtasks completed by the first type of object group and the number of the first type of resource accounts included in the first type of object group can be obtained. Among them, the information of the historical subtasks includes but is not limited to: the historical activity level, activity degree or the information of the historical completed subtasks of the first type of object group, etc.; According to the number of the first type of resource accounts in the first type of object group, the number of resource accounts required for the second type of object group is determined, and at least one second type of resource account is generated for the second type of object group according to the number of resource accounts required for the second type of object group; According to the information of the historical subtasks completed by the first type of object group, the N subtasks that the second type of object group needs to complete are determined. For the first type of object group that participates in the task for the first time, other first type of object groups with a lower activity level can be matched for this first type of object group, or the second type of object group can be generated for this first type of object group according to the user level or activity degree of the first type of resource accounts in the first type of object group.

[0033] In an alternative embodiment, there is also a subtask set corresponding to the task maintained. The subtask set includes K subtasks, where K≥2 and K is an integer. Each subtask corresponds to a fixed amount of resources. The N subtasks that the second type of object group needs to complete can be selected from this subtask set according to the information of the historical subtasks completed by the first type of object group. Specifically, according to the amount of resources corresponding to the historical subtasks completed by the first type of object group, the range of the total amount of resources that can be allocated to the second type of object group is determined. For example, the range of the total amount of resources that can be allocated to the second type of object group includes an upper limit value and a lower limit value. The upper limit value can be the amount of resources corresponding to the historical subtasks completed by the first type of object group plus a set first amount of resources, and the lower limit value can be the amount of resources corresponding to the historical subtasks completed by the first type of object group plus or minus a set second amount of resources. The first amount of resources and the second amount of resources can be the same or different, and the first amount of resources and the second amount of resources are less than the amount of resources corresponding to the historical subtasks completed by the first type of object group. After determining the range of the total amount of resources that can be allocated to the second type of object group, at least one subtask in the K subtasks is combined according to the amount of resources corresponding to each subtask in the K subtasks and this range of the total amount of resources to form the N subtasks that the second type of object group needs to complete, and the sum of the amounts of resources corresponding to the N subtasks is within the range of the total amount of resources.

[0034] In an optional embodiment, the K seed tasks include a first type of subtasks with a limited number of executions and a second type of subtasks without a limited number of executions. For the first type of subtasks, limiting the number of executions means limiting the number of times the second type of subtasks are executed for each second type of resource account. For example, for the subtask of "signing in", the number of sign-in times for each second type of resource account is limited to 1; for the subtask of "sharing a video", the number of executions for each second type of resource account is limited to 5. When the number of executions of the first type of subtasks does not exceed the set number of executions, each execution of the first type of subtasks can update the resource data corresponding to the resource account. If the number of executions of the first type of subtasks exceeds the set number of executions, subsequent executions of the first type of subtasks will no longer update the resource data, such as no longer accumulating scores or rewards. For the second type of subtasks, not limiting the number of times means not limiting the number of executions of the second type of subtasks by the second type of resource account. For example, there is no limit on the number of executions for "watching a video", "opening the APP", "inviting friends", "inviting new users", or "forwarding a video", etc. Each execution of the second type of subtasks can update the resource data, such as accumulating scores or rewards.

[0035] Based on the above, according to the resource amount corresponding to each seed task in the K seed tasks and the range of the total resource amount, at least one type of subtask in the K seed tasks is combined to form N subtasks that the second type of object group needs to complete, including: combining at least one type of subtask in the first type of subtasks to form N1 subtasks according to the resource amount and the number of executions corresponding to each subtask in the first type of subtasks and in combination with the range of the total resource amount, such as Figure 2As shown. Among them, the number of occurrences of the same subtask in N1 subtasks is less than the execution times corresponding to this subtask. For example, if the execution times of the first type of subtask X1 is 2 and the number of the second type of resource accounts is 3, then the number of times each second type of resource account can execute the first type of subtask is 2, and the execution times of the first type of subtask can be less than or equal to 2×3 = 6 times. That is to say, the number of times the first type of subtask X1 appears in N1 subtasks is less than or equal to 6. If the sum of the resource amounts corresponding to N1 subtasks is less than the lower limit value of the resource total amount range, then calculate the difference between the upper limit value of the resource total amount range and the sum of the resource amounts corresponding to N1 subtasks. The calculation method of the resource amounts corresponding to N1 subtasks can be to calculate the product of the execution times corresponding to each subtask in N1 subtasks and the resource amount corresponding to this subtask, obtain the resource amount of each subtask, and sum the resource amounts corresponding to each subtask to obtain the resource amounts corresponding to N1 subtasks. According to the difference between the upper limit value of the resource total amount range and the sum of the resource amounts corresponding to N1 subtasks and the resource amount corresponding to each subtask in the second type of subtasks, perform task combination on at least one type of subtask in the second type of subtasks to form N2 subtasks. N1 and N2 are positive integers, and N1 + N2 = N. The second type of subtasks included in N2 subtasks can belong to different types or the same type. For example, the type of the second type of subtasks is 5 and N2 is 3, then N2 subtasks can include 3 different second type of subtasks, or N2 subtasks can include 3 identical second type of subtasks, or two identical second type of subtasks and another second type of subtask of a different type. Among them, the sum of the resource amounts corresponding to N2 subtasks is less than or equal to this difference. That is to say, the sum of the resource amounts corresponding to N1 subtasks and the resource amounts corresponding to N2 subtasks is within the resource total amount range that can be allocated by the second type of object group, so that the strength of the second type of object group matches that of the first type of object group to enhance the user's task experience.

[0036] In an optional embodiment, an implementation method for establishing a correspondence relationship among at least one second-type resource account, N sub-tasks, and multiple task periods includes: aiming at each second-type resource account corresponding to a first-type sub-task, establishing a correspondence relationship between N1 sub-tasks and at least one second-type resource account. For example, if there are 3 second-type resource accounts in the second object group, the number of first-type sub-tasks is 5 and the type of first-type sub-tasks is 1, then one first-type sub-task can be assigned to one of the second-type resource accounts, and two first-type sub-tasks can be assigned to the remaining two second-type resource accounts. In addition, a correspondence relationship between N2 sub-tasks and at least one second-type resource account can be randomly established. After assigning the first-type sub-tasks and second-type sub-tasks to the second-type resource accounts, the sub-tasks corresponding to at least one second-type resource account can be sorted according to the type of sub-tasks, and the sorted sub-tasks of at least one second-type resource account are cross-sorted to obtain a sub-task queue, as Figure 2 shown; for example, the second object group includes: second-type resource account Y1 and second-type resource account Y2. The second-type resource account Y1 and the second-type resource account Y2 each have 3 sub-tasks. After sorting each second-type resource account, the sub-task order of the second-type resource account Y1 is: sub-task 1, sub-task 3, and sub-task 4. The sub-task order of the second-type resource account Y2 is: sub-task 2, sub-task 5, and sub-task 6. The sorted sub-tasks of the second-type resource account Y1 and the second-type resource account Y2 are cross-sorted to obtain a sub-task queue, and the sub-task queue is: sub-task 1, sub-task 2, sub-task 3, sub-task 4, sub-task 5, and sub-task 6. After determining the sub-task queue, the task volume corresponding to each task period can be set. According to the task volume corresponding to each task period, the sub-tasks in the sub-task queue are sequentially assigned to each task period, and a correspondence relationship among at least one second-type resource account, N sub-tasks, and multiple task periods is established according to the sub-tasks assigned to each task period and the sub-tasks corresponding to at least one second-type resource account, as Figure 2 shown.

[0037] Optionally, before distributing the subtasks in the subtask queue to each task period according to the task volume corresponding to each task period, it is also possible to determine the task volume ratio corresponding to multiple task periods according to the number of historical subtasks corresponding to multiple task periods; and obtain the task volume corresponding to each task period according to the task volume ratio corresponding to multiple task periods and the number of N subtasks. For example, according to the number of historical subtasks corresponding to multiple task periods, it is obtained that the active time period of the first type of resource account is from 18:00 to 21:00 and from 9:00 to 12:00. Then, the quantity ratio of the task period corresponding to 18:00 to 21:00 can be set to 50%, the quantity ratio of the task period corresponding to 9:00 to 12:00 can be set to 30%, and the quantity ratio of the task period corresponding to 12:00 to 18:00 can be set to 20%. For example, for the 10 subtasks that the second type of object group needs to complete, 5 subtasks can be allocated to the task period corresponding to 18:00 to 21:00, 2 subtasks can be allocated to the task period corresponding to 12:00 to 18:00, and 3 subtasks can be allocated to the task period corresponding to 18:00 to 21:00.

[0038] In an alternative embodiment, an implementation method of manually intervening in the execution of subtasks by the second type of resource account is also added, adding or deleting tasks for some second type of object groups participating in tasks on the social platform, so that the strengths of the first type of object group and the second type of object group in a competing relationship are matched, enhancing the user experience and improving user activity. Based on this, in the case where there are multiple first type of object groups, according to the resource data of each first type of resource account in each first type of object group, calculate the total resource volume of each first type of object group respectively, and obtain the first type of object group with the total resource volume greater than the set resource threshold as the first target object group. The number of first target object groups can be one, or multiple, such as 2, 3, or 5, etc., and no limitation is made in this regard; the second type of object group in a competing relationship with the first target object group is used as the second target object group. The number of second target object groups can be one, or multiple, and no limitation is made in this regard. The number of first target object groups and the number of second target object groups can be the same or different. Calculate the total resource volume of the second target object group according to the resource data of each second type of resource account in the second target object group; adjust the number of second type of subtasks in the second target object group according to the ratio of the total resource volume of the first target object group to the total resource volume of the second target object group.

[0039] In an alternative embodiment, the number of second - type subtasks in the second target object group can be increased or deleted according to the ratio of the total resources of the first target object group to the total resources of the second target object group. Specifically, when the ratio of the total resources of the first target object group to the total resources of the second target object group exceeds a set first threshold, the second - type subtasks in the second target object group are increased; or when the ratio of the total resources of the first target object group to the total resources of the second target object group is lower than a set second threshold, the second - type subtasks in the second target object group are deleted.

[0040] Among them, the implementation manner of increasing the number of second - type subtasks in the second target object group according to the ratio of the total resources of the first target object group to the total resources of the second target object group is not limited. The following is an example for introduction. In an alternative embodiment, as Figure 3 shown, when the ratio of the total resources of the first target object group to the total resources of the second target object group exceeds the set first threshold, for the convenience of distinction and description, the ratio of the total resources of the first target object group to the total resources of the second target object group is denoted as the first ratio; when the total resources of the first target object group are determined, based on the first ratio and the first threshold, the expected total resources of the second - type object group can be calculated, denoted as the first expected total resources and the second expected total resources respectively. The first expected resource sum is denoted as the current total resources of the second target object group, and the second expected total resources represents the total resources of the second target object group when the ratio of the total resources of the first target object group to the total resources of the second target object group is the first threshold. According to the difference between the first expected total resources and the second expected total resources, the resource amount of the second - type subtasks to be increased is determined, and according to this resource amount, the second - type subtasks in the second target object group are increased.

[0041] In another alternative embodiment, as Figure 3As shown, when the ratio of the total resource amount of the first target object group to the total resource amount of the second target object group exceeds the set first threshold, according to the level of the first target object group, the second type of subtasks in the second target object group is increased. Specifically, the corresponding relationship between the level of the first target object group and the percentage is preset, where the percentage is used to reflect the fluctuation range of the task amount of the subtasks executed by the second target object group corresponding to the first target object group, and this percentage can be configured according to the actual situation. For example, the higher the level of the first target object group, the higher the percentage corresponding to this level, and the larger the fluctuation range of the resource amount of the subtasks that the second target object group corresponding to the first target object group needs to execute. According to the level of the first target object group, determine the percentage corresponding to the second target object group from the preset corresponding relationship between the level and the percentage; according to the percentage and the expected total resources of the second target object group at this level, determine the resource amount of the second type of subtasks that need to be increased, and according to the resource amount of the second type of subtasks that need to be increased, increase the second type of subtasks in the second target object group. For example, the following formula can be used to determine the resource amount of the second type of subtasks that need to be increased: threshold*(1+floatFactor)*addRatio. Where threshold represents the expected total resource amount of the second target object group, floatFactor represents the activity factor, and addRatio represents the percentage. For example, (1+floatFactor)*addRatio can fluctuate between 0.9-1.1.

[0042] In an optional embodiment, in addition to increasing the second type of subtasks in the second target object group, when the ratio of the total resource amount of the first target object group to the total resource amount of the second target object group is lower than the set second threshold, the second type of subtasks in the second target object group can be deleted. Optionally, according to the ratio of the total resource amount of the first target object group to the total resource amount of the second target object group and the second threshold, from the dimension of the second type of resource account, a set proportion of the second type of resource accounts in the task are deleted, and then the first type of subtasks and the second type of subtasks that need to be executed by this second type of resource account will be deleted.

[0043] In some alternative embodiments of the present application, to improve the fault tolerance performance, during the execution of subtasks by the second type of resource accounts, if a subtask is blocked or delayed for longer than a set duration, the subtask is deleted to ensure the stability of the social platform. Specifically, after randomly determining a target time point in the target task period, the target subtask can also be added to a task delay queue according to the target time point. The task delay queue includes subtasks corresponding to each second type of resource account stored in the order of the execution time points. Based on the task delay queue, the subtasks of each second type of resource account in the second type of object group can be executed in a second execution order, and the subtasks stored in the task delay queue can be triggered at a set time point. If the target subtask fails to be executed at the target time point, and the current time and the duration later than the target time point are greater than a set duration threshold, the target subtask is deleted from the task delay queue.

[0044] It should be noted that the execution entity of each step of the method provided in the above embodiments can be the same device, or the method can also be executed by different devices as the execution entity. For example, the execution entity of steps 101 to 103 can be device A; for another example, the execution entity of steps 101 and 102 can be device A, and the execution entity of step 103 can be device B; and so on.

[0045] In addition, in some processes described in the above embodiments and the accompanying drawings, there are multiple operations that appear in a specific order. However, it should be clearly understood that these operations can be executed not in the order in which they appear in this document or in parallel. The operation numbers such as 101, 102, etc. are only used to distinguish different operations, and the numbers themselves do not represent any execution order. In addition, these processes can include more or fewer operations, and these operations can be executed in sequence or in parallel. It should be noted that the descriptions such as "first" and "second" in this document are used to distinguish different messages, devices, modules, etc., do not represent a sequence, and do not limit that "first" and "second" are of different types.

[0046] Figure 4 This is a schematic structural diagram of a task control device for a social platform provided by an exemplary embodiment of the present application. As Figure 4 shown, the device includes: a memory 44 and a processor 45.

[0047] The memory 44 is used to store computer programs and can be configured to store various other data to support operations on the task control device. Examples of these data include instructions for any application program or method operating on the task control device.

[0048] The memory 44 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk or optical disk.

[0049] The processor 45, coupled to the memory 44, is configured to execute a computer program in the memory 44 for: in response to a trigger operation of a first type of object group participating in a task, generating a second type of object group and N sub-tasks that the second type of object group needs to complete, where the second type of object group has a competitive relationship with the first type of object group and includes at least one second type of resource account, N is a positive integer and N≥2; determining a plurality of task time periods during the execution of the task according to the duration of the task, and establishing a correspondence relationship among at least one second type of resource account, N sub-tasks, and the plurality of task time periods; for any second type of resource account, determining a target task time period and a target sub-task corresponding to the any second type of resource account according to the correspondence relationship, randomly determining a target time point in the target task time period, executing the target sub-task when the target time point arrives, and updating the resource data in the any second type of resource account according to the execution result of the target sub-task.

[0050] In an alternative embodiment, when the processor 45 generates a second type of object group and N sub-tasks that the second type of object group needs to complete in response to a trigger operation of a first type of object group participating in a task, it is specifically configured to: in response to the trigger operation of the first type of object group participating in the task, obtain information on historical sub-tasks completed by the first type of object group and the number of first type of resource accounts included in the first type of object group; determine the number of resource accounts required for the second type of object group according to the number of first type of resource accounts, and generate at least one second type of resource account for the second type of object group according to the number of resource accounts required for the second type of object group; determine N sub-tasks that the second type of object group needs to complete according to the information on historical sub-tasks completed by the first type of object group.

[0051] In an alternative embodiment, the sub-task set corresponding to the task includes K types of sub-tasks, and each type of sub-task corresponds to a fixed amount of resources, where K≥2 and K is an integer; when the processor 45 determines N sub-tasks that the second type of object group needs to complete according to the information on historical sub-tasks completed by the first type of object group, it is specifically configured to: determine the range of the total amount of resources that can be allocated to the second type of object group according to the amount of resources corresponding to the historical sub-tasks completed by the first type of object group; perform task combination on at least one type of sub-task among the K types of sub-tasks according to the amount of resources corresponding to each type of sub-task among the K types of sub-tasks and the range of the total amount of resources, to form N sub-tasks that the second type of object group needs to complete, and the sum of the amounts of resources corresponding to the N sub-tasks is within the range of the total amount of resources.

[0052] In an alternative embodiment, the K seed tasks include a first type of subtask with a limited number of executions and a second type of subtask with an unlimited number of executions. When the processor 45 forms N subtasks to be completed by the second type of object group by combining at least one of the K seed tasks according to the resource amount corresponding to each seed task in the K seed tasks and the total resource range, it is specifically configured to: combine at least one of the first type of subtasks according to the resource amount and the number of executions corresponding to each subtask in the first type of subtasks, in combination with the total resource range, to form N1 subtasks, where the number of occurrences of the same subtask in the N1 subtasks is less than the number of executions corresponding to the subtask; if the sum of the resource amounts corresponding to the N1 subtasks is less than the lower limit value of the total resource range, calculate the difference between the upper limit value of the total resource range and the sum of the resource amounts corresponding to the N1 subtasks; combine at least one of the second type of subtasks according to the difference and the resource amount corresponding to each subtask in the second type of subtasks to form N2 subtasks, where the sum of the resource amounts corresponding to the N2 subtasks is less than or equal to the difference; where N1 and N2 are positive integers, and N1 + N2 = N.

[0053] In an alternative embodiment, when the processor 45 establishes the correspondence between at least one second type of resource account, N subtasks, and multiple task periods, it is specifically configured to: aim at each second type of resource account corresponding to a first type of subtask, establish the correspondence between the N1 subtasks and at least one second type of resource account, and randomly establish the correspondence between the N2 subtasks and at least one second type of resource account; sort the subtasks corresponding to at least one second type of resource account according to the type of subtasks, and cross-sort the sorted subtasks of at least one second type of resource account to obtain a subtask queue; allocate the subtasks in the subtask queue to each task period in sequence according to the task amount corresponding to each task period, and establish the correspondence between at least one second type of resource account, N subtasks, and multiple task periods according to the subtasks allocated to each task period and the subtasks corresponding to at least one second type of resource account.

[0054] In an alternative embodiment, before allocating the subtasks in the subtask queue to each task period in sequence according to the task amount corresponding to each task period, the processor 45 is further configured to: determine the task amount ratio corresponding to multiple task periods according to the number of historical subtasks corresponding to multiple task periods; obtain the task amount corresponding to each task period according to the task amount ratio corresponding to multiple task periods and the number of N subtasks.

[0055] In an alternative embodiment, there are multiple groups of first-type objects, and the processor 45 is further configured to: calculate the total resource amount of each group of first-type objects according to the resource data of each first-type resource account in each group of first-type objects, and obtain the group of first-type objects whose total resource amount is greater than the set resource threshold as the first target object group; use the group of second-type objects that has a competitive relationship with the first target object group as the second target object group, and calculate the total resource amount of the second target object group according to the resource data of each second-type resource account in the second target object group; adjust the number of second-type subtasks in the second target object group according to the ratio of the total resource amount of the first target object group to the total resource amount of the second target object group.

[0056] In an alternative embodiment, when the processor 45 adjusts the number of second-type subtasks in the second target object group according to the ratio of the total resource amount of the first target object group to the total resource amount of the second target object group, it is specifically configured to: increase the second-type subtasks in the second target object group when the ratio of the total resource amount of the first target object group to the total resource amount of the second target object group exceeds the set first threshold; or delete the second-type subtasks in the second target object group when the ratio of the total resource amount of the first target object group to the total resource amount of the second target object group is lower than the set second threshold.

[0057] In an alternative embodiment, after randomly determining the target time point in the target task period, the processor 45 is further configured to: add the target subtask to the task delay queue according to the target time point, where the task delay queue includes N subtasks that need to be completed by the group of second-type objects stored in the order of the execution time points; if the target subtask fails to be executed at the target time point, and the current time and the duration that is later than the target time point and longer than the target time point is greater than the set duration threshold, delete the target subtask data from the task delay queue.

[0058] The task control device provided by the embodiments of the present application generates a group of second-type objects that have a competitive relationship for the group of first-type objects composed of users, creates second-type resource accounts in the group of second-type objects and N subtasks that need to be completed by the second-type resource accounts, distributes the N subtasks that need to be completed by the second-type resource accounts to multiple task periods, and for each task period, sets a random task execution time for the subtasks assigned to that task period, so that the time for the second-type resource accounts to execute the subtasks is no longer fixed, and the second-type resource accounts can execute the task data at random time points, improving the user experience and the fun of the task, and increasing the user activity and platform stickiness.

[0059] Further, as Figure 4 shown, the task control device further includes other components such as a communication component 46, a display 47, a power supply component 48, and an audio component 49. Figure 4Only some components are schematically shown, which does not mean that the task control device only includes Figure 4 the components shown. It should be noted that Figure 4 the components within the dashed box in are optional components, rather than mandatory components, and can be determined according to the product form of the task control device specifically.

[0060] Correspondingly, an embodiment of the present application further provides a computer-readable storage medium storing a computer program, which when executed by a processor, enables the processor to implement Figure 1 each step in the method shown.

[0061] Correspondingly, an embodiment of the present application further provides a computer program product, including a computer program / instructions, which when executed by a processor, enables the processor to implement Figure 1 each step in the method shown.

[0062] The above Figure 4 The communication component in is configured to facilitate communication between the device where the communication component is located and other devices in a wired or wireless manner. The device where the communication component is located can access a wireless network based on a communication standard, such as WiFi, 2G, 3G, 4G / LTE, 5G and other mobile communication networks, or a combination thereof. In an exemplary embodiment, the communication component receives a broadcast signal or broadcast-related information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communication component further includes a Near Field Communication (NFC) module to facilitate short-range communication. For example, the NFC module can be implemented based on Radio Frequency Identification (RFID) technology, Infrared Data Association (IrDA) technology, Ultra Wideband (UWB) technology, Bluetooth (BT) technology and other technologies.

[0063] The above Figure 4 The display in includes a screen, and the screen can include a Liquid Crystal Display (LCD) and a Touch Panel (TP). If the screen includes a touch panel, the screen can be implemented as a touch screen to receive input signals from a user. The touch panel includes one or more touch sensors to sense touches, swipes and gestures on the touch panel. The touch sensors can not only sense the boundaries of touch or swipe actions, but also detect the duration and pressure associated with the touch or swipe operation.

[0064] The above Figure 4 The power supply component in provides power for various components of the device where the power supply component is located. The power supply component can include a power management system, one or more power supplies, and other components associated with generating, managing and distributing power for the device where the power supply component is located.

[0065] The above Figure 4The audio component therein can be configured to output and / or input audio signals. For example, the audio component includes a microphone (MIC). When the device where the audio component is located is in an operation mode, such as a call mode, a recording mode, and a voice recognition mode, the microphone is configured to receive external audio signals. The received audio signals can be further stored in a memory or sent via a communication component. In some embodiments, the audio component further includes a speaker for outputting audio signals.

[0066] Those skilled in the art should understand that the embodiments of the present application can be provided as a method, a system, or a computer program product. Therefore, the present application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Moreover, the present application can take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0067] The present application is described with reference to the flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each flow and / or block in the flowcharts and / or block diagrams, as well as the combination of flows and / or blocks in the flowcharts and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to the processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing devices to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing devices generate means for implementing the functions specified in Figure 1 one or more flows and / or Figure 1 blocks.

[0068] These computer program instructions can also be stored in a computer-readable memory that can direct a computer or other programmable data processing device to work in a specific manner, so that the instructions stored in the computer-readable memory generate a manufactured article including instruction means, and the instruction means implements the functions specified in Figure 1 one or more flows and / or Figure 1 blocks.

[0069] These computer program instructions can also be loaded onto a computer or other programmable data processing device, so that a series of operation steps are executed on the computer or other programmable device to generate a computer-implemented process. Thus, the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in Figure 1 one or more flows and / or Figure 1 blocks.

[0070] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0071] The memory may include non-permanent storage in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. The memory is an example of a computer-readable medium.

[0072] Computer readable media include permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. Information can be computer readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include temporary computer readable media (transitory media), such as modulated data signals and carrier waves.

[0073] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.

[0074] The above are only embodiments of the present application and are not intended to limit the present application. For those skilled in the art, the present application may have various changes and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included within the scope of the claims of the present application.

Claims

1. A task control method, characterized in that, Including: On a social platform, in response to a trigger operation for a first type of object group to participate in a task, a second type of object group and N sub-tasks that the second type of object group needs to complete are generated. The second type of object group has a competitive relationship with the first type of object group and includes at least one second type of resource account. N is a positive integer and N≥2; The sub-task set corresponding to the task includes K sub-tasks, each sub-task corresponding to a fixed amount of resources. K≥2 and K is an integer. The K sub-tasks include a first type of sub-task with a limited execution number and a second type of sub-task without a limited execution number. The N sub-tasks are formed by task combination of at least one of the K sub-tasks according to the resource amounts of the K sub-tasks, the execution number of the first type of sub-task, and the total resource range of the second type of object group; The total resource range that can be allocated to the second type of object group is dynamically generated based on the resource amounts corresponding to the historical sub-tasks completed by the first type of object group, so that the strength of the second type of object group matches that of the first type of object group; According to the duration of the task, multiple task periods during the execution of the task are determined, and a corresponding relationship is established among the at least one second type of resource account, the N sub-tasks, and the multiple task periods; For any second type of resource account, according to the corresponding relationship, determine the target task period and the target sub-task corresponding to the any second type of resource account, and randomly determine the target time point in the target task period. Add the target sub-task to the task delay queue according to the target time point. The task delay queue includes the N sub-tasks that the second type of object group needs to complete, stored in the order of the execution time points. If the target sub-task fails to be executed at the target time point and the duration when the current time is later than the target time point is greater than the set threshold, delete the target sub-task from the task delay queue; Execute the target sub-task when the target time point arrives, and update the resource data in the any second type of resource account according to the execution result of the target sub-task.

2. The method according to claim 1, wherein In response to a trigger operation for a first type of object group to participate in a task, generating a second type of object group and N sub-tasks that the second type of object group needs to complete, including: In response to the trigger operation for the first type of object group to participate in the task, obtain the information of the historical sub-tasks completed by the first type of object group and the number of first type of resource accounts included in the first type of object group; According to the number of the first type of resource accounts, determine the number of resource accounts required for the second type of object group, and generate at least one second type of resource account for the second type of object group according to the number of resource accounts required for the second type of object group; According to the information of the historical sub-tasks completed by the first type of object group, determine the N sub-tasks that the second type of object group needs to complete.

3. The method according to claim 2, characterized in that, According to the information of the historical sub-tasks completed by the first type of object group, determining the N sub-tasks that the second type of object group needs to complete, including: Determine the range of the total resources allocable to the second type of object group according to the resource amount corresponding to the historical subtasks completed by the first type of object group; According to the resource amount corresponding to each of the K subtasks and the range of the total resource amount, perform task combination on at least one of the K subtasks to form N subtasks that the second type of object group needs to complete, and the sum of the resource amounts corresponding to the N subtasks is within the range of the total resource amount.

4. The method according to claim 3, wherein According to the resource amount corresponding to each of the K subtasks and the range of the total resource amount, perform task combination on at least one of the K subtasks to form N subtasks that the second type of object group needs to complete, including: According to the resource amount and the execution times corresponding to each subtask in the first type of subtasks, and in combination with the range of the total resource amount, perform combination on at least one of the first type of subtasks to form N1 subtasks, where the number of occurrences of the same subtask in the N1 subtasks is less than the execution times corresponding to the subtask; If the sum of the resource amounts corresponding to the N1 subtasks is less than the lower limit value of the range of the total resource amount, calculate the difference between the upper limit value of the range of the total resource amount and the sum of the resource amounts corresponding to the N1 subtasks; According to the difference and the resource amount corresponding to each of the second type of subtasks, perform task combination on at least one of the second type of subtasks to form N2 subtasks, where the sum of the resource amounts corresponding to the N2 subtasks is less than or equal to the difference; where N1 and N2 are positive integers, and N1 + N2 = N.

5. The method according to claim 4, characterized in that Establish the corresponding relationship among the at least one second type of resource account, the N subtasks, and the multiple task time periods, including: Aiming at each second type of resource account corresponding to a first type of subtask, establish the corresponding relationship between the N1 subtasks and the at least one second type of resource account, and randomly establish the corresponding relationship between the N2 subtasks and the at least one second type of resource account; Sort the subtasks corresponding to the at least one second type of resource account according to the type of subtasks respectively, and perform cross sorting on the sorted subtasks of the at least one second type of resource account to obtain a subtask queue; according to the task amount corresponding to each task time period, allocate the subtasks in the subtask queue to each task time period in sequence, and establish the corresponding relationship among the at least one second type of resource account, the N subtasks, and the multiple task time periods according to the subtasks allocated to each task time period and the subtasks corresponding to the at least one second type of resource account.

6. The method according to claim 5, wherein Before allocating the subtasks in the subtask queue to each task time period in sequence according to the task amount corresponding to each task time period, it further includes: Determine the task amount ratio corresponding to the multiple task time periods according to the number of historical subtasks corresponding to the multiple task time periods; Obtain the task amount corresponding to each task time period according to the task amount ratio corresponding to the multiple task time periods and the number of the N subtasks.

7. The method according to claim 4, characterized in that, There are multiple first types of object groups, and the method further includes: Calculate the total resource volume of each first - type object group respectively according to the resource data of each first - type resource account in each first - type object group, and obtain the first - type object groups whose total resource volume is greater than the set resource threshold as the first target object groups; Take the second - type object groups that have a competitive relationship with the first target object groups as the second target object groups, and calculate the total resource volume of the second target object groups according to the resource data in each second - type resource account of the second target object groups; Adjust the number of second - type subtasks in the second target object groups according to the ratio of the total resource volume of the first target object groups to the total resource volume of the second target object groups.

8. The method according to claim 7, wherein Adjusting the number of second - type subtasks in the second target object groups according to the ratio of the total resource volume of the first target object groups to the total resource volume of the second target object groups includes: When the ratio of the total resource volume of the first target object groups to the total resource volume of the second target object groups exceeds the set first threshold, increase the second - type subtasks in the second target object groups; Or, When the ratio of the total resource volume of the first target object groups to the total resource volume of the second target object groups is lower than the set second threshold, delete the second - type subtasks in the second target object groups.

9. A task control device, characterized in that, Includes: A memory and a processor; The memory is used to store a computer program; The processor, coupled to the memory, is used to execute the computer program to implement the steps in the method according to any one of claims 1 - 8.

10. A computer-readable storage medium storing a computer program, characterized in that, When the computer program is executed by the processor, it causes the processor to implement the steps in the method according to any one of claims 1 - 8.

11. A computer program product comprising a computer program / instructions, characterized in that, When the computer program / instructions are executed by the processor, it causes the processor to implement the steps in the method according to any one of claims 1 - 8.

Images