Method and system for optimizing task distribution and computing equipment

Abstract

The invention provides a method and system for optimizing task distribution and computing equipment, and the method comprises the steps: generating a material table record which comprises a material identifier, a material type and material content, and the material content points to a target material; group delineation is carried out according to task object identifiers associated with the tasks, and task objects are divided into groups with different group identifiers according to preset rules or conditions; according to the material table record, a distribution task table record is created, and the distribution task table record comprises a corresponding task identifier, a channel identifier, a distribution task type, the material identifier and the group identifier; and creating different distribution tasks for asynchronous execution based on the distribution task table record according to the distribution task type. According to the technical scheme, task object requirements can be more quickly and accurately understood and met, search complexity and efficiency are improved, and the method has high applicability and universality and is rich in applicable scene.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of e-commerce, in particular to a method and system for optimizing task distribution and a computing device. BACKGROUND

[0002] In the case of multi-channel operation of an e-commerce platform based on a social software ecosystem, the traditional single-channel distribution method cannot meet the increasingly complex needs of task objects, and cannot effectively improve the information reach rate and task object coverage rate. The difference in group characteristics determines the distribution effect of different distribution methods and channels for different task objects.

[0003] Therefore, a technical solution is needed to meet the increasingly complex needs of task objects, effectively improve the information reach rate and task object coverage rate, and improve distribution efficiency. SUMMARY

[0004] The present application aims to provide a method and system for optimizing task distribution and a computing device, which can meet the increasingly complex needs of task objects, effectively improve the information reach rate and task object coverage rate, and improve distribution efficiency.

[0005] According to an aspect of the present application, a method for optimizing task distribution is provided, the method comprising:

[0006] Generating a material table record, the material table record including a material identifier, a material type, and a material content, the material content pointing to a target material;

[0007] According to the task-associated task object identifier, the task objects are divided into groups with different group identifiers according to predetermined rules or conditions;

[0008] According to the material table record, a distribution task table record is created, the distribution task table record including a corresponding task identifier, a channel identifier, a distribution task type, the material identifier, and the group identifier;

[0009] According to the distribution task type, different asynchronous tasks are created based on the distribution task table record.

[0010] According to some embodiments, according to the distribution task type, different asynchronous tasks are created based on the distribution task table record, including:

[0011] If the distribution task type is an event-driven task, the distribution task table record is connected to at least one event source and a corresponding asynchronous task is created for asynchronous execution.

[0012] According to some embodiments, according to the distribution task type, different asynchronous tasks are created based on the distribution task table record, including:

[0013] If the distribution task type is a non-event-driven task, polling execution is performed by a task scheduling system.

[0014] According to some embodiments, creating a distribution task table record comprises:

[0015] Group verification is performed to determine whether the corresponding group is valid;

[0016] Channel verification is performed to determine whether the corresponding channel is open;

[0017] Material verification is performed to determine whether the corresponding material exists and is valid;

[0018] Frequency verification is performed to determine whether the frequency limit is valid;

[0019] After the verification is completed, the distribution task table record is created.

[0020] According to some embodiments, after the distribution task table record is created, further comprising:

[0021] Asynchronous post-processing is performed on the distribution task table record.

[0022] According to some embodiments, performing asynchronous post-processing on the distribution task table record comprises:

[0023] Performing corresponding specific processing on different distribution tasks.

[0024] According to some embodiments, the distribution task table record contains a task state, and the task state has four values of new state, effective state, pause state, and invalid state.

[0025] According to some embodiments, after the distribution task table record is created, the task state is changed to the new state.

[0026] According to some embodiments, when the distribution task table record is in the new state, after the asynchronous post-processing is completed, the task state is changed to the effective state, and the distribution task in the effective state is executed.

[0027] According to some embodiments, when the distribution task in the effective state is paused, the task state is changed to the pause state, the distribution task in the pause state is not executed, and the pause state can be changed to the effective state or the invalid state.

[0028] According to some embodiments, the invalid state cannot be modified again, and is the final state of the distribution task.

[0029] According to some embodiments, the frequency verification comprises:

[0030] determining whether to limit access traffic to a system or service; and / or

[0031] determining whether to limit the frequency of task object behavior or system resource usage.

[0032] According to another aspect of the present application, there is provided a computer program product comprising a computer program which, when executed by a processor, implements the method of any one of the above.

[0033] According to another aspect of the present application, there is provided a computing device comprising:

[0034] a processor;

[0035] a memory storing a computer program which, when executed by the processor, implements the method of any one of the above.

[0036] According to embodiments of the present application, by generating a material table record, grouping according to the task object identifier associated with the task, and dividing the task objects into groups with different group identifiers according to predetermined rules or conditions. Then according to the material table record, create a distribution task table record, and finally create different distribution task asynchronous execution based on the distribution task table record according to the distribution task type. The present application divides the distribution task according to the task object identifier and the group circle, which can meet the growing complex needs of task objects, effectively improve the arrival rate of information and the participation of task objects, improve the distribution efficiency, and enhance the experience of task objects.

[0037] According to some embodiments, by performing task object identifier circle, group circle and material table creation, then creating a distribution task table, managing task data makes data management more efficient, visual, quantifiable and flexible. According to the task distribution table, create a distribution task, build an asynchronous task, post-process the distribution task, improve the stability of the task through the asynchronous task, separate the distribution task from other application logic, and reduce the system complexity.

[0038] According to some embodiments, event-driven according to the distribution task type, and updating the record data of the task distribution table, updating the record data in the task distribution table can track the changes of various indicators in real time, such as sending success rate, task object click rate, etc., in order to meet the complex needs of task objects and effectively improve the distribution efficiency.

[0039] According to some embodiments, non-group distribution is often a "one-size-fits-all" approach, which may result in a mismatch between information and target audience. The present application distributes in groups, which can provide more targeted content or products according to the preferences and needs of different task objects, thereby improving the relevance and effectiveness of information.

[0040] According to some embodiments, the degree of care and attention that the task objects feel through the complex distribution is improved, thereby improving their satisfaction and loyalty. Group distribution can better meet the actual needs of task objects, thereby improving purchase intention and conversion rate.

[0041] According to some embodiments, the response and behavior patterns of different task object groups may differ significantly, and group distribution helps optimize the allocation of marketing resources, more reasonably evaluate and adjust the input-output ratio, and thereby improve marketing efficiency.

[0042] According to some embodiments, the task distribution scheme provided by the present application can help the platform better understand the characteristics of different task object groups through data analysis, achieve more refined management and decision-making, reduce marketing noise, and significantly reduce unnecessary marketing information interference, optimize information reception of task objects, and avoid negative effects caused by information bombardment.

[0043] It should be understood that the above general description and the following detailed description are only exemplary and do not limit the present application. BRIEF DESCRIPTION OF DRAWINGS

[0044] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed in the embodiment description will be briefly introduced as follows.

[0045] Figure 1 A flowchart of a method for optimizing task distribution according to an example embodiment is shown.

[0046] Figure 2 A flowchart of creating a task according to an example embodiment is shown.

[0047] Figure 3 A schematic diagram of task state flow according to an example embodiment is shown.

[0048] Figure 4 A flowchart of a timing task polling according to an example embodiment is shown.

[0049] Figure 5 A flowchart of event-driven according to an example embodiment is shown.

[0050] Figure 6 A schematic diagram of the overall scheme according to an example embodiment is shown.

[0051] Figure 7 A block diagram of a computing device according to an example embodiment is shown. DETAILED DESCRIPTION

[0052] Exemplary embodiments will now be described more fully with reference to the accompanying drawings. However, these exemplary embodiments can be implemented in many forms and should not be construed as limited to the embodiments set forth herein; rather, they are provided so that the invention will be thorough and complete, and the concept of the exemplary embodiments will be fully conveyed to those skilled in the art. The same reference numerals in the drawings denote the same or similar parts, and therefore repeated descriptions of them will be omitted.

[0053] Furthermore, the described features, structures, or characteristics can be combined in any suitable manner in one or more embodiments. Numerous specific details are provided in the following description to give a full understanding of embodiments of the invention. However, those skilled in the art will recognize that the technical solutions of the invention can be practiced without one or more of the specific details, or other methods, components, apparatuses, steps, etc., can be employed. In other instances, well-known methods, apparatuses, implementations, or operations are not shown or described in detail to avoid obscuring various aspects of the invention.

[0054] The block diagrams shown in the accompanying drawings are merely functional entities and do not necessarily correspond to physically independent entities. That is, these functional entities can be implemented in software, in one or more hardware modules or integrated circuits, or in different network and / or processor devices and / or microcontroller devices.

[0055] The flowcharts shown in the accompanying drawings are merely illustrative and do not necessarily include all content and operations / steps, nor do they necessarily have to be performed in the described order. For example, some operations / steps can be broken down, while others can be combined or partially combined; therefore, the actual execution order may change depending on the specific circumstances.

[0056] It should be understood that although the terms first, second, third, etc., may be used herein to describe various components, these components should not be limited by these terms. These terms are used to distinguish one component from another. Therefore, the first component discussed below may be referred to as the second component without departing from the teachings of the present invention. As used herein, the term "and / or" includes all combinations of any one and more of the associated listed items.

[0057] The task object information (including but not limited to task object equipment information, task object personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this invention are all information and data authorized by the task object or fully authorized by all parties. Furthermore, the collection, use and processing of related data must comply with the relevant laws, regulations and standards of the relevant countries and regions, and corresponding operation entry points are provided for the task object to choose to authorize or refuse.

[0058] Those skilled in the art can understand that the drawings are only schematic views of example embodiments, and the modules or flows in the drawings are not necessarily essential for implementing the present application, and therefore cannot be used to limit the protection scope of the present application.

[0059] In the wave of digital transformation, online shopping has become an important part of our lives. E-commerce platforms in the operation of social software ecology are in a period of rapid application growth, and need to carry out fine operation on different groups. Different social platforms have different task object groups, usage habits and content forms, so it is crucial to choose a social platform that suits your product or service. High-quality content is also the key to attracting task objects. Interesting, useful or educational content can attract the attention of target audiences, and cleverly integrate product information to build a brand community that can enhance the sense of belonging and loyalty of task objects. By organizing online activities, providing exclusive discounts, etc., encourage task objects to participate and interact, and form a good community atmosphere. Continuously track and analyze various data indicators such as click-through rate, conversion rate, and task object dwell time, and continuously adjust and optimize operation strategies based on data feedback to achieve the desired effect.

[0060] To this end, the present application provides a method for optimizing task distribution, which can meet the increasing complex needs of task objects, effectively improve the arrival rate of information and the participation of task objects, improve the distribution efficiency, and enhance the experience of task objects.

[0061] The example embodiments of the present application will be described below with reference to the accompanying drawings.

[0062] Figure 1 A flowchart of a method for optimizing task distribution according to an example embodiment is shown.

[0063] In S101, a material table record is generated, which includes material identification, material type and material content, and the material content points to the target material.

[0064] According to some embodiments, task object identification, group identification and material table creation are first performed. The material table record includes material identification number, material type, material content, creator number, creator nickname, creation time and modification time, and the material content points to the real material. The distribution task table record is created according to the task object identification, the group and the material table record, wherein the distribution task table contains the material identification number associated with the material table.

[0065] According to some embodiments, the task object identification and the group delineation and the creation of the material are performed in the group system, a material table record is generated, which mainly records the material type and different material content, wherein the material content points to a real material such as a picture, a video, a script and a picture-text, and a distribution task table record is created according to the material table record, and the state is new.

[0066] According to some embodiments, the table design of the material table record is shown in Table 1.

[0067] Table 1

[0068] Name Comment Data Type material_id Material ID INTEGER material_type Material Type INTEGER content Content VARCHAR creator_workid Creator Work ID VARCHAR creator_name Creator Name VARCHAR create_time Creation Time DATE modify_time Modification Time DATE

[0069] In S103, the group delineation is performed according to the task object identification associated with the task, and the task objects are divided into groups with different group identifiers according to predetermined rules or conditions.

[0070] According to some embodiments, the task object identification and the group delineation and the creation of the material are performed in the group system.

[0071] According to some embodiments, the group system or the task object group system is a tool or platform for dividing task objects into different groups according to specific rules or conditions by analyzing task object data. Its core function is to identify task objects and delineate target groups, helping application parties to achieve precise operation, complex service and data-driven decision-making.

[0072] According to some embodiments, the task object identification includes active task objects, mommies and young people, etc., which are usually produced offline or in real time by data analysis.

[0073] In S105, a distribution task table record is created according to the material table record, and the distribution task table record includes corresponding task identifier, channel identifier, distribution task type, material identifier and group identifier.

[0074] According to some embodiments, based on the group and the task object identification, the distribution task table is created according to the material table record, which can create complex distribution tasks, meet the complex needs of task objects, effectively improve the information reach rate and the participation of task objects, and improve the distribution efficiency. The table design of the distribution task table record is shown in Table 2.

[0075] Table 2

[0076]

[0077] According to some embodiments, according to the material identification number in the task distribution table record, the corresponding material table record is obtained; according to the material type and the material content in the material table record, the real material required for creating the distribution task is obtained.

[0078] According to some embodiments, referring to Figure 2 , the creation of the task requires the selection or creation of materials, where the materials refer to the material record table records described above, and according to different material types, the corresponding real materials are found from the material content. For example, the real materials include material information directly presented to the task object, such as specific articles, images, and texts, etc. The material record table records have a mapping relationship from the material ID to the real materials, and the specific material content can be located through the record of the material record table.

[0079] According to some embodiments, various verifications are required before creating the distribution task table record. Group verification is performed to determine whether the corresponding group is valid; channel verification is performed to determine whether the corresponding channel is open; material verification is performed to determine whether the corresponding material exists and is valid; and frequency verification is performed to determine whether the frequency limit is valid. After the verification is completed, the distribution task table record is created.

[0080] According to some embodiments, the frequency verification includes determining whether to limit the access traffic of the system or service, and determining whether to limit the frequency of use of the task object behavior or system resource.

[0081] According to some embodiments, after the distribution task is created, parameter verification (determining whether the parameters are empty, such as time-related parameters), group verification (determining the group state), channel verification (determining whether the channel is open, such as whether the channel message template is open, for example, the WeChat public number template message distribution task needs the corresponding template id in the WeChat public number background), material verification (determining whether the material exists and is valid), and frequency verification (determining whether the frequency limit is valid, including traffic control and fatigue control) are performed. According to some embodiments, it is also necessary to determine whether tagging is required, for example, the WeChat public number mass distribution channel needs to create a group task object identifier and perform tagging. After the verification is completed, the task record is created, and the asynchronous task is executed for post-processing. Traffic control includes limiting the access traffic of the system or service to prevent system crashes, resource depletion, or performance degradation due to sudden high traffic, which can be achieved through algorithms such as token bucket, funnel, and sliding window. Fatigue control includes limiting the frequency of use of the task object behavior or system resource to prevent the loss of task objects, waste of resources, or decline in experience due to excessive use. For example, a task object can only receive 1 message per day, which can be recorded in a cache middleware similar to redis to record the number of sending times per day. After the verification is completed, the task record is created and the asynchronous post-processing is executed.

[0082] According to some embodiments, after the distribution task table record is created, asynchronous post-processing is performed on the distribution task table record, and the post-processing includes performing corresponding specific processing on different distribution tasks.

[0083] According to some embodiments, the distribution task table record contains a task state, and the task state has four values of a new state, an effective state, a suspended state, and an invalid state. After the distribution task table record is created, the task state is changed to the new state. In the new state, after the asynchronous post-processing is completed, the task state is changed to the effective state, and the distribution task in the effective state is executed. After the distribution task in the effective state is suspended, the task state is changed to the suspended state, and the distribution task in the suspended state is not executed, and the suspended state can be changed to the effective state or the invalid state. The invalid state cannot be modified again and is the final state of the distribution task.

[0084] According to some embodiments, referring to Figure 3 , the distribution task contains a new state, an effective state, a suspended state, and an invalid state. After the distribution task is created, the task state is changed to the new state. In the new state, an asynchronous task is created, the task state is changed to the effective state, and the distribution task in the effective state is executed. After the distribution task in the effective state is suspended, the task state is changed to the suspended state, and the distribution task in the suspended state is not executed. The suspended state can be changed to the effective state and / or the invalid state. The distribution task in the invalid state cannot be modified again and is the final state of the distribution task.

[0085] According to some embodiments, after the task is created, an asynchronous task is created, such as an asynchronous task for marking a public number graphic message. After the asynchronous task is successfully completed, the state is changed to the effective state. The task in the effective state is executed, such as polling only the effective task. The task in the effective state can be suspended, and during the suspension, the task is not executed. The suspended state can be changed to the effective state and the invalid state. The invalid state is the final state, and the task state in the invalid state cannot be modified again.

[0086] According to some embodiments, the state change is performed by the system or manually, such as creating a new distribution task. The state is first new, and after the asynchronous JAVA task post-processing is completed, the state is automatically changed to the effective state. At the same time, the operation personnel can also click “suspend” to modify the task state to the suspended state.

[0087] According to some embodiments, the present application drives precise grouping according to data obtained from material tables, task distribution tables and the like, uses big data and algorithm capabilities to deeply analyze the behavior, interest and consumption habits of task objects through retained identity information or behavior data of the task objects, forms more detailed group portraits, and ensures the precision of the distribution mechanism. The present application performs complex content recommendation through multiple channels based on groups, performs complex content and recommendation systems according to the characteristics of different groups, uses recommendation algorithms to realize dynamic adaptation of content, and improves the participation and conversion rate of task objects.

[0088] In S107, different distribution task asynchronous executions are created based on the distribution task table records according to the distribution task type.

[0089] According to some embodiments, if the distribution task type is an event-driven task, the distribution task table records are connected to at least one event source and corresponding asynchronous tasks are created for asynchronous execution. If the distribution task type is a non-event-driven task, polling execution is performed through a task scheduling system.

[0090] According to some embodiments, asynchronous tasks (task, JAVA asynchronous tasks) are constructed to perform post-processing for distribution tasks, including asynchronously executing some special processing for different distribution tasks, such as creating social software task object identifiers and tagging.

[0091] According to some embodiments, the asynchronous task explicitly indicates the type of the distribution task, the list of task objects that need to be distributed, the distribution content and the trigger condition.

[0092] According to some embodiments, the asynchronous task updates the records in the distribution task table, marks the task status and completion result, collects key indicators such as the sending volume, opening rate, click rate and the like, and stores them in a database for subsequent analysis.

[0093] According to some embodiments, the asynchronous task can improve system performance. Through the asynchronous task, the main program does not need to wait for all distribution tasks to be completed before continuing to perform other operations, thereby improving the response speed of the system. A large number of distribution tasks are distributed to multiple worker nodes for parallel processing, avoiding single-point bottlenecks. Through control of the concurrency and batch processing, flow limiting or blocking due to a large number of calls to the interface of the social software in a short period of time is avoided.

[0094] According to some embodiments, the asynchronous task can improve the experience of task objects. Through the asynchronous task, the behavior of task objects is quickly responded to, the sense of participation and satisfaction of task objects is improved, complex content is generated based on the behavior or preferences of task objects in groups, and precise distribution is realized through the asynchronous task.

[0095] According to some embodiments, the distribution task type is a non-event-driven task and an event-driven task.

[0096] According to some embodiments, when the distribution task type is a non-event-driven task, timing polling is performed, various check logics are executed, distribution of the task is performed, and asynchronous task creation and execution are performed. When the distribution task type is an event-driven task, each event source is queried and various checks are performed, corresponding processing logic is called according to data recorded in the task, and asynchronous tasks are generated for asynchronous execution.

[0097] According to some embodiments, the non-event-driven task is polled by scheduleX, and an instance table record is generated. The table design of the task instance table is shown in Table 3.

[0098] Table 3

[0099] Name Comment Data Type id ID INTEGER task_id Task ID INTEGER status Instance Status / / In execution, success, failure INTEGER result Execution Result VARCHAR create_time Creation Time DATE modify_time Modification Time DATE

[0100] Referring to Figure 4 , for a non-event-driven task, timing polling is performed. First, various check logics are executed, including validity period, execution time, channel, and material, etc. Finally, distribution of the task (different processing methods for different channels) and JAVA asynchronous task creation and execution are performed.

[0101] According to some embodiments, the event-driven task is driven and executed by accessing an event source and having specific events. At the same time, invalidation time, etc. are modified by a task distribution table record, and task logs are recorded by a task operation log table. The task operation log table is shown in Table 4.

[0102] Table 4

[0103]

[0104]

[0105] Referring to Figure 5 , the event-driven task first interfaces each event source, such as a message queue (MQ) of order delivery notification and an MQ of merchant new, etc., then queries relevant records in a task table and performs various checks. Subsequently, corresponding processing logic is called according to channel, material, etc. data recorded in the task, and asynchronous tasks are generated for asynchronous execution. For example, for distribution task records of order delivery notification, etc., a corresponding distribution task can be created after accessing the event source, and execution of the task, validity period, and group are controlled.

[0106] Referring to Figure 6 , Figure 6The overall scheme of the present application is shown. The method of the present application is based on group creation of distribution tasks, according to an embodiment of the present application, by creating a distribution task table, managing task data, so that data management is more efficient, visual, quantifiable and flexible. According to the task distribution table, the distribution task is created, the asynchronous task is constructed, the post-processing is performed for the distribution task, the stability of the task is improved through the asynchronous task, the distribution task is separated from other application logic, and the system complexity is reduced. According to the type of the distribution task, the event driving is performed, and the record data of the task distribution table is updated. Updating the record data in the task distribution table can track the changes of various indicators in real time, such as the sending success rate, the task object click rate, etc., so as to meet the growing complex needs of the task object, effectively improve the information arrival rate and the participation of the task object, improve the distribution efficiency, and enhance the experience of the task object.

[0107] According to some embodiments, non-group distribution tends to be a "one-size-fits-all" approach, which may result in a mismatch between information and target audience. However, the present application distributes in groups, which can provide more targeted content or products according to the preferences and needs of different task objects, thereby improving the relevance and effectiveness of information. For example, for the mom group, articles about infant health and growth can be created, and when creating a distribution task, the identification of the mom group can be constructed using the group system, and then the channel and material records can be constructed. Finally, when executing the task, the mom can be sent articles about infant health and growth, so that the matching degree of information and target audience will be higher.

[0108] According to some embodiments, through complex distribution, the degree of care and attention that the task object feels will be improved, thereby improving their satisfaction and loyalty. Group distribution can better meet the actual needs of the task object, thereby improving the purchase intention and conversion rate.

[0109] According to some embodiments, the response and behavior patterns of different task object groups may differ significantly, and group distribution can help optimize the allocation of marketing resources, more reasonably evaluate and adjust the input-output ratio, and thereby improve marketing efficiency.

[0110] According to some embodiments, the task distribution scheme provided by the present application can help the platform better understand the characteristics of different task object groups through data analysis, achieve more refined management and decision-making, reduce marketing noise, significantly reduce unnecessary marketing information interference, optimize information reception of the task object, and avoid negative effects caused by information bombardment.

[0111] Figure 7 A block diagram of a computing device according to an example embodiment is shown.

[0112] As Figure 7As shown, the computing device 30 includes a processor 12 and a memory 14. The computing device 30 can also include a bus 22, a network interface 16, and an I / O interface 18. The processor 12, the memory 14, the network interface 16, and the I / O interface 18 can communicate with each other through the bus 22.

[0113] The processor 12 can include one or more general-purpose CPUs (Central Processing Units), microprocessors, or application-specific integrated circuits, etc., for executing relevant program instructions. According to some embodiments, the computing device 30 can also include a high-performance display adapter (GPU) 20 for accelerating the processor 12.

[0114] The memory 14 can include machine system readable media in the form of volatile memory, such as random access memory (RAM), read only memory (ROM), and / or cache memory. The memory 14 is used to store one or more programs containing instructions and data. The processor 12 can read the instructions stored in the memory 14 to execute the above-mentioned method according to the embodiments of the present application.

[0115] The computing device 30 can also communicate with one or more networks through the network interface 16. The network interface 16 can be a wireless network interface.

[0116] The bus 22 can include an address bus, a data bus, a control bus, etc. The bus 22 provides a path for exchanging information between the components.

[0117] It should be noted that, in the specific implementation process, the computing device 30 can also include other components necessary for normal operation. In addition, those skilled in the art can understand that the above-mentioned device can also only contain the components necessary to implement the embodiments of the present application, and does not necessarily contain all the components shown in the figure.

[0118] The present application also provides a computer readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of the above-mentioned method. The computer readable storage medium can include but is not limited to any type of disk, including floppy disks, optical disks, DVDs, CD-ROMs, micro-drives, and magneto-optical disks, ROMs, RAMs, EPROMs, EEPROMs, DRAMs, VRAMs, flash memory devices, magnetic or optical cards, nanosystems (including molecular memory ICs), network storage devices, cloud storage devices, or any type of medium or device suitable for storing instructions and / or data.

[0119] The embodiments of the present application also provide a computer program product, which includes a computer program operable to cause a computer to execute some or all of the steps of any one of the methods as described in the above-mentioned method embodiments.

[0120] Those skilled in the art can clearly understand that the technical solutions of the present application can be realized by means of software and / or hardware. The "unit" and "module" in the specification refer to software and / or hardware that can independently complete or cooperate with other components to complete a specific function, and the hardware can be, for example, a field programmable gate array, an integrated circuit, etc.

[0121] It should be noted that, for the foregoing method embodiments, in order to simply describe, they are all expressed as a series of action combinations, but those skilled in the art should know that the present application is not limited by the action sequence described, because according to the present application, certain steps can be performed in other sequences or simultaneously. Secondly, those skilled in the art should know that the embodiments described in the specification all belong to preferred embodiments, and the actions and modules involved are not necessarily necessary for the present application.

[0122] In the above embodiments, the description of each embodiment has its own focus, and the parts not described in detail in a certain embodiment can be referred to the related description of other embodiments.

[0123] In the several embodiments provided by the present application, it should be understood that the disclosed device can be implemented in other ways. For example, the device embodiments described above are only schematic. The division of the units is only a logical function division. There can be another division manner for actual implementation, for example, a plurality of units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the displayed or discussed mutual couplings or direct couplings or communication connections between the units can be indirect couplings or communication connections through some interfaces, devices or units, and can be electrical or other forms.

[0124] The units described as separate components can or can not be physically separate, and the components shown as units can or can not be physical units, i.e. can be located in one place, or can be distributed on a plurality of network units. Part or all of the units can be selected according to actual needs to achieve the purpose of the embodiment.

[0125] In addition, each functional unit in each embodiment of the present application can be integrated into a processing unit, or each unit can exist physically independently, or two or more units can be integrated into one unit. The integrated unit can be realized in the form of hardware or software functional unit.

[0126] The integrated unit, if implemented in the form of a software function unit and sold or used as an independent product, can be stored in a computer readable memory. Based on such understanding, the technical solutions of the present application essentially or the part of the prior art that contributes or the whole or part of the technical solutions can be embodied in the form of a software product. The computer software product is stored in a memory and includes a plurality of instructions for causing a computer device (which can be a personal computer, a server or a network device, etc.) to execute all or part of the steps of the embodiments of the present application.

[0127] In the above embodiments, the description of each embodiment has its own focus, and the parts not described in detail in a certain embodiment can be referred to the relevant description of other embodiments.

[0128] The exemplary embodiments of the present application are specifically shown and described above. It should be understood that the present application is not limited to the detailed structure, arrangement or implementation method described herein; on the contrary, the present application is intended to cover various modifications and equivalent arrangements included in the spirit and scope of the appended clauses.

Claims

1. A method for optimizing task distribution, the method comprising: generating a material table record, the material table record comprising a material identifier, a material type, and a material content, the material content pointing to a target material; grouping according to a task object identifier associated with a task, dividing task objects into groups with different group identifiers according to predetermined rules or conditions; creating a distribution task table record according to the material table record, the distribution task table record comprising a corresponding task identifier, a channel identifier, a distribution task type, the material identifier, and the group identifier; creating different asynchronous tasks based on the distribution task table record according to the distribution task type.

2. The method of claim 1, wherein, creating different asynchronous tasks based on the distribution task table record according to the distribution task type, comprising: if the distribution task type is an event-driven task, then interfacing the distribution task table record with at least one event source and creating a corresponding asynchronous task for asynchronous execution.

3. The method of claim 1, wherein, creating different asynchronous tasks based on the distribution task table record according to the distribution task type, comprising: if the distribution task type is a non-event-driven task, then polling through a task scheduling system.

4. The method of claim 1, wherein, creating a distribution task table record, comprising: group verification, determining whether the corresponding group is valid; channel verification, determining whether the corresponding channel is open; material verification, determining whether the corresponding material exists and is valid; frequency verification, determining whether the frequency limit is valid; after verification is complete, creating the distribution task table record.

5. The method of claim 4, wherein, after creating the distribution task table record, further comprising: performing asynchronous post-processing on the distribution task table record.

6. The method of claim 5, wherein, performing asynchronous post-processing on the distribution task table record, comprising: performing specific processing on different distribution tasks.

7. The method of claim 6, wherein, the distribution task table record contains a task state, the task state having four values: new state, effective state, suspended state, and invalid state.

8. The method of claim 7, wherein, after the distribution task table record is created, the task state changes to the new state.

9. The method of claim 7, wherein, after the asynchronous post-processing is complete in the new state, the task state changes to the effective state, and the distribution task in the effective state is executed.

10. The method of claim 7, wherein, after the distribution task in the effective state is suspended, the task state changes to the suspended state, and the distribution task in the suspended state is not executed, and the suspended state can change to the effective state or the invalid state.

11. The method of claim 7, wherein, the invalid state cannot be modified again and is the final state of the distribution task.

12. The method of claim 4, wherein, the frequency verification comprises: determining whether to limit access traffic to a system or service; and / or determining whether to limit the frequency of task object behavior or system resource usage.

13. A computer program product, characterised in that, a computer program, which, when executed by a processor, implements the method of any one of claims 1-12.

14. A computing device, comprising: comprising: a processor; a memory storing a computer program, which, when executed by the processor, implements the method of any one of claims 1-12.

Images