Task execution method and device, electronic equipment and storage medium

Abstract

The invention provides a task execution method and device, electronic equipment and a storage medium, and relates to the field of artificial intelligence, in particular to the technical fields of big data, cloud computing and the like. According to the specific implementation scheme, a to-be-processed task is executed, so that a target delivery behavior record corresponding to the same object associated with the task type of the to-be-processed task is inquired from a target delivery table; according to a first identifier, a second identifier and a delivery timestamp in the target delivery behavior record, querying a first time zipper table associated with the task type to obtain a target resource occupation ratio of the same object to a service entity of the service under the delivery timestamp; wherein the first time zipper table is used for recording resource occupation proportions of the multiple objects to different service entities in at least one effective time period; based on the target resource occupation proportion and the total resource occupation amount, determining a resource occupation value of the same object to the service entity of the service under the delivery timestamp; and generating a task execution result according to the resource occupation value of each object.

Description

Technical Field

[0001] The present disclosure relates to the field of AI (Artificial Intelligence), specifically to technical fields such as big data and cloud computing, and in particular to task execution methods, devices, electronic devices and storage media. Background Art

[0002] In order to improve the company's refined operation level and assist the company in making correct business management decisions, it is necessary to calculate the resource usage value of the objects associated with the company (such as salesmen, agents, project roles, etc.) for the company's business entities. Therefore, it is very important to calculate the resource usage value of the above objects based on the company's massive business data. Summary of the invention

[0003] The present disclosure provides a method, device, electronic device and storage medium for executing a task.

[0004] According to one aspect of the present disclosure, there is provided a task execution method, comprising:

[0005] Execute the pending task to query the target delivery behavior record corresponding to the same object associated with the task type of the pending task from the target delivery table; wherein the target delivery behavior record includes the first identifier of the same object, the second identifier of the business entity served by the same object, the delivery timestamp and the total amount of resource occupancy;

[0006] According to the first identifier, the second identifier and the delivery timestamp, query the first time zipper table associated with the task type to obtain the target resource occupation ratio of the same object to the business entity of the service at the delivery timestamp; wherein the first time zipper table is used to record the resource occupation ratios of multiple objects to different business entities within at least one effective period;

[0007] Determine, based on the target resource occupation ratio and the total resource occupation, a resource occupation value of the same object for the service entity at the delivery timestamp;

[0008] The execution result of the task to be processed is generated according to the resource occupation value of the corresponding business entity served by each object.

[0009] According to another aspect of the present disclosure, there is provided a task execution device, comprising:

[0010] An execution module, used for executing the pending task, to query the target delivery behavior record corresponding to the same object associated with the task type of the pending task from the target delivery table; wherein the target delivery behavior record includes the first identifier of the same object, the second identifier of the business entity served by the same object, the delivery timestamp and the total amount of resource occupancy;

[0011] A query module, used to query a first time zipper table associated with the task type according to the first identifier, the second identifier and the delivery timestamp, so as to obtain the target resource occupation ratio of the same object to the business entity of the service at the delivery timestamp; wherein the first time zipper table is used to record the resource occupation ratios of multiple objects to different business entities within at least one effective period;

[0012] A determination module, configured to determine, based on the target resource occupation ratio and the total resource occupation, a resource occupation value of the same object for the service entity at the delivery timestamp;

[0013] The first generating module is used to generate the execution result of the task to be processed according to the resource occupation value of the corresponding business entity served by each object.

[0014] According to another aspect of the present disclosure, there is provided an electronic device, comprising:

[0015] at least one processor; and

[0016] a memory communicatively connected to the at least one processor; wherein,

[0017] The memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute the task execution method proposed in the above aspect of the present disclosure.

[0018] According to another aspect of the present disclosure, a non-transitory computer-readable storage medium of computer instructions is provided, wherein the computer instructions are used to enable the computer to execute the task execution method proposed in the above aspect of the present disclosure.

[0019] According to another aspect of the present disclosure, a computer program product is provided, including a computer program, wherein when the computer program is executed by a processor, the task execution method proposed in the above aspect of the present disclosure is implemented.

[0020] It should be understood that the content described in this section is not intended to identify the key or important features of the embodiments of the present disclosure, nor is it intended to limit the scope of the present disclosure. Other features of the present disclosure will become easily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] The accompanying drawings are used to better understand the present solution and do not constitute a limitation of the present disclosure.

[0022] Figure 1 A flowchart of a task execution method provided in the first embodiment of the present disclosure;

[0023] Figure 2 A flowchart of a task execution method provided in the second embodiment of the present disclosure;

[0024] Figure 3 A flowchart of a task execution method provided in Embodiment 3 of the present disclosure;

[0025] Figure 4 A flowchart of a task execution method provided in Embodiment 4 of the present disclosure;

[0026] Figure 5 A flowchart of a task execution method provided in Embodiment 5 of the present disclosure;

[0027] Figure 6 A schematic diagram of the implementation principle of the task execution method provided in each embodiment of the present disclosure;

[0028] Figure 7 This is a schematic diagram of the structure of a task execution device provided in Embodiment 6 of the present disclosure;

[0029] Figure 8 A schematic block diagram of an example electronic device that can be used to implement embodiments of the present disclosure is shown. DETAILED DESCRIPTION

[0030] The following is a description of exemplary embodiments of the present disclosure in conjunction with the accompanying drawings, including various details of the embodiments of the present disclosure to facilitate understanding, which should be considered as merely exemplary. Therefore, it should be recognized by those of ordinary skill in the art that various changes and modifications may be made to the embodiments described herein without departing from the scope and spirit of the present disclosure. Similarly, for the sake of clarity and conciseness, descriptions of well-known functions and structures are omitted in the following description.

[0031] The business data records of a company's massive business scenarios contain timestamps, which are the Greenwich Mean Time when the corresponding real business behavior occurs. For example, the moment when a user successfully completes payment after placing an order, or the moment when the customer's docking salesperson in the CRM (Customer Relationship Management) system changes the setting from employee A to employee B.

[0032] It is very important to calculate the resource occupancy value of objects associated with the enterprise (such as salesmen, agents, project roles, etc.) for the enterprise's business entities based on the timestamps in the business data records, so as to calculate the enterprise's operating costs based on the resource occupancy value of each object.

[0033] Without loss of generality, let's take a scenario where a large number of salespeople of different job levels sell products, and the corporate headquarters calculates the resource usage value (such as the incentive amount) of all salespeople within the company for the sales performance of the product as an example:

[0034] Due to the different business characteristics of each store, the sales staff will have different management mechanisms. For example, different job titles will have different resource utilization ratios (such as incentive ratios or commission ratios) for sales performance. For example, sales staff A's job level is x, and the job level ratio corresponding to job level x is 25%. Sales staff B's ​​job level is y, and the job level ratio corresponding to job level y is 20%. Among them, the job level ratio is used to calculate the resource utilization ratio.

[0035] It should be noted that the job grade information of the same salesperson may change over time, which will affect the salesperson's resource usage ratio. In addition, with the need for refined management of the enterprise, it is sometimes necessary to modify the timestamp corresponding to the salesperson's job grade (i.e., the effective timestamp). For example, the following three cases can be used to modify the effective timestamp corresponding to the salesperson's job grade:

[0036] Case 1: The actual time when the salesperson is promoted to a higher professional title is 2024-07-01. However, in order to improve the incentive effect, it needs to take effect one quarter in advance, that is, from 2024-04-01. At this time, the effective timestamp corresponding to the salesperson's professional title needs to be changed from 2024-07-01 to 2024-04-01.

[0037] Case 2: In order to reduce costs and increase efficiency, two operations are performed for all job titles x. The effective timestamp is uniformly delayed by one quarter, and the indicator column (i.e., job level ratio) after the effective timestamp delay takes effect is uniformly multiplied by a decay ratio (such as 0.9);

[0038] Case 3: For a salesperson who performs well during a probation period (the resource utilization ratio is half of that after formal employment), the salesperson's entry time will be advanced so that the sales results during the probation period can use the resource utilization ratio corresponding to the formal employment.

[0039] Obviously, the needs of business management will require a large number of adjustments to the massive sales management information, and each adjustment will have a different impact on the sales domain, job title domain, and timestamp. Among them, the adjustment of sales management information can be understood as adjusting the effective timestamp, or job grade ratio, or the effective timestamp and job grade ratio for a group of salesmen at a certain job grade.

[0040] In addition to the above-mentioned job level dimension, companies often carry out special impulse stimulus plans at the end of a quarter or year, such as expanding the resource occupancy ratio of the performance of the flagship product series, such as the expansion coefficient is 1.2; reducing the resource occupancy ratio of the performance of the product series at the end of the life cycle, such as the reduction coefficient is 0.8. For example, assuming that the job level of salesperson A is x, the job level ratio corresponding to job level x is 25%, and the adjustment ratio (i.e., product ratio) of product t is 1.1 in the whole month of December at the end of the year. For salesperson A with job level x, the final resource occupancy ratio (i.e., incentive ratio or commission ratio) of selling product t in the whole month of December at the end of the year is 25%*1.1=27.5%. Taking the special impulse stimulus plan as the product dimension and combining it with the job level dimension, a multi-dimensional timestamp matching problem is formed. Product dimension data example: product t, the adjustment ratio (i.e., product ratio) is 1.1, and the effective period of this adjustment ratio (i.e., product ratio) is December.

[0041] The salesperson is marked to have completed the sales delivery behavior at a certain timestamp, and the corresponding total resource occupation (such as the delivery amount or the sales amount) is amount, and the corresponding delivery timestamp (or sales timestamp) is time. Then, the calculation process of the sales performance calculation result (i.e., the resource occupation value, such as the incentive amount) of the sales delivery behavior can be as follows: First, according to the delivery timestamp time, query the sales rank information maintenance table (referred to as the sales table sale) of the tens of millions level, and then load all the rank-timestamp adjustment information in the sales management information adjustment table adjust. After that, adjust and refresh the sales table sale using the loaded information, and then load all the product dimension data in the product dimension expansion coefficient table (referred to as the product table product). Finally, through data processing methods such as full information sorting and multi-dimensional judgment of whether it is hit, find the product dimension corresponding to the delivery timestamp time or the rank dimension corresponding to the rank information and indicator column (i.e., rank ratio or product ratio), and calculate the resource occupation ratio of the performance. According to the product of the resource occupation ratio and amount, calculate the resource occupation value (i.e., the sales performance calculation result, such as the incentive amount), and store the calculation result in the data table.

[0042] In this way, the sales delivery behaviors of a large number of other salesmen can be processed until the resource usage values ​​of all salesmen are calculated.

[0043] As an example, the core business fields in the sales table sale may be shown in Table 1.

[0044] Table 1 Core business fields in sale

[0045] Salesperson Rank Effective timestamp Job level ratio Other business fields Salesperson Level 1 2021-01-01 a-R1 Salesperson Level 2 2022-09-01 a-R2 Salesperson Level 3 2023-09-01 a-R3 Salesperson Level 4 2024-08-01 a-R4 Salesperson B Level 1 2020-08-01 b-r1 Salesperson B Level 2 2024-07-01 b-r2 Salesperson Level 1 2021-07-01 c-r1 …

[0046] As an example, the core business fields in the sales management information adjustment table adjust may be shown in Table 2:

[0047] Table 2 Core business fields in adjust

[0048]

[0049] As an example, the core business fields in the product table product may be shown in Table 3.

[0050] Table 3 Core business fields in product

[0051] product Effective time End effective time Change ratio / product ratio Product 1 2022-12-01 2023-01-01 1.1 Product 1 2023-10-01 2024-01-01 0.9 Product 2 2023-10-01 2024-01-01 1.2 …

[0052] As an example, the core business fields in the sales delivery table delivery for which the resource occupancy value is to be calculated may be as shown in Table 4.

[0053] Table 4 Core business fields in delivery

[0054]

[0055] However, the company's sales rank information maintenance table (abbreviated as sales table sale, as shown in Table 1) is at the tens of millions level, the sales management information adjustment table (as shown in Table 2) is at the millions level, the product dimension expansion coefficient table (abbreviated as product table product, as shown in Table 3) is at the thousands level, and the sales delivery table (as shown in Table 4) is at the billions level. The calculation of a single sales performance calculation result takes dozens of days, and the calculation efficiency is extremely low.

[0056] Therefore, in order to solve the above-mentioned problems, the present disclosure proposes a task execution method, device, electronic device and storage medium.

[0057] The following describes the task execution method, apparatus, electronic device, and storage medium of the embodiments of the present disclosure with reference to the accompanying drawings.

[0058] Figure 1 A flowchart of a task execution method provided in Embodiment 1 of the present disclosure.

[0059] The embodiment of the present disclosure takes the task execution method being configured in a task execution device as an example. The task execution device can be applied to any electronic device so that the electronic device can perform the task execution function.

[0060] Among them, the electronic device can be any device with computing capabilities, such as a personal computer, a mobile terminal, a server, etc. The mobile terminal can be, for example, a mobile phone, a tablet computer, a personal digital assistant, a wearable device, and other hardware devices with various operating systems, touch screens and / or display screens.

[0061] like Figure 1 As shown, the task execution method may include the following steps:

[0062] Step S101, execute the pending task to query the target delivery behavior record corresponding to the same object associated with the task type of the pending task from the target delivery table; wherein the target delivery behavior record includes the first identifier of the same object, the second identifier of the business entity served by the same object, the delivery timestamp and the total amount of resource occupancy.

[0063] Among them, the task to be processed may be a scheduled task to be executed, and the execution cycle of the task to be processed is pre-set. It should be noted that the present disclosure does not limit the specific value of the cycle duration of the execution cycle of the task to be processed, and the cycle duration of the execution cycle can be set according to actual business needs.

[0064] The pending tasks are used to calculate the resource occupation value corresponding to the delivery behavior record in the target delivery table associated with the task type. That is, the resource occupation value of each object associated with the target enterprise to the service business entity can be periodically calculated.

[0065] Among them, the task types of tasks to be processed include but are not limited to: sales incentive tasks (or sales commission calculation tasks), agent incentive tasks (or agent commission calculation tasks), project incentive tasks (or project role reward calculation tasks), etc.

[0066] Among them, the target delivery table is a delivery table associated with the task type of the task to be processed, and the target delivery table includes multiple delivery behavior records. Each delivery behavior record includes the object identifier of an object associated with the target enterprise, the entity identifier of the business entity served by the object, the delivery timestamp and the total amount of resource occupancy.

[0067] Among them, the target enterprise can be any enterprise.

[0068] The objects include, but are not limited to: salespeople within the target enterprise, agents acting as agents for the target enterprise's business entities, and different project roles in the projects carried out by the target enterprise (such as designers, developers, technical leaders, etc.).

[0069] The business entity includes, but is not limited to, the products of the target enterprise, the projects carried out by the target enterprise, etc. For example, in the case of product sales, the object may be a salesperson and the business entity may be a product; in the case of product agency, the object may be an agent and the business entity may be a product; in the case of project development, the object may be a project role and the business entity may be a project.

[0070] For example, when the task type is a sales incentive task, the target delivery table may be the sales delivery table shown in Table 4, and each delivery behavior record in the target delivery table includes the employee ID of a salesperson within the target enterprise, the product ID of the product sold by the salesperson, the delivery timestamp (i.e., the sales timestamp), and the total amount of resources occupied (i.e., the delivery amount or the sales amount); when the task type is an agent incentive task, the target delivery table may be an agent delivery table, and each delivery behavior record in the target delivery table includes the identification information of the agent cooperating with the target enterprise, the product ID of the product represented by the agent, the delivery timestamp (i.e., the sales timestamp), and the total amount of resources occupied (i.e., the delivery amount or the sales amount); when the task type is a project incentive task, the target delivery table may be a project role delivery table, and each delivery behavior record in the target delivery table includes the role ID of the project role of the target enterprise, the project ID of the project served by the project role, the delivery timestamp, and the total amount of resources occupied.

[0071] In an embodiment of the present disclosure, when the execution cycle of a pending task is reached, the pending task can be executed to query the target delivery behavior record corresponding to the same object associated with the task type of the pending task from multiple delivery behavior records in the target delivery table; wherein the target delivery behavior record includes the object identifier of the same object (recorded as the first identifier in the present disclosure), the entity identifier of the business entity served by the same object (recorded as the second identifier in the present disclosure), the delivery timestamp and the total amount of resource occupancy.

[0072] Among them, the number of target delivery behavior records can be at least one.

[0073] Step S102, based on the first identifier, the second identifier and the delivery timestamp, query the first time zipper table associated with the task type to obtain the target resource occupancy ratio of the same object to the service business entity at the delivery timestamp; wherein the first time zipper table is used to record the resource occupancy ratios of multiple objects to different business entities within at least one effective period.

[0074] Among them, the first time zipper table is a time zipper table associated with the task type of the task to be processed, which is used to record the resource occupancy ratio of multiple objects to different business entities within at least one effective period, wherein the effective period is used to indicate the start and end effective times of the resource occupancy ratio.

[0075] In an embodiment of the present disclosure, the first time zipper table associated with the task type of the task to be processed can be queried based on the first identifier, the second identifier and the delivery timestamp in the same target delivery behavior record to obtain the resource occupancy ratio (referred to as the target resource occupancy ratio in the present disclosure) of the business entity (i.e., the business entity indicated by the second identifier) ​​served by the above-mentioned same object at the delivery timestamp.

[0076] Step S103: determining the resource occupation value of the same object for the service entity at the delivery timestamp based on the target resource occupation ratio and the total resource occupation.

[0077] In an embodiment of the present disclosure, the product of the total resource occupancy in the target delivery behavior record and the target resource occupancy ratio can be used as the resource occupancy value of the business entity served by the same object at the delivery timestamp (i.e., the resource occupancy value of the same object in the target delivery behavior record).

[0078] Taking the task type of sales incentive task as an example, the resource usage ratio can be the salesperson's incentive ratio for the product, and the resource usage value can be the salesperson's incentive amount for the product.

[0079] Step S104: generating the execution result of the task to be processed according to the resource occupation value of the corresponding business entity served by each object.

[0080] In the embodiment of the present disclosure, the execution result of the task to be processed may be generated according to the resource occupancy value of the corresponding business entity served by each object, that is, the execution result may include the resource occupancy value under each delivery behavior record.

[0081] The task execution method of the disclosed embodiment maintains a corresponding first-time zipper table for each task type to record the resource occupancy ratios of objects of different job levels to different business entities during different effective periods. Therefore, in the disclosed embodiment, the first-time zipper table associated with the task type of the task to be processed can be directly queried to obtain the target resource occupancy ratio of any object to the business entity it serves at a certain delivery timestamp, and the resource occupancy value of the object can be calculated based on the target resource occupancy ratio, without the need to query multiple data tables to calculate in real time the target resource occupancy ratio of the object to the business entity it serves at the above-mentioned delivery timestamp. This can improve the query efficiency of the resource occupancy ratio, thereby improving the execution efficiency of the tasks to be processed, reducing the waiting time of users, and improving the user experience.

[0082] It should be noted that in the technical solution of the present disclosure, the collection, storage, use, processing, transmission, provision and disclosure of user personal information are all carried out with the user's consent, and are in compliance with relevant laws and regulations and do not violate public order and good morals.

[0083] In order to clearly illustrate how any embodiment of the present disclosure queries a first time zipper table associated with a task type of a task to be processed based on a first identifier, a second identifier and a delivery timestamp, the present disclosure also proposes a task execution method.

[0084] Figure 2 A flowchart of a task execution method provided in Embodiment 2 of the present disclosure.

[0085] like Figure 2 As shown, the task execution method may include the following steps:

[0086] Step S201 , executing the task to be processed to query the target delivery behavior record corresponding to the same object associated with the task type of the task to be processed from the target delivery table.

[0087] The target delivery behavior record includes a first identifier of the same object, a second identifier of the business entity served by the same object, a delivery timestamp, and a total amount of resource usage.

[0088] For the explanation of step S201, reference may be made to the relevant description in any embodiment of the present disclosure, and no further details will be given here.

[0089] Step S202, determine whether there is a first target time zipper record among the multiple first time zipper records in the first time zipper table associated with the task type, if yes, execute steps S203 and S207, if no, execute steps S204 to S207.

[0090] Among them, the first time zipper table contains multiple first time zipper records, each first time zipper record is used to record the object identifier of an object associated with the task type, the entity identifier of the business entity, the resource occupancy ratio, and the mapping relationship between the start effective time and the end effective time of the resource occupancy ratio.

[0091] The first target time zipper record includes a first identifier and a second identifier, and the delivery timestamp is between the start effective time and the end effective time in the first target time zipper record.

[0092] It should be noted that steps S203 and S207 are two parallel implementation methods as well as steps S204 to S207. In actual application, only one needs to be executed.

[0093] Step S203: Use the resource occupancy ratio in the first target time zip record as the target resource occupancy ratio of the same object for the service entity at the delivery timestamp.

[0094] In an embodiment of the present disclosure, when it is determined that there is a first target time zipper record in the first time zipper table based on the first identifier, the second identifier and the delivery timestamp, the resource occupancy ratio in the first target time zipper record can be directly used as the resource occupancy ratio (referred to as the target resource occupancy ratio in the present disclosure) of the business entity (i.e., the business entity indicated by the second identifier) ​​served by the same object at the delivery timestamp.

[0095] Step S204, query the second time zipper table according to the first identifier and the delivery timestamp.

[0096] Among them, the second time zipper table includes multiple second time zipper records, each of which is used to record the mapping relationship between the object identification, object rank, rank ratio, start effective time and end effective time of an object associated with the task type.

[0097] In an embodiment of the present disclosure, when it is determined that there is no first target time zipper record in the first time zipper table based on the first identifier, the second identifier and the delivery timestamp, the second time zipper table associated with the task type of the task to be processed can be further queried based on the first identifier and the delivery timestamp.

[0098] Step S205: determining a second target time zipper record from the plurality of second time zipper records.

[0099] The second target time zipper record includes a first identifier, and the delivery timestamp is located between the start effective time and the end effective time in the second target time zipper record.

[0100] In an embodiment of the present disclosure, a second target time zipper record can be determined from multiple second time zipper records in a second time zipper table based on the first identifier and the delivery timestamp; wherein the second target time zipper record contains the first identifier of the same object mentioned above, and the delivery timestamp is located between the start effective time and the end effective time in the second target time zipper record.

[0101] Step S206: Use the job grade ratio in the second target time zipper record as the target resource occupancy ratio of the same object to the service business entity at the delivery timestamp.

[0102] In the disclosed embodiment, the job grade ratio in the second target time zipper record may be directly used as the target resource occupancy ratio of the same object to the business entity it serves at the delivery timestamp.

[0103] Step S207, based on the target resource occupancy ratio and the total resource occupancy, determine the resource occupancy value of the same object for the service business entity at the delivery timestamp, and generate the execution result of the task to be processed according to the resource occupancy value of each object for the corresponding service business entity.

[0104] For the explanation of step S207, reference may be made to the relevant description in any embodiment of the present disclosure, and no further details will be given here.

[0105] In any embodiment of the present disclosure, by automatically executing pending tasks, the execution efficiency of pending tasks can be improved, the degree of manual participation can be reduced, and the accuracy of the execution of pending tasks can be improved. Sending the accurate execution results corresponding to the pending tasks to the designated account can ensure the timeliness and timeliness of the execution results synchronization to the relevant personnel, so that the relevant personnel bound to the designated account can view the execution results of the pending tasks in a timely manner through the terminal devices they use, and analyze the execution results of the pending tasks, so as to optimize resource allocation and cost structure based on the analysis results.

[0106] In any embodiment of the present disclosure, the accurate execution results corresponding to the tasks to be processed can also be persistently stored so that relevant personnel of the target enterprise can conduct data queries in a timely and effective manner, thereby optimizing resource allocation and cost structure based on the query results.

[0107] In any embodiment of the present disclosure, the execution results of the pending tasks can also be sent to a designated account, and the execution results of the pending tasks can be persistently stored, so that relevant personnel can analyze the execution results of the pending tasks in a timely manner, and optimize resource allocation and cost structure based on the query results.

[0108] In summary, different methods can be used to provide the execution results of pending tasks to relevant personnel for data analysis, which can improve the flexibility and applicability of the method and meet personalized application needs in different scenarios.

[0109] The task execution method of the disclosed embodiment preferentially queries the first time zipper table containing both object information and business entity information according to the target delivery behavior record. When there is a first target time zipper record matching the first identifier, the second identifier and the delivery timestamp in the first time zipper table, the resource occupancy ratio in the first target time zipper record is directly used as the target resource occupancy ratio. Since the target resource occupancy ratio is calculated based on the rank ratio of the same object and the entity ratio (such as product ratio and project ratio) of the business entity served by the same object during the effective period of the rank ratio, the rationality and accuracy of the determination of the target resource occupancy ratio can be improved, thereby improving the accuracy of the resource occupancy value calculation.

[0110] When there is no first target time zipper record in the first time zipper table, further query the second target time zipper record that matches the first identifier and delivery timestamp from the second time zipper table containing the object information, and use the job grade ratio in the second target time zipper record as the target resource occupancy ratio, which can improve the effectiveness of obtaining the target resource occupancy ratio, and then improve the effectiveness of calculating the resource occupancy value.

[0111] In order to clearly illustrate any of the above embodiments, the present disclosure also proposes a task execution method.

[0112] Figure 3 This is a flowchart of the task execution method provided in the third embodiment of the present disclosure.

[0113] like Figure 3 As shown, the first time zipper table can be obtained by following the steps below:

[0114] Step S301, obtain an object management information adjustment table associated with the task type of the task to be processed; wherein the object management information adjustment table is used to record the object management information of at least one target object, and the target object refers to an object in which at least one of the object rank, the effective timestamp of the object rank and the rank ratio has changed.

[0115] In an embodiment of the present disclosure, an object management information adjustment table associated with a task type of a task to be processed may be obtained or loaded, wherein the object management information adjustment table includes a plurality of object management information records (hereinafter referred to as first object management information records), wherein each first object management information record is used to record object management information of a target object associated with a target enterprise and a task type, wherein the first object management information record may be used to record an object identifier, an object rank, an effective timestamp of an object rank (or an effective timestamp of a rank ratio), and a mapping relationship between rank ratios of a target object.

[0116] For example, taking the task type as a sales incentive task as an exemplary description, the object management information adjustment table may be the sales management information adjustment table adjust shown in Table 2.

[0117] Step S302: based on the object management information adjustment table, update the first object management information table associated with the task type to obtain a second object management information table; wherein the first object management information table is used to record the object management information of the object associated with the task type.

[0118] In an embodiment of the present disclosure, the first object management information table may include multiple object management information records (hereinafter referred to as second object management information records), wherein each second object management information record is used to record the object identifier, object rank, effective timestamp of the object rank (or effective timestamp of the rank ratio), and mapping relationship between rank ratios of any object associated with the target enterprise and task type.

[0119] For example, taking the task type as a sales incentive task as an exemplary description, the first object management information table may be the sales table sale shown in Table 1.

[0120] In the embodiment of the present disclosure, a first object management information table associated with a task type may be acquired or loaded, and based on the object management information adjustment table, the first object management information table may be updated to obtain a second object management information table.

[0121] As an example, the priority of the first object management information table can be replaced based on the object management information adjustment table to generate the second object management information table. That is, the priority value algorithm can be used to preferentially use the first object management information record in the object management information adjustment table to adjust the second object management information record in the first object management information table.

[0122] For example, still taking the task type as a sales incentive task for exemplary explanation, the object management information adjustment table can be the sales management information adjustment table shown in Table 2, and the first object management information table can be the sales table sale shown in Table 1. For the first first object management information record in Table 2, the second object management information record (that is, the second second object management information record in Table 1) containing the object identifier (sales a) and the object rank (rank 2) can be found from Table 1 according to the object identifier (sales a) and the object rank (rank 2) in the first first object management information record. Afterwards, the effective timestamp (2022-06-01) in the first first object management information record in Table 2 can be preferentially used to update the effective timestamp (2022-09-01) in the second second object management information record in Table 1.

[0123] Step S303: Generate a first time zipper table according to the second object management information table and the business entity table; wherein the business entity table is used to record entity management information of multiple business entities.

[0124] The business entity table may include multiple business entity management records, each of which may be used to record the mapping relationship between the entity ID, entity ratio, start effective time and end effective time of a business entity associated with the target enterprise.

[0125] For example, taking the task type as a sales incentive task as an example, the business entity table may be the product table product shown in Table 3.

[0126] In the disclosed embodiment, a business entity table associated with the target enterprise may be acquired or loaded, and the second object management information table and the business entity table may be integrated to generate a first time zipper table associated with the business type.

[0127] Among them, the first time zipper table contains multiple first time zipper records, each first time zipper record is used to record the object identifier of an object associated with the target enterprise and task type, the entity identifier of the business entity, the resource occupancy ratio, and the mapping relationship between the start effective time and the end effective time of the resource occupancy ratio.

[0128] The task execution method of the disclosed embodiment integrates the object management information adjustment table, the object management information table and the business entity table associated with the task type to generate a first-time zipper table, which can realize the comprehensive object rank ratio and the entity ratio of the business entity to calculate the resource occupancy ratio of each record in the first-time zipper table, thereby improving the rationality and accuracy of the resource occupancy ratio calculation, and can also realize the comprehensive object rank effective timestamp and the start effective time and end effective time of the entity ratio to calculate the start effective time and end effective time of the resource occupancy ratio of each record in the first-time zipper table, thereby improving the accuracy and reliability of determining the effective period of the resource occupancy ratio.

[0129] In order to clearly explain how to generate a first time zipper table according to the second object management information table and the business entity table in any embodiment of the present disclosure, the present disclosure also proposes a task execution method.

[0130] Figure 4 This is a flowchart of the task execution method provided in the fourth embodiment of the present disclosure.

[0131] like Figure 4 As shown, the first time zipper table can be obtained by following the steps below:

[0132] Step S401: obtaining an object management information adjustment table associated with a task type of a task to be processed.

[0133] The object management information adjustment table is used to record the object management information of at least one target object, where the target object refers to an object in which at least one of the object rank, the effective timestamp of the object rank and the rank ratio has changed.

[0134] Step S402: based on the object management information adjustment table, update the first object management information table associated with the task type to obtain a second object management information table.

[0135] The first object management information table is used to record the object management information of the object associated with the target enterprise and the task type. Exemplarily, the first object management information table may include multiple object management information records (i.e., second object management information records), wherein each second object management information record is used to record the mapping relationship between the object identifier, object rank, rank ratio, and effective timestamp of the object rank of an object associated with the target enterprise and the task type.

[0136] The second object management information table is used to record updated object management information corresponding to an object associated with the target enterprise and the task type. Exemplarily, the second object management information table may include multiple object management information records (hereinafter referred to as third object management information records), wherein each third object management information record is used to record the mapping relationship between the object identifier, object rank, rank ratio, and effective timestamp of the object rank of an object associated with the target enterprise.

[0137] For explanations of steps S401 to S402, reference may be made to the relevant descriptions in any embodiment of the present disclosure, and will not be repeated here.

[0138] Step S403: Execute a time zipper algorithm on the second object management information table to obtain a second time zipper table.

[0139] Among them, the second time zipper table may include multiple second time zipper records, each second time zipper record is used to record the mapping relationship between the object identification, object rank, rank ratio, object rank start effective time and end effective time of an object associated with the target enterprise and task type.

[0140] It should be noted that since each record in the second object management information table only contains one timestamp, namely the effective timestamp of the object rank or rank ratio (i.e. the start effective time), but does not contain the end effective time of the object rank, it may not be possible to accurately match the delivery timestamps in each interaction behavior record in the target delivery table. In response to the above situation, in the present disclosure, a time zipper algorithm can be executed on the second object management information table to obtain a second time zipper table containing two timestamps.

[0141] In a first possible implementation of the embodiment of the present disclosure, the following steps A to F may be used to execute a time zipper algorithm on the second object management information table to obtain a second time zipper table:

[0142] Step A: determining a target object management information record containing the same object identifier from a plurality of third object management information records in the second object management information table;

[0143] Step B: sorting each target object management information record in descending order according to the corresponding effective time stamp to obtain a sorting sequence (hereinafter referred to as a first sorting sequence);

[0144] Step C: for i target object management information records in the first sorting sequence, use the effective time stamp in the i-th target object management information record as the effective start time corresponding to the object rank in the i-th target object management information record;

[0145] Step D: When i=1, the specified timestamp is used as the end effective time corresponding to the object rank in the i-th target object management information record;

[0146] The time difference between the specified timestamp and the effective start time corresponding to the object rank in the first target object management information record is greater than a set threshold. For example, the specified timestamp may be December 31, 2099.

[0147] Step E: when i is a positive integer greater than 1, the effective time stamp in the i-1th target object management information record is used as the end effective time of the object rank in the i-th target object management information record;

[0148] Step F: Generate a second time zipper record in the second time zipper table according to the object identifier, object rank and rank ratio in the i-th target object management information record, and the start effective time and end effective time corresponding to the object rank in the i-th target object management information record.

[0149] In a second possible implementation manner of the embodiment of the present disclosure, the following steps A' to F' may also be used to execute a time zipper algorithm on the second object management information table to obtain a second time zipper table:

[0150] Step A': determining a target object management information record containing the same object identifier from a plurality of third object management information records in the second object management information table;

[0151] Step B': sorting each target object management information record in ascending order according to the corresponding effective time stamp to obtain a sorting sequence (hereinafter referred to as a second sorting sequence);

[0152] Step C': for i target object management information records in the second sorting sequence, use the effective time stamp in the i-th target object management information record as the effective start time corresponding to the object rank in the i-th target object management information record;

[0153] Step D': when i=N, the specified timestamp is used as the end effective time corresponding to the object rank in the i-th target object management information record;

[0154] Wherein, N is the total number of target object management information records in the second sorting sequence, and N is a positive integer.

[0155] Step E': when i is a positive integer less than N, the effective time stamp in the (i+1)th target object management information record is used as the end effective time of the object rank in the (i)th target object management information record.

[0156] Step F': Generate a second time zipper record in the second time zipper table according to the object identifier, object rank and rank ratio in the i-th target object management information record, and the start effective time and end effective time corresponding to the object rank in the i-th target object management information record.

[0157] Therefore, it is possible to use the effective timestamp of the previous element in the sorting sequence as the end effective time of the next element by sorting in descending order, or to use the effective timestamp of the next element in the sorting sequence as the end effective time of the previous element by sorting in ascending order, so that two timestamps (i.e., the start effective time and the end effective time of the object's rank) can be effectively and reasonably generated for each element in the sorting sequence to obtain a second time zipper table, which can improve the effectiveness and rationality of the generation of the second time zipper table.

[0158] Step S404, obtaining the business entity table.

[0159] The business entity table includes multiple business entity management records, each of which is used to record the mapping relationship between the entity ID, entity ratio, start effective time and end effective time of a business entity associated with the target enterprise.

[0160] For example, taking the task type as a sales incentive task as an example, the business entity table may be the product table product shown in Table 3.

[0161] In the embodiment of the present disclosure, a business entity table associated with the target enterprise may be acquired or loaded.

[0162] Step S405: merge the second time zipper table and the business entity table to obtain the first time zipper table.

[0163] Among them, the first time zipper table can contain multiple first time zipper records, each first time zipper record is used to record the object identifier of an object associated with the target enterprise, the entity identifier of the business entity, the resource occupancy ratio, and the mapping relationship between the start effective time and the end effective time of the resource occupancy ratio.

[0164] In the embodiment of the present disclosure, the second time zipper table and the business entity table may be merged to generate a first time zipper table that merges the object information and the business entity information.

[0165] The task execution method of the disclosed embodiment executes a time zipper algorithm on the second object management information table to obtain a second time zipper table, and merges the second time zipper table with the business entity table associated with the target enterprise to obtain a first time zipper table. This allows each record in the generated first time zipper table to simultaneously contain object information, business entity information and two timestamps associated with the target enterprise, thereby allowing each record in the target delivery table to accurately match the records in the first time zipper table, thereby improving the effectiveness, accuracy and rationality of the resource occupancy value calculation for each record in the target delivery table.

[0166] In order to clearly explain how to merge the second time zipper table and the business entity table to obtain the first time zipper table in any embodiment of the present disclosure, the present disclosure also proposes a task execution method.

[0167] Figure 5 This is a flowchart of the task execution method provided in Embodiment 5 of the present disclosure.

[0168] like Figure 5 As shown, the first time zipper table can be obtained by following the steps below:

[0169] Step S501: obtaining an object management information adjustment table associated with a task type of a task to be processed.

[0170] Among them, the object management information adjustment table is used to record the object management information of at least one target object associated with the target enterprise and task type. The target object refers to an object in which at least one of the object rank, the effective timestamp of the object rank and the rank ratio has changed.

[0171] Step S502: based on the object management information adjustment table, update the first object management information table associated with the task type to obtain a second object management information table.

[0172] The first object management information table is used to record the object management information of the object associated with the target enterprise and the task type. Exemplarily, the first object management information table may include multiple object management information records (i.e., second object management information records), wherein each second object management information record is used to record the mapping relationship between the object identifier, object rank, rank ratio, and effective timestamp of the object rank of an object associated with the target enterprise and the task type.

[0173] The second object management information table is used to record updated object management information corresponding to the object associated with the target enterprise and task type. Exemplarily, the second object management information table may include multiple object management information records (hereinafter referred to as third object management information records), wherein each third object management information record is used to record the mapping relationship between the object identifier, object rank, rank ratio, and effective timestamp of the object rank of an object associated with the target enterprise and task type.

[0174] Step S503: Execute a time zipper algorithm on the second object management information table to obtain a second time zipper table.

[0175] Step S504, obtaining a business entity table.

[0176] The business entity table contains multiple business entity management records, each of which is used to record the mapping relationship between the entity ID, entity ratio, start effective time and end effective time of a business entity associated with the target enterprise.

[0177] The explanation of steps S501 to S504 can be found in the relevant description in any embodiment of the present disclosure, and will not be repeated here.

[0178] Step S505 , determining a first effective period according to the effective start time and effective end time of the object rank in any second time zipper record in the second time zipper table.

[0179] In the embodiment of the present disclosure, for any second time zipper record in the second time zipper table, the first effective period can be determined based on the effective start time and effective end time of the object rank in the second time zipper record, that is, the start time of the first effective period is equal to the effective start time of the object rank in the second time zipper record, and the end time of the first effective period is equal to the effective end time of the object rank in the second time zipper record.

[0180] Step S506: Determine a second effective period according to the effective start time and effective end time of the entity ratio in any business entity management record in the business entity table.

[0181] In an embodiment of the present disclosure, for any business entity management record in the business entity table, the second effective period can be determined based on the effective start time and effective end time of the entity ratio in the business entity management record, that is, the start time of the second effective period is equal to the effective start time of the entity ratio in the business entity management record, and the end time of the second effective period is equal to the effective end time of the entity ratio in the business entity management record.

[0182] Step S507: determine whether there is an intersection between the first effective time period and the second effective time period.

[0183] In the embodiment of the present disclosure, it can be determined whether there is an intersection between the first effective time period and the second effective time period. If so, it indicates that the second time zipper record in step S505 and the business entity management record in step S506 can be merged. At this time, step S508 can be executed. If not, it indicates that the second time zipper record in step S505 and the business entity management record in step S506 cannot be merged. At this time, step S508 does not need to be executed.

[0184] Step S508: If it exists, merge any second time zipper record and any business entity management record to obtain a first time zipper record, and enter it into the first time zipper table.

[0185] In an embodiment of the present disclosure, when there is an intersection between the first effective period and the second effective period, the second time zipper record in step S505 and the business entity management record in step S506 can be merged to obtain a first time zipper record, and the first time zipper record can be entered into the first time zipper table.

[0186] In any embodiment of the present disclosure, the resource occupancy ratio contained in the first time zipper record to be generated can be determined according to the product of the job grade ratio in the second time zipper record in the above step S505 and the entity ratio in the business entity management record in step S506, and the start time of the above intersection is used as the start effective time of the resource occupancy ratio in the first time zipper record to be generated, and the end time of the intersection is used as the end effective time of the resource occupancy ratio in the first time zipper record to be generated, so that a first time zipper record can be generated according to the object identifier in the above second time zipper record, the entity identifier in the above business entity management record, the resource occupancy ratio contained in the first time zipper record to be generated, and the start effective time and the end effective time of the resource occupancy ratio.

[0187] Therefore, the second time zipper record and the business entity management record whose effective time periods overlap are merged, wherein the fusion method is: retaining the object identifier in the second time zipper record and the entity identifier in the business entity management record, and taking the product of the job grade ratio in the second time zipper record and the entity ratio in the business entity management record as the resource occupancy ratio in the first time zipper record, and taking the overlapping period between the first effective time period corresponding to the second time zipper record and the second effective time period corresponding to the business entity management record as the effective time period of the resource occupancy ratio, which can improve the accuracy and rationality of the merged first time zipper record.

[0188] The task execution method of the disclosed embodiment only merges the second time zipper records and business entity management records with overlapping effective periods, which can improve the rationality of the generation of each first time zipper record, and further improve the rationality of the generation of the first time zipper table.

[0189] In any one of the embodiments of the present disclosure, the present disclosure proposes a timestamp-oriented comprehensive time processing method and a multi-dimensional time zipper matching algorithm, which can realize timestamp data processing and multi-dimensional timestamp matching in the scenario of massive business data, reduce the processing time of business data records from tens of days to seconds, and realize accurate and rapid output and delivery of business data, thereby optimizing resource allocation.

[0190] As an example, take a product sales scenario, that is, the task type of the task to be processed is a sales incentive task. The object can be a salesperson, the business entity can be a product, the resource occupancy ratio can be an incentive ratio, the total resource occupancy can be a delivery amount or a sales amount, and the resource occupancy value can be an incentive amount. At this time, the object management information adjustment table can be the sales management information adjustment table adjust shown in Table 2, the first object management information table can be the sales table sale shown in Table 1, the business entity table can be the product table product shown in Table 3, the target delivery table can be the sales delivery table delivery shown in Table 4, the second object management information table can be marked as sale_v2, the second time zipper table can be marked as sale_v3, and the first time zipper table can be marked as sale_v4. The implementation principles of each embodiment of the present disclosure can be as follows: Figure 6 As shown, it mainly includes the following steps:

[0191] Step S1, based on the sales management information adjustment table adjust, complete the priority replacement of the sales table sale and generate sale_v2.

[0192] That is, when adjust has relevant timestamp & job level ratio, the value in the sales management information adjustment table adjust is used first.

[0193] Step S2, since each row of records in sale_v2 has only one timestamp, that is, the start effective time of a certain job level, but no end effective time, it may not be able to match the delivery timestamp in the sales delivery table delivery. Therefore, the time zipper algorithm can be executed based on the adjusted sales table sale_v2 to generate a second time zipper table sale_v3 containing two timestamps.

[0194] Step S3, based on sale_v3 and the product table product, generate a time zipper table of the fused product information version, which is recorded as the first time zipper table sale_v4 in this disclosure.

[0195] In order to prevent repeated matching, the effective period of sale_v4 can be closed on the left and open on the right, that is, the effective period of each first-time zipper record in sale_v4 is [start effective time, end effective time).

[0196] Step S4, for the sales interaction behavior records in the sales delivery table delivery, based on the time + product dual-dimensional restriction conditions, match the first time zipper table sale_v4 to generate the sales performance calculation result result (used to indicate the salesperson's incentive amount for the product).

[0197] Step S5, for the sales interaction behavior records in the sales delivery table delivery, based on the dual-dimensional restriction conditions of time + product, match the first time zipper table sale_v4. If the time zipper record in sale_v4 cannot be matched, match the second time zipper table sale_v3 to generate the sales performance calculation result result_v2.

[0198] Step S6, merge result and result_v2 to obtain the full sales performance calculation result.

[0199] In summary, the technical solution provided by the present disclosure has at least the following advantages over the prior art:

[0200] 1) Adapt to dynamic adjustment: Support repeated adjustment of timestamps to meet the operational management needs of enterprises and generate them dynamically at any time;

[0201] 2) Lightweight algorithm architecture: The calculation process is simple. Using a batch of SQL (Structured Query Language) statements, the full amount of sales performance calculation results can be generated at one time in an ETL (Extract-Transform-Load, which is used to describe the process of extracting, transforming, and loading data from the source to the destination) data processing process;

[0202] 3) Flexible multi-dimensional matching: supports high-priority matching strategies for product dimensions, and product data can also be repeatedly revised and changed;

[0203] 4) Performance advantage: Massive level: tens of millions or hundreds of millions of rows of data, unified batch zipper data processing and resource usage value (such as incentive amount) calculation can be performed in seconds.

[0204] With the above Figures 1 to 6 Corresponding to the task execution method provided in the embodiment, the present disclosure also provides a task execution device. Figures 1 to 6 The task execution method provided in the embodiment corresponds to the task execution method, so the implementation method of the task execution method is also applicable to the task execution device provided in the embodiment of the present disclosure, and will not be described in detail in the embodiment of the present disclosure.

[0205] Figure 7 This is a structural diagram of the task execution device provided in Example 6 of the present disclosure.

[0206] like Figure 7 As shown, the task execution device 700 may include: an execution module 710 , a query module 720 , a determination module 730 and a first generation module 740 .

[0207] The execution module 710 is used to execute the pending task to query the target delivery behavior record corresponding to the same object associated with the task type of the pending task from the target delivery table; wherein the target delivery behavior record includes the first identifier of the same object, the second identifier of the business entity served by the same object, the delivery timestamp and the total amount of resource occupancy;

[0208] The query module 720 is used to query the first time zipper table associated with the task type according to the first identifier, the second identifier and the delivery timestamp, so as to obtain the target resource occupation ratio of the same object to the service business entity under the delivery timestamp; wherein the first time zipper table is used to record the resource occupation ratios of multiple objects to different business entities within at least one effective period;

[0209] A determination module 730, configured to determine a resource occupation value of a service entity served by the same object at a delivery timestamp based on the target resource occupation ratio and the total resource occupation;

[0210] The first generating module 740 is used to generate the execution result of the task to be processed according to the resource occupation value of the corresponding business entity served by each object.

[0211] In a possible implementation of the embodiment of the present disclosure, the first time zipper table contains multiple first time zipper records, and the first time zipper record is used to record the object identifier of the object associated with the task type, the entity identifier of the business entity, the resource occupancy ratio, and the mapping relationship between the start effective time and the end effective time of the resource occupancy ratio; the query module 720 is used to: determine whether there is a first target time zipper record in the multiple first time zipper records; wherein the first target time zipper record contains a first identifier and a second identifier, and the delivery timestamp is between the start effective time and the end effective time in the first target time zipper record; if it exists, the resource occupancy ratio in the first target time zipper record is used as the target resource occupancy ratio of the same object for the business entity served at the delivery timestamp.

[0212] In a possible implementation of the embodiment of the present disclosure, the query module 720 is also used to: if it does not exist, query the second time zipper table associated with the task type based on the first identifier and the delivery timestamp; wherein the second time zipper table includes multiple second time zipper records, and the second time zipper record is used to record the mapping relationship between the object identifier, object rank, rank ratio, and the start effective time and end effective time of the object associated with the task type; determine the second target time zipper record from the multiple second time zipper records; wherein the second target time zipper record contains the first identifier, and the delivery timestamp is between the start effective time and the end effective time in the second target time zipper record; use the rank ratio in the second target time zipper record as the target resource occupancy ratio of the same object to the service business entity at the delivery timestamp.

[0213] In a possible implementation of the embodiment of the present disclosure, the first time zipper table is obtained by using the following modules:

[0214] An acquisition module, used to acquire an object management information adjustment table associated with a task type; wherein the object management information adjustment table is used to record object management information of at least one target object, where the target object refers to an object whose rank, effective timestamp of the object rank, and rank ratio have changed;

[0215] An updating module, configured to update a first object management information table associated with a task type based on the object management information adjustment table to obtain a second object management information table; wherein the first object management information table is used to record object management information of objects associated with the task type;

[0216] The second generating module is used to generate a first time zipper table according to the second object management information table and the business entity table; wherein the business entity table is used to record entity management information of multiple business entities.

[0217] In a possible implementation of the embodiment of the present disclosure, the second generation module is used to: execute a time zipper algorithm on the second object management information table to obtain a second time zipper table; wherein the second time zipper table includes multiple second time zipper records, and the second time zipper record is used to record the mapping relationship between the object identification, object rank, rank ratio, and the start effective time and end effective time of the object associated with the task type; obtain a business entity table; wherein the business entity table contains multiple business entity management records, and the business entity management records the mapping relationship between the entity identification, entity ratio, and the start effective time and end effective time of the entity ratio of the business entity; and merge the second time zipper table and the business entity table to obtain the first time zipper table.

[0218] In a possible implementation of the embodiment of the present disclosure, the second object management information table includes multiple object management information records, and the object management information records are used to record the mapping relationship between the object identifier, object rank, rank ratio and effective timestamp of the object rank associated with the task type; the second generation module is used to: determine the target object management information record containing the same object identifier from the multiple object management information records; sort the target object management information records in descending order according to the corresponding effective timestamp to obtain a sorted sequence; for i target object management information records in the sorted sequence, use the effective timestamp in the i-th target object management information record as the i-th target object management the start effective time corresponding to the object rank in the information record; when i=1, the specified timestamp is used as the end effective time corresponding to the object rank in the i-th target object management information record; when i is a positive integer greater than 1, the effective timestamp in the i-1-th target object management information record is used as the end effective time of the object rank in the i-th target object management information record; according to the object identifier, object rank and rank ratio in the i-th target object management information record, and according to the start effective time and end effective time corresponding to the object rank in the i-th target object management information record, a second time zipper record in the second time zipper table is generated.

[0219] In a possible implementation of the embodiment of the present disclosure, the second generation module is used to: determine the first effective period according to the start effective time and end effective time of the object's rank in any second time zipper record in the second time zipper table; determine the second effective period according to the start effective time and end effective time of the entity ratio in any business entity management record in the business entity table; determine whether there is an intersection between the first effective period and the second effective period; if so, merge any second time zipper record and any business entity management record to obtain a first time zipper record, and enter it into the first time zipper table.

[0220] In a possible implementation of the embodiment of the present disclosure, the second generation module is used to: determine the resource occupancy ratio contained in the first time zipper record to be generated according to the product of the job grade ratio in any second time zipper record and the entity ratio in any business entity management record; determine the start effective time and end effective time of the contained resource occupancy ratio according to the intersection; generate the first time zipper record according to the object identifier in any second time zipper record, the entity identifier in any business entity management record, the contained resource occupancy ratio, and the start effective time and end effective time of the contained resource occupancy ratio.

[0221] In a possible implementation of the embodiment of the present disclosure, the task execution device 700 further includes:

[0222] The sending module is used to send the execution results of the pending tasks to the specified account;

[0223] and / or,

[0224] The storage module is used to persistently store the execution results of the tasks to be processed.

[0225] The task execution device of the disclosed embodiment maintains a corresponding first-time zipper table separately for each task type to record the resource occupancy ratio of objects of different job levels to different business entities in different effective periods. Therefore, in the disclosed embodiment, the first-time zipper table associated with the task type of the task to be processed can be directly queried to obtain the target resource occupancy ratio of any object to the business entity it serves at a certain delivery timestamp, and the resource occupancy value of the object is calculated based on the target resource occupancy ratio, without the need to query multiple data tables to calculate in real time the target resource occupancy ratio of the object to the business entity it serves at the above-mentioned delivery timestamp. This can improve the query efficiency of the resource occupancy ratio, thereby improving the execution efficiency of the tasks to be processed, reducing the waiting time of users, and improving the user experience.

[0226] In order to implement the above embodiments, the present disclosure also provides an electronic device, which may include at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute the task execution method proposed in any of the above embodiments of the present disclosure.

[0227] In order to implement the above embodiments, the present disclosure further provides a non-transitory computer-readable storage medium storing computer instructions, wherein the computer instructions are used to enable a computer to execute the task execution method proposed in any of the above embodiments of the present disclosure.

[0228] In order to implement the above embodiments, the present disclosure further provides a computer program product, which includes a computer program. When the computer program is executed by a processor, it implements the task execution method proposed in any of the above embodiments of the present disclosure.

[0229] According to an embodiment of the present disclosure, the present disclosure also provides an electronic device, a readable storage medium and a computer program product.

[0230] Figure 8 A schematic block diagram of an example electronic device that can be used to implement embodiments of the present disclosure is shown.

[0231] Among them, the electronic device may include the server and the client in the above-mentioned embodiment. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workbenches, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device can also represent various forms of mobile devices, such as personal digital processing, cellular phones, smart phones, wearable devices and other similar computing devices. The components shown herein, their connections and relationships, and their functions are only examples and are not intended to limit the implementation of the present disclosure described and / or required herein.

[0232] like Figure 8 As shown, the electronic device 800 includes a computing unit 801, which can perform various appropriate actions and processes according to a computer program stored in a ROM (Read-Only Memory) 802 or a computer program loaded from a storage unit 807 to a RAM (Random Access Memory) 803. In the RAM 803, various programs and data required for the operation of the device 800 can also be stored. The computing unit 801, the ROM 802, and the RAM 803 are connected to each other via a bus 804. An I / O (Input / Output) interface 805 is also connected to the bus 804.

[0233] A number of components in the device 800 are connected to the I / O interface 805, including: an input unit 806, such as a keyboard, a mouse, etc.; an output unit 807, such as various types of displays, speakers, etc.; a storage unit 808, such as a disk, an optical disk, etc.; and a communication unit 809, such as a network card, a modem, a wireless communication transceiver, etc. The communication unit 809 allows the device 800 to exchange information / data with other devices through a computer network such as the Internet and / or various telecommunication networks.

[0234] The computing unit 801 may be a variety of general and / or special processing components with processing and computing capabilities. Some examples of the computing unit 801 include, but are not limited to, CPU (Central Processing Unit), GPU (Graphic Processing Units), various dedicated AI (Artificial Intelligence) computing chips, various computing units running machine learning model algorithms, DSP (Digital Signal Processor), and any appropriate processor, controller, microcontroller, etc. The computing unit 801 performs the various methods and processes described above, such as the above-mentioned task execution method. For example, in some embodiments, the above-mentioned task execution method may be implemented as a computer software program, which is tangibly contained in a machine-readable medium, such as a storage unit 808. In some embodiments, part or all of the computer program may be loaded and / or installed on the device 800 via the ROM 802 and / or the communication unit 809. When the computer program is loaded into the RAM 803 and executed by the computing unit 801, one or more steps of the task execution method described above may be executed. Alternatively, in other embodiments, the computing unit 801 may be configured to perform the above-mentioned task execution method in any other appropriate manner (for example, by means of firmware).

[0235] Various embodiments of the systems and techniques described above herein may be implemented in digital electronic circuit systems, integrated circuit systems, FPGAs (Field Programmable Gate Arrays), ASICs (Application-Specific Integrated Circuits), ASSPs (Application Specific Standard Products), SOCs (System On Chips), CPLDs (Complex Programmable Logic Devices), computer hardware, firmware, software, and / or combinations thereof. These various embodiments may include: being implemented in one or more computer programs that may be executed and / or interpreted on a programmable system including at least one programmable processor that may be a dedicated or general-purpose programmable processor that may receive data and instructions from a storage system, at least one input device, and at least one output device, and transmit data and instructions to the storage system, the at least one input device, and the at least one output device.

[0236] The program code for implementing the method of the present disclosure may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general-purpose computer, a special-purpose computer, or other programmable data processing device, so that the program code, when executed by the processor or controller, enables the functions / operations specified in the flow chart and / or block diagram to be implemented. The program code may be executed entirely on the machine, partially on the machine, partially on the machine and partially on a remote machine as a stand-alone software package, or entirely on a remote machine or server.

[0237] In the context of the present disclosure, a machine-readable medium may be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, device, or equipment. A machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or device, or any suitable combination of the foregoing. More specific examples of machine-readable storage media may include electrical connections based on one or more lines, portable computer disks, hard disks, RAM, ROM, EPROM (Electrically Programmable Read-Only-Memory) or flash memory, optical fiber, CD-ROM (Compact Disc Read-Only Memory), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

[0238] To provide interaction with a user, the systems and techniques described herein can be implemented on a computer having: a display device (e.g., a CRT (Cathode-Ray Tube) or LCD (Liquid Crystal Display) monitor) for displaying information to the user; and a keyboard and pointing device (e.g., a mouse or trackball) through which the user can provide input to the computer. Other types of devices can also be used to provide interaction with the user; for example, the feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including acoustic input, voice input, or tactile input).

[0239] The systems and techniques described herein may be implemented in a computing system that includes backend components (e.g., as a data server), or a computing system that includes middleware components (e.g., an application server), or a computing system that includes frontend components (e.g., a user computer with a graphical user interface or a web browser through which a user can interact with implementations of the systems and techniques described herein), or a computing system that includes any combination of such backend components, middleware components, or frontend components. The components of the system may be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: LAN (Local Area Network), WAN (Wide Area Network), the Internet, and blockchain networks.

[0240] A computer system may include a client and a server. The client and the server are generally remote from each other and usually interact through a communication network. The relationship between the client and the server is generated by computer programs running on the corresponding computers and having a client-server relationship with each other. The server may be a cloud server, also known as a cloud computing server or a cloud host, which is a host product in the cloud computing service system to solve the defects of difficult management and weak business scalability in traditional physical hosts and VPS services (Virtual Private Server). The server may also be a server of a distributed system, or a server combined with a blockchain.

[0241] It should be noted that artificial intelligence is a discipline that studies how computers can simulate certain human thought processes and intelligent behaviors (such as learning, reasoning, thinking, planning, etc.), and includes both hardware-level and software-level technologies. Artificial intelligence hardware technologies generally include technologies such as sensors, dedicated artificial intelligence chips, cloud computing, distributed storage, and big data processing; artificial intelligence software technologies mainly include computer vision technology, speech recognition technology, natural language processing technology, as well as machine learning / deep learning, big data processing technology, knowledge graph technology, and other major directions.

[0242] According to the technical solution of the embodiment of the present disclosure, a corresponding first-time zipper table is maintained separately for each task type to record the resource occupancy ratios of objects of different job levels for different business entities in different effective periods. Therefore, in the present disclosure, the first-time zipper table associated with the task type of the task to be processed can be directly queried to obtain the target resource occupancy ratio of any object to the business entity it serves at a certain delivery timestamp, and the resource occupancy value of the object can be calculated based on the target resource occupancy ratio, without the need to query multiple data tables to calculate in real time the target resource occupancy ratio of the object to the business entity it serves at the above-mentioned delivery timestamp. This can improve the query efficiency of the resource occupancy ratio, thereby improving the execution efficiency of the tasks to be processed, reducing the waiting time of users, and improving the user experience.

[0243] It should be understood that the various forms of processes shown above can be used to reorder, add or delete steps. For example, the steps recorded in this disclosure can be executed in parallel, sequentially or in different orders, as long as the desired results of the technical solutions disclosed in this disclosure can be achieved, and this document does not limit this.

[0244] The above specific implementations do not constitute a limitation on the protection scope of the present disclosure. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions can be made according to design requirements and other factors. Any modification, equivalent substitution and improvement made within the spirit and principle of the present disclosure shall be included in the protection scope of the present disclosure.

Claims

1. A task execution method, include: Execute the pending task to query the target delivery behavior record corresponding to the same object associated with the task type of the pending task from the target delivery table; wherein the target delivery behavior record includes the first identifier of the same object, the second identifier of the business entity served by the same object, the delivery timestamp and the total amount of resource occupancy; According to the first identifier, the second identifier and the delivery timestamp, query the first time zipper table associated with the task type to obtain the target resource occupation ratio of the same object to the business entity of the service at the delivery timestamp; wherein the first time zipper table is used to record the resource occupation ratios of multiple objects to different business entities within at least one effective period; Determine, based on the target resource occupation ratio and the total resource occupation, a resource occupation value of the same object for the service entity at the delivery timestamp; The execution result of the task to be processed is generated according to the resource occupation value of the corresponding business entity served by each object.

2. The method according to claim 1, in, The first time zipper table includes a plurality of first time zipper records, and the first time zipper record is used to record the object identifier of the object associated with the task type, the entity identifier of the business entity, the resource occupancy ratio, and the mapping relationship between the start effective time and the end effective time of the resource occupancy ratio; The querying a first time zipper table associated with the task type according to the first identifier, the second identifier, and the delivery timestamp includes: Determine whether there is a first target time zipper record in the multiple first time zipper records; wherein the first target time zipper record contains the first identifier and the second identifier, and the delivery timestamp is between the start effective time and the end effective time in the first target time zipper record; If so, the resource occupancy ratio in the first target time zip record is used as the target resource occupancy ratio of the same object to the business entity of the service at the delivery timestamp.

3. The method according to claim 2, in, The querying of a first time zipper table associated with the task type according to the first identifier, the second identifier and the delivery timestamp further includes: If it does not exist, query the second time zipper table associated with the task type according to the first identifier and the delivery timestamp; wherein the second time zipper table includes multiple second time zipper records, and the second time zipper record is used to record the mapping relationship between the object identifier, object rank, rank ratio, object rank start effective time and end effective time of the object associated with the task type; Determine a second target time zipper record from the plurality of second time zipper records; wherein the second target time zipper record contains the first identifier, and the delivery timestamp is between the start effective time and the end effective time in the second target time zipper record; The job grade ratio in the second target time zipper record is used as the target resource occupancy ratio of the same object to the business entity of the service at the delivery timestamp.

4. The method according to claim 1, in, The first time zipper table is obtained by using the following steps: Obtaining an object management information adjustment table associated with the task type; wherein the object management information adjustment table is used to record object management information of at least one target object, wherein the target object refers to an object in which at least one of the object rank, the effective timestamp of the object rank, and the rank ratio has changed; Based on the object management information adjustment table, the first object management information table associated with the task type is updated to obtain a second object management information table; wherein the first object management information table is used to record the object management information of the object associated with the task type; The first time zipper table is generated according to the second object management information table and the business entity table; wherein the business entity table is used to record entity management information of multiple business entities.

5. The method according to claim 4, in, The step of generating the first time zipper table according to the second object management information table and the business entity table includes: A time zipper algorithm is executed on the second object management information table to obtain a second time zipper table; wherein the second time zipper table includes a plurality of second time zipper records, and the second time zipper record is used to record the mapping relationship between the object identifier, the object rank, the rank ratio, the start effective time and the end effective time of the object associated with the task type; Acquire the business entity table; wherein the business entity table contains a plurality of business entity management records, and the business entity management records are used to record the mapping relationship between the entity identifier, entity ratio, entity ratio start effective time and end effective time of the business entity; The second time zipper table and the business entity table are merged to obtain the first time zipper table.

6. The method according to claim 5, in, The second object management information table includes a plurality of object management information records, and the object management information records are used to record the mapping relationship between the object identifier, the object rank, the rank ratio and the effective timestamp of the object rank associated with the task type; The performing a time zipper algorithm on the second object management information table to obtain a second time zipper table includes: Determining, from the plurality of object management information records, a target object management information record containing the same object identifier; Sorting each of the target object management information records in descending order according to the corresponding effective timestamps to obtain a sorted sequence; For i target object management information records in the sorting sequence, the effective time stamp in the i-th target object management information record is used as the effective start time corresponding to the object rank in the i-th target object management information record; In the case of i=1, the specified timestamp is used as the end effective time corresponding to the object rank in the i-th target object management information record; When i is a positive integer greater than 1, the effective time stamp in the i-1th target object management information record is used as the end effective time of the object rank in the i-th target object management information record; A second time zipper record in the second time zipper table is generated according to the object identifier, object rank and rank ratio in the i-th target object management information record, and the start effective time and end effective time corresponding to the object rank in the i-th target object management information record.

7. The method according to claim 5, in, The step of fusing the second time zipper table with the business entity table to obtain the first time zipper table includes: Determine the first effective period according to the effective start time and effective end time of the object's rank in any second time zipper record in the second time zipper table; Determine a second effective period according to the effective start time and effective end time of the entity ratio in any business entity management record in the business entity table; Determine whether there is an intersection between the first effective time period and the second effective time period; If it exists, any second time zipper record and any business entity management record are merged to obtain a first time zipper record, and the record is entered into the first time zipper table.

8. The method according to claim 7, in, The step of fusing any second time zipper record with any business entity management record to obtain a first time zipper record includes: Determining the resource occupancy ratio contained in the first time zipper record to be generated according to the product of the job level ratio in any second time zipper record and the entity ratio in any business entity management record; Determine, according to the intersection, the effective start time and effective end time of the resource occupancy ratio included; The first time zipper record is generated according to the object identifier in any of the second time zipper records, the entity identifier in any of the business entity management records, the resource occupancy ratio contained, the start effective time and the end effective time of the resource occupancy ratio contained.

9. The method according to any one of claims 1 to 8, in, The method further comprises: Sending the execution result of the pending task to a designated account; and / or, The execution results of the tasks to be processed are persistently stored.

10. A task execution device, include: An execution module, used for executing the pending task, to query the target delivery behavior record corresponding to the same object associated with the task type of the pending task from the target delivery table; wherein the target delivery behavior record includes the first identifier of the same object, the second identifier of the business entity served by the same object, the delivery timestamp and the total amount of resource occupancy; A query module, used to query a first time zipper table associated with the task type according to the first identifier, the second identifier and the delivery timestamp, so as to obtain the target resource occupation ratio of the same object to the business entity of the service at the delivery timestamp; wherein the first time zipper table is used to record the resource occupation ratios of multiple objects to different business entities within at least one effective period; A determination module, configured to determine, based on the target resource occupation ratio and the total resource occupation, a resource occupation value of the same object for the service entity at the delivery timestamp; The first generating module is used to generate the execution result of the task to be processed according to the resource occupation value of the corresponding business entity served by each object.

11. The device according to claim 10, in, The first time zipper table includes a plurality of first time zipper records, and the first time zipper record is used to record the object identifier of the object associated with the task type, the entity identifier of the business entity, the resource occupancy ratio, and the mapping relationship between the start effective time and the end effective time of the resource occupancy ratio; The query module is used to: Determine whether there is a first target time zipper record in the multiple first time zipper records; wherein the first target time zipper record contains the first identifier and the second identifier, and the delivery timestamp is between the start effective time and the end effective time in the first target time zipper record; If so, the resource occupancy ratio in the first target time zip record is used as the target resource occupancy ratio of the same object to the business entity of the service at the delivery timestamp.

12. The device according to claim 11, in, The query module is also used for: If it does not exist, query the second time zipper table associated with the task type according to the first identifier and the delivery timestamp; wherein the second time zipper table includes multiple second time zipper records, and the second time zipper record is used to record the mapping relationship between the object identifier, object rank, rank ratio, object rank start effective time and end effective time of the object associated with the task type; Determine a second target time zipper record from the plurality of second time zipper records; wherein the second target time zipper record contains the first identifier, and the delivery timestamp is between the start effective time and the end effective time in the second target time zipper record; The job grade ratio in the second target time zipper record is used as the target resource occupancy ratio of the same object to the business entity of the service at the delivery timestamp.

13. The device according to claim 10, in, The first time zipper table is obtained by using the following modules: an acquisition module, configured to acquire an object management information adjustment table associated with the task type; wherein the object management information adjustment table is configured to record object management information of at least one target object, wherein the target object refers to an object in which at least one of the object rank, the effective timestamp of the object rank, and the rank ratio has changed; An updating module, configured to update a first object management information table associated with the task type based on the object management information adjustment table to obtain a second object management information table; wherein the first object management information table is used to record object management information of objects associated with the task type; The second generating module is used to generate the first time zipper table according to the second object management information table and the business entity table; wherein the business entity table is used to record entity management information of multiple business entities.

14. The device according to claim 13, in, The second generating module is used for: A time zipper algorithm is executed on the second object management information table to obtain a second time zipper table; wherein the second time zipper table includes a plurality of second time zipper records, and the second time zipper record is used to record the mapping relationship between the object identifier, the object rank, the rank ratio, the start effective time and the end effective time of the object associated with the task type; Acquire the business entity table; wherein the business entity table contains a plurality of business entity management records, and the business entity management records are used to record the mapping relationship between the entity identifier, entity ratio, entity ratio start effective time and end effective time of the business entity; The second time zipper table and the business entity table are merged to obtain the first time zipper table.

15. The device according to claim 14, in, The second object management information table includes a plurality of object management information records, and the object management information records are used to record the mapping relationship between the object identifier, the object rank, the rank ratio and the effective timestamp of the object rank associated with the task type; The second generating module is used for: Determining, from the plurality of object management information records, a target object management information record containing the same object identifier; Sorting each of the target object management information records in descending order according to the corresponding effective timestamps to obtain a sorted sequence; For i target object management information records in the sorting sequence, the effective time stamp in the i-th target object management information record is used as the effective start time corresponding to the object rank in the i-th target object management information record; In the case of i=1, the specified timestamp is used as the end effective time corresponding to the object rank in the i-th target object management information record; When i is a positive integer greater than 1, the effective time stamp in the i-1th target object management information record is used as the end effective time of the object rank in the i-th target object management information record; A second time zipper record in the second time zipper table is generated according to the object identifier, object rank and rank ratio in the i-th target object management information record, and the start effective time and end effective time corresponding to the object rank in the i-th target object management information record.

16. The device according to claim 14, in, The second generating module is used for: Determine the first effective period according to the effective start time and effective end time of the object's rank in any second time zipper record in the second time zipper table; Determine a second effective period according to the effective start time and effective end time of the entity ratio in any business entity management record in the business entity table; Determine whether there is an intersection between the first effective time period and the second effective time period; If it exists, any second time zipper record and any business entity management record are merged to obtain a first time zipper record, and the record is entered into the first time zipper table.

17. The device according to claim 16, in, The second generating module is used for: Determining the resource occupancy ratio contained in the first time zipper record to be generated according to the product of the job level ratio in any second time zipper record and the entity ratio in any business entity management record; Determine, according to the intersection, the effective start time and effective end time of the resource occupancy ratio included; The first time zipper record is generated according to the object identifier in any of the second time zipper records, the entity identifier in any of the business entity management records, the resource occupancy ratio contained, the start effective time and the end effective time of the resource occupancy ratio contained.

18. The device according to any one of claims 10 to 17, in, The device also includes: A sending module, used to send the execution result of the pending task to a designated account; and / or, The storage module is used to persistently store the execution results of the tasks to be processed.

19. An electronic device, include: at least one processor; as well as a memory communicatively connected to the at least one processor; wherein, The memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to execute the task execution method according to any one of claims 1 to 9.

20. A non-transitory computer-readable storage medium storing computer instructions, in, The computer instructions are used to enable the computer to execute the task execution method according to any one of claims 1 to 9.

21. A computer program product, comprising a computer program, wherein when the computer program is executed by a processor, the computer program implements the steps of the task execution method according to any one of claims 1 to 9.

Images