Task processing method and device, electronic equipment and storage medium

Abstract

The embodiment of the invention discloses a task processing method and device, electronic equipment and a storage medium, and the method comprises the steps: determining a task ownership to which a to-be-processed task belongs when the received to-be-processed task comprises at least two to-be-split sub-tasks; determining target splitting configuration data corresponding to the task ownership, and processing the at least two to-be-split sub-tasks according to the target splitting configuration data to obtain at least one to-be-processed sub-task; and configuring a processing attribute for the to-be-processed sub-task, and sending the to-be-processed sub-task and the corresponding processing attribute to the target platform so as to process the to-be-processed sub-task based on a user corresponding to the target platform. According to the technical scheme provided by the embodiment of the invention, the technical problem that task processing is difficult due to the fact that the task can only be pre-processed by a task ownership party and cannot be pre-processed by a logistics party in the prior art is solved, and the effects of improving the distribution efficiency and improving the use experience of a user are achieved while the task processing efficiency is improved.

Description

Technical Field

[0001] Embodiments of the present invention relate to the field of data processing technology, and in particular to a task processing method, device, electronic device and storage medium. Background Art

[0002] In the logistics industry, there are usually logistics parties and task owners. The task owner can issue tasks to the logistics party that need to be processed. The task usually contains subtasks with different task attributes. For example, the task attribute can be the delivery address, delivery item information, task type, etc. At this time, the task needs to be processed. The processing method is usually that the task owner performs pre-processing on the task, and the logistics party performs subsequent further processing on the task based on the result of the pre-processing to complete each subtask in the task.

[0003] When implementing the technical solution based on the above method, the inventor found the following problems:

[0004] Currently, when processing tasks, only the party to which the task belongs can perform pre-processing of the task, while the logistics party cannot perform pre-processing of the task, resulting in difficulties in task processing. Summary of the invention

[0005] The present invention provides a task processing method, device, electronic device and storage medium, which improve the task processing efficiency while improving the delivery efficiency, thereby achieving the technical effect of improving the user experience.

[0006] In a first aspect, an embodiment of the present invention provides a task processing method, the method comprising:

[0007] When the received task to be processed includes at least two subtasks to be split, determining the task owner to which the task to be processed belongs;

[0008] Determine the target splitting configuration data corresponding to the task owner, and process the at least two to-be-split subtasks according to the target splitting configuration data to obtain at least one to-be-processed subtask;

[0009] A processing attribute is configured for the at least one to-be-processed subtask, and the to-be-processed subtask and the corresponding processing attribute are sent to a target platform, so that the to-be-processed subtask is processed based on a user corresponding to the target platform.

[0010] Furthermore, the method further comprises:

[0011] When receiving an original task, checking the overall parameters of each subtask to be split in the original task; the overall parameters include the parameters of the items to be dispatched and the service parameters of each subtask to be split;

[0012] If the verification result is consistent with the preset verification result, the original task is determined to be the task to be processed.

[0013] Furthermore, the to-be-selected split configuration data corresponding to the task owner includes a plurality of data, and the method further includes:

[0014] Determine the target split configuration data according to the priorities corresponding to the split configuration data to be selected; or,

[0015] Determining the target split configuration data from the split configuration data to be selected according to the target sender corresponding to the task to be processed; or,

[0016] The target splitting configuration data is determined from the splitting configuration data to be selected according to the specification parameters corresponding to each to-be-split subtask in the to-be-processed task.

[0017] Furthermore, the processing attribute includes a processing timeliness attribute, and the method further includes:

[0018] According to the parameters of the items to be dispatched in each of the subtasks to be processed, a processing timeliness attribute is configured for the corresponding subtask to be processed.

[0019] Furthermore, the method further comprises:

[0020] Generate a to-be-delivered task corresponding to the to-be-processed subtask;

[0021] The delivery identifier of the task to be delivered and the subtask to be processed are sent to the target platform.

[0022] Furthermore, the method further comprises:

[0023] When receiving a task cancellation instruction, obtaining the task identifier carried in the task cancellation instruction;

[0024] If the task to be canceled corresponding to the task identifier includes at least two subtasks to be split, the task to be canceled is processed based on the target data processing method.

[0025] Furthermore, the method further comprises:

[0026] When the subtask to be split has been processed in the target platform, feedback information of cancellation failure is fed back to the task owner corresponding to the task to be canceled;

[0027] When the subtask to be split has not been processed in the target platform or the target platform has not received the subtask to be split, feedback information of successful cancellation is fed back to the task owner corresponding to the task to be canceled.

[0028] Furthermore, the method further comprises:

[0029] When the cancellation of at least two to-be-split subtasks in the to-be-cancelled task is completed, the task statuses of the at least two to-be-split subtasks are updated to determine the processing progress of the to-be-split subtasks based on the task statuses.

[0030] Furthermore, the method also includes: the subtask to be split includes at least one of delivery location information and task specification information.

[0031] In a second aspect, an embodiment of the present invention further provides a task processing device, the device comprising:

[0032] A task owner determination module, used to determine the task owner to which the task to be processed belongs when the received task to be processed includes at least two subtasks to be split;

[0033] A task splitting module, used to determine the target splitting configuration data corresponding to the task owner, and process the at least two to-be-split subtasks according to the target splitting configuration data to obtain at least one to-be-processed subtask;

[0034] The task sending module is used to configure processing attributes for the at least one to-be-processed subtask, and send the to-be-processed subtask and the corresponding processing attributes to the target platform, so as to process the to-be-processed subtask based on the user corresponding to the target platform.

[0035] In a third aspect, an embodiment of the present invention further provides an electronic device, the electronic device comprising:

[0036] one or more processors;

[0037] a storage device for storing one or more programs,

[0038] When one or more programs are executed by one or more processors, the one or more processors implement any task processing method as in the embodiments of the present invention.

[0039] In a fourth aspect, an embodiment of the present invention further provides a storage medium comprising computer executable instructions, which, when executed by a computer processor, are used to perform a task processing method as described in any one of the embodiments of the present invention.

[0040] The technical solution of the embodiment of the present invention is to determine the task owner to which the task to be processed belongs when the received task to be processed includes at least two subtasks to be split; determine the target splitting configuration data corresponding to the task owner, and process at least two subtasks to be split according to the target splitting configuration data to obtain at least one subtask to be processed; configure processing attributes for at least one subtask to be processed, and send the subtask to be processed and the corresponding processing attributes to the target platform, so as to process the subtask to be processed based on the user corresponding to the target platform. The technical solution of the embodiment of the present invention solves the problem that only the task owner can pre-process the task in the prior art, while the logistics party cannot pre-process the task, resulting in difficulty in task processing, and realizes that when receiving the task to be processed including at least two subtasks to be split, the target splitting configuration data matching the task owner to which the task to be processed belongs is retrieved to split the at least two subtasks to be split, so that not only the split subtasks to be processed meet the splitting requirements of the task owner, but also the task processing efficiency and distribution efficiency are improved by performing task processing on each subtask to be processed. At the same time, by configuring a processing attribute for at least one subtask to be processed, the subtask to be processed is processed based on the processing attribute, thereby achieving a technical effect of improving user experience while improving task processing effect. BRIEF DESCRIPTION OF THE DRAWINGS

[0041] In order to more clearly illustrate the technical solutions of the exemplary embodiments of the present invention, the following briefly introduces the drawings required to describe the embodiments. Obviously, the drawings introduced are only drawings of a part of the embodiments to be described in the present invention, rather than all the drawings. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0042] Figure 1 A flowchart of a task processing method provided by an embodiment of the present invention;

[0043] Figure 2 A schematic diagram of a method for verifying integrity parameters provided by an embodiment of the present invention;

[0044] Figure 3 A schematic diagram of a task processing method provided by an embodiment of the present invention;

[0045] Figure 4 A flowchart of a task processing method provided by an embodiment of the present invention;

[0046] Figure 5 A flowchart of a task processing method provided by an embodiment of the present invention;

[0047] Figure 6A schematic diagram of a task processing method provided by an embodiment of the present invention;

[0048] Figure 7 A schematic diagram of the structure of a task processing device provided by an embodiment of the present invention;

[0049] Figure 8 The present invention is a schematic diagram of the structure of an electronic device provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0050] The present invention will be further described in detail below in conjunction with the accompanying drawings and embodiments. It is to be understood that the specific embodiments described herein are only used to explain the present invention, rather than to limit the present invention. It should also be noted that, for ease of description, only parts related to the present invention, rather than all structures, are shown in the accompanying drawings.

[0051] Before introducing the present technical solution, the application scenario may be described first. For example, in a distribution scenario, the task owner issues a distribution task to the logistics party. At this time, there may be a situation where the distribution task contains subtasks with different task attributes, and the distribution task needs to be processed. If the task owner does not pre-process the task, the logistics party will not be able to perform subsequent processing on the task, and there is a problem of not being able to process the task in a timely and effective manner. At this time, the logistics party can split the task based on the technical solution provided in the embodiment of the present invention, so that it can be processed based on the split subtasks.

[0052] Figure 1 A flowchart of a task processing method provided in an embodiment of the present invention is provided. This embodiment is applicable to the situation of processing tasks. The method can be executed by a task processing device. The device can be implemented in the form of software and / or hardware. The hardware can be an electronic device, such as a mobile terminal, a PC or a server.

[0053] like Figure 1 As shown, the method includes:

[0054] S110: When the received task to be processed includes at least two subtasks to be split, determine the task owner to which the task to be processed belongs.

[0055] Among them, the pending task may refer to a distribution task that needs to be processed. The pending task may contain multiple subtasks to be split, and the subtasks to be split may include at least one of the delivery location information and task specification information. The delivery location information may be the delivery address, and the task specification information may be understood as the attribute information of the task, for example, it may be the information of the items to be delivered in the task (such as quantity, category, type, etc.), or it may be the task type, such as procurement type, outbound type, recall type, etc. The task owner may be understood as the publisher of the task, which may be an individual, unit, department or merchant, etc.

[0056] In this embodiment, the user can generate a task to be processed according to the needs of the upstream system, and the task can contain task parameters of multiple subtasks, for example, the task parameters can be the quantity, specification, type, address, etc. of the items to be delivered. After the system receives the task to be processed, it can parse the information carried on the task to determine which user has issued the task, and the party that issued the task can be regarded as the task owner of the task to be processed.

[0057] It should be noted that in order to improve the effectiveness of task reception and ensure the efficiency of task processing, when receiving the distribution task submitted by the user, the task information in the distribution task can be verified to verify whether it meets the preset task acceptance conditions. For example, it can be verified whether the quantity of goods in the inventory can meet the stocking requirements in the distribution task. If so, it can be considered that the task acceptance conditions are met, and the distribution task can be received and treated as a task to be processed.

[0058] In this embodiment, when an original task is received, an overall parameter check is performed on each subtask to be split in the original task; if the check result is consistent with a preset check result, the original task is determined to be a task to be processed.

[0059] Among them, the original task refers to the task that has not been verified and processed. At this time, the task is the original task submitted by the user. The overall parameters include the parameters of the items to be matched and the service parameters of each sub-task to be split. The parameters of the items to be matched can be used to characterize the item attributes of the items to be matched, for example, the item identification, item quantity, item specifications, the warehouse to which the item belongs, the item owner code and other information. The service parameters can be used to characterize the service information provided to the task owner, for example, the unit mileage distribution cost, the warehouse information with usage rights, the available inventory and the effective use period of the warehouse, etc. The preset verification result can be a verification pass, which means that the task meets the preset verification requirements, that is, it is considered that the task acceptance conditions are met.

[0060] Specifically, after receiving the original task of stocking and delivery submitted by the user to the system, the parameters of the items to be distributed and the service parameters of the multiple subtasks to be split contained in the original task can be parsed, and then all the parameters can be classified and integrated to obtain the overall parameters. For example, assuming that the parameters of the items to be distributed include the item quantity parameters, the item quantity parameters of the same item to be distributed can be accumulated to obtain the total quantity of items to be distributed corresponding to the item to be distributed, and used as the overall parameters. Or, assuming that the service parameters are business permissions, all business permissions can be integrated as the overall parameters. Further, the overall parameters can be verified, and the verification method can be: comparing the overall parameters with the total item attributes and preset service attributes stored by the task owner. If the total quantity of items to be distributed in the overall parameters is less than the total item attributes corresponding to the item, then it can be considered that the item information in the warehouse can meet the demand for the items to be distributed; if the service parameters in the overall parameters are consistent with the preset service attributes, then it can be considered that the distribution service can be provided to the task owner. If these conditions are met, the verification result of the integrity parameter verification can be considered as a successful verification, that is, consistent with the preset verification result. At this time, the original task can be used as a pending task to perform subsequent processing based on the pending task to ensure the smooth progress of the task. It should be noted that if the total quantity of items to be dispatched corresponding to the items to be dispatched in the integrity parameters is greater than the total item attributes, or the service parameters are inconsistent with the preset service attributes, the verification result of the integrity parameter verification is considered to be a verification failure. At this time, the verification failure result and the verification failure details (such as insufficient inventory of item A to be dispatched) can be fed back to the task owner, and the order can be rejected, so that the task owner can learn about the receipt of the task based on the feedback information and make corresponding processing in a timely manner to improve the user experience.

[0061] For example, see Figure 2 , Figure 2 It can be represented as a schematic diagram of a method for verifying the overall parameters. First, the task owner can publish the original task on platform A, and platform A submits the original task to platform B. When platform B receives the original task containing at least two subtasks to be split, it verifies the overall parameters of each subtask to be split in the original task and determines the verification result. For example, verify whether the inventory can supply the quantity of items required for distribution in the original task, and verify whether the task owner has the authority to use the inventory to be used. When the verification conditions are met, the verification is considered successful. If the verification conditions are not met, the verification is considered to have failed. Further, it is determined whether the verification result is consistent with the preset verification result (verification success). If so, the original task is saved as a pending task, and the information of successful reception is fed back to platform A; if not, it is considered that the task reception has failed, and the information of failed reception is fed back to platform A.

[0062] S120: Determine the target splitting configuration data corresponding to the task owner, and process at least two to-be-split subtasks according to the target splitting configuration data to obtain at least one to-be-processed subtask.

[0063] Among them, the target splitting configuration data may include at least one preset splitting rule. The preset splitting rule refers to a pre-set rule for splitting a task, which can split the task into multiple subtasks to be processed. Each subtask to be processed may contain one subtask to be split, or may contain multiple subtasks to be split. It should be noted that multiple subtasks to be split in a subtask to be processed may be similar in a certain dimension. For example, the dimension may be the delivery address, item aging, item specifications, warehouse to which it belongs, task importance, etc., which is related to the splitting rule.

[0064] In this embodiment, based on the identification of the task owner, the split configuration data matching the identification can be retrieved from the preset configuration library as the target split configuration data, wherein the preset configuration library contains multiple pre-configured split configuration data to be selected; or, if there is no split configuration data matching the identification in the preset configuration library, the pre-defined general split configuration data can be used as the target split configuration data corresponding to the task owner; or, the general split configuration data can be directly used as the target split configuration data corresponding to the task owner. Furthermore, each subtask to be split can be processed based on the splitting rules in the target split configuration data to obtain at least one subtask to be processed. For example, subtasks with similar delivery addresses can be combined into one subtask as a subtask to be processed; or, subtasks with similar item specifications can be combined into a subtask to be processed; or, a subtask with a large distribution volume or a large variety of distribution items can be reasonably divided into multiple subtasks, all of which are subtasks to be processed; or, subtasks with similar task levels (such as task processing priority, importance level, security level, etc.) can be combined into one subtask to be processed, so that the task level can be used to intuitively identify which subtask to be processed contains important subtasks and which subtask to be processed contains ordinary subtasks, so that the processing attributes of the subtasks to be processed can be configured more reasonably and effectively in the future. The advantage of dividing tasks is that it can improve the efficiency of task processing while realizing the rational division of tasks, thereby improving the distribution efficiency.

[0065] For example, see Figure 3 , Figure 3It can be represented as a task processing method diagram. When platform C receives a pending task containing at least two pending subtasks, it can notify the splitting platform to determine the target splitting configuration data corresponding to the task owner from the pending splitting configuration data in the configuration center, and then the splitting platform splits and processes at least two pending subtasks according to the target splitting configuration data to obtain at least one pending subtask, and sends at least one pending subtask to platform C. Platform C can transfer the pending task inventory to the pending subtask, generate a fulfillment order according to the pending subtask, and then trigger the task fulfillment process, so that after the task fulfillment process is triggered, platform D configures the processing time attribute for the pending subtask.

[0066] S130: Configure processing attributes for at least one to-be-processed subtask, and send the to-be-processed subtask and the corresponding processing attributes to the target platform, so that the to-be-processed subtask is processed based on a user corresponding to the target platform.

[0067] Among them, the processing attributes can be used to represent the specific information when processing tasks. For example, the processing attributes can be attributes such as preparation time, insurance information, delivery time, and transportation method. They can also be processing time attributes. For example, if some subtasks are more urgent, their processing time attributes can be configured as expedited attributes; if some subtasks are not urgent, their processing time attributes can be configured as ordinary processing attributes. It should be noted that the configuration of processing attributes is related to the task information of the subtask to be processed. For example, the processing attributes of the subtask for distributing seafood items can be configured as refrigeration, air transportation, and transportation time of 2 days; the processing attributes of the subtask for distributing key service customers can be configured as expedited transportation. The target platform can refer to the operating system of the computer hardware or software required to process the task. For example, it can be a stocking system, a distribution system, or a distribution system that integrates stocking and distribution functions.

[0068] In practical applications, the task attributes of the pending subtasks can be used to configure corresponding processing attributes for the pending subtasks. For example, the task attribute is the importance. If the importance of the pending subtask is high, its processing attribute can be set to a high priority to give priority to the pending subtask. Alternatively, the pending subtasks can also be configured with corresponding processing attributes based on information such as the parameters of the items to be dispatched and the service parameters in the pending subtasks. For example, the parameter of the items to be dispatched is the number of items. If the number of items is large, the processing time in the processing attribute can be set within a constraint time, so that the processing progress can be controlled by constraining the processing time to ensure that the task is executed smoothly; or, the parameter of the items to be dispatched is the storage method, such as freezing, in which case the processing attribute can be configured as air transport; or, the service parameter is the warehouse validity period, and the processing time limit of the processing attribute can be set within the warehouse validity period to ensure that the task is executed within the warehouse validity period, thereby improving the user experience of the task owner. After configuring the processing attributes for at least one pending subtask, the pending subtask and the corresponding processing attributes can be sent to the target platform accordingly, so that the user corresponding to the target platform can process the pending subtask. Alternatively, a task list may be generated based on the subtasks to be processed and the corresponding processing attributes, and then the task list corresponding to each subtask to be processed may be sent to the target platform, so that the executing users on the target platform can clearly understand the specific task information that needs to be processed based on the task list for processing.

[0069] In order to ensure the quality of items when they arrive at the consignee, improve the consignee's receiving experience, and the user experience of the task owner, when configuring processing attributes for at least one pending subtask, you can configure processing timeliness attributes for the corresponding pending subtask based on the parameters of the items to be shipped in each pending subtask.

[0070] Specifically, for configuring a processing time limit attribute for a subtask to be processed, the processing time required for the subtask to be processed can be configured according to the parameters of the items to be dispatched of the subtask to be processed, and the processing time required can be used as the processing time limit attribute. For example, if the parameters of the items to be dispatched are the shelf life of the items to be dispatched, which is 10 days, then the processing time limit attribute can be set to 2 days to complete the dispatching task within 2 days. Accordingly, the corresponding processing time limit attribute can be configured for each subtask to be processed.

[0071] It should be noted that in actual applications, when processing pending tasks, there may be situations where system platforms with different functions are used for joint processing. For example, the splitting platform is used to split the pending tasks, the configuration platform is used to configure the processing attributes for the pending subtasks, or the stocking platform is used to stock, and then the distribution platform is used to distribute the stocks after stocking, etc. It is understandable that different processing platforms may have different marking information for the tasks when processing the same pending subtask or the pending subtask. For example, the splitting platform marks task A as 1, and the configuration platform marks task A as A-1. In order to enable the system platform to effectively manage tasks, in the process of sending the pending subtasks and the corresponding processing attributes to the target platform, a pending distribution task corresponding to the pending subtask can be generated; the distribution identification of the pending distribution task and the pending subtask are sent to the target platform.

[0072] The delivery identifier can be used to represent the uniqueness of the task to be delivered, and its representation form can be any one or any combination of letters, words, numbers, and symbols. For example, it can be represented by a delivery order number.

[0073] Specifically, the subtask to be processed can be used as the task to be delivered, and a delivery identifier corresponding to the task to be delivered can be generated using a coding method. Furthermore, the delivery identifier of the task to be delivered and the subtask to be processed can be sent to the target platform together, so that the target platform can perform distribution management on the corresponding subtask to be processed based on the delivery identifier. Figure 3 After platform D configures the processing time attribute for the pending subtask, it can generate the pending delivery task based on the pending subtask, and send all the pending subtasks, processing time attributes and delivery identification to the target platform, so as to process the pending subtask based on the user corresponding to the target platform.

[0074] The technical solution of the embodiment of the present invention is to determine the task owner to which the task to be processed belongs when the received task to be processed includes at least two subtasks to be split; determine the target splitting configuration data corresponding to the task owner, and process at least two subtasks to be split according to the target splitting configuration data to obtain at least one subtask to be processed; configure processing attributes for at least one subtask to be processed, and send the subtask to be processed and the corresponding processing attributes to the target platform, so as to process the subtask to be processed based on the user corresponding to the target platform. The technical solution of the embodiment of the present invention solves the problem that only the task owner can pre-process the task in the prior art, while the logistics party cannot pre-process the task, resulting in difficulty in task processing, and realizes that when receiving the task to be processed including at least two subtasks to be split, the target splitting configuration data matching the task owner to which the task to be processed belongs is retrieved to split the at least two subtasks to be split, so that not only the split subtasks to be processed meet the splitting requirements of the task owner, but also the task processing efficiency and distribution efficiency are improved by performing task processing on each subtask to be processed. At the same time, by configuring a processing attribute for at least one subtask to be processed, the subtask to be processed is processed based on the processing attribute, thereby achieving a technical effect of improving user experience while improving task processing effect.

[0075] Figure 4 A flowchart of a task processing method provided by an embodiment of the present invention is provided. Based on the above embodiment, the to-be-selected split configuration data corresponding to the task owner may include multiple, and the implementation method of determining the target split configuration data corresponding to the task owner may also include multiple, and its specific implementation method can refer to the technical solution of this embodiment. Among them, the technical terms that are the same or corresponding to the above embodiment are not repeated here.

[0076] like Figure 4 As shown, the method specifically comprises the following steps:

[0077] S210: When the received task to be processed includes at least two subtasks to be split, determine the task owner to which the task to be processed belongs.

[0078] S220 : Determine target split configuration data according to the priorities corresponding to the split configuration data to be selected.

[0079] The split configuration data to be selected refers to pre-configured split configuration data that can be selected for use, and each split configuration data to be selected can be used as a split rule. The priority can be used to characterize the order in which the split configuration data is used, for example, the split configuration data with a higher priority is used first, and the split configuration data with a lower priority is used later.

[0080] Specifically, a preset number of to-be-selected split configuration data with higher priority can be taken as target split configuration data. For example, the to-be-selected split configuration data can be sorted from high to low based on priority, and then a preset number of to-be-selected split configuration data in the front can be taken as target split configuration data.

[0081] S230 , determining target split configuration data from the split configuration data to be selected according to the target sender corresponding to the task to be processed.

[0082] The target sender may refer to the party that sends the task to be processed. The target sender corresponds to the party to which the task belongs and may be the same party.

[0083] In practical applications, in order to ensure that the determined target split configuration data meets the splitting requirements of the task owner, the user corresponding to the task to be processed can be determined as the target sender when determining the target split configuration data. Further, it is possible to find out whether the split configuration data to be selected corresponding to the target sender is stored in the preset configuration library. If so, all the split configuration data to be selected corresponding to the target sender can be screened out, and then the target split configuration data can be determined from the screened split configuration data to be selected based on the priority, or the screened split configuration data to be selected can be directly used as the target split configuration data. If it does not exist, it means that the split configuration data corresponding to the target sender is not pre-configured. At this time, the target split configuration data can be determined from the split configuration data to be selected based on the preset split configuration data selection rules, or the split configuration data with a general identifier in the split configuration data to be selected can be used as the target split configuration data.

[0084] S240 , determining target splitting configuration data from the splitting configuration data to be selected according to the specification parameters corresponding to each to-be-split subtask in the to-be-processed task.

[0085] The specification parameter can be used to characterize the task type of the subtask to be split. For example, the specification parameter of the subtask 1 to be split is A, which characterizes it as a procurement task; the specification parameter of the subtask 2 to be split is B, which characterizes it as a distribution task.

[0086] Specifically, the parameter data in each subtask to be split can be analyzed to determine the specification parameters in each subtask to be split, and then based on the specification parameters of each subtask to be split, the split configuration data to be selected that matches the specification parameters can be retrieved from the split configuration data to be selected as the target split configuration data. It is understandable that the specification parameters of each subtask to be split are different, and the corresponding target split configuration data may also be different. For example, the target split configuration data corresponding to the procurement task with specification parameter A is split based on the item parameters; the target split configuration data corresponding to the distribution task with specification parameter B is split based on the warehouse to which it belongs.

[0087] On the basis of the above scheme, when at least two sub-tasks to be split are processed according to the target splitting configuration data and at least one sub-task to be processed is obtained, all sub-tasks to be split corresponding to the same target splitting configuration data can be grouped together, and then these sub-tasks to be split can be split based on the target splitting configuration data to obtain at least one sub-task to be processed, thereby improving the rationality and accuracy of task splitting.

[0088] It should be noted that the above three steps S220, S230, and S240 are all implementation methods for determining the target split configuration data corresponding to the task owner. When determining the target split configuration data corresponding to the task owner, S220 to S240 can be executed sequentially or in parallel, or any one of the steps can be selected to determine the target split configuration data, which is not limited here. The above order is only the order for explaining the technical solutions in each step, not the execution order of each step.

[0089] In order to meet the task splitting requirements of the task owner, an interface for configuring splitting configuration data can also be provided for the task owner, so that the task owner can use the server to call the interface and configure the corresponding splitting configuration data as the splitting configuration data to be selected based on its own splitting requirements, so that the target splitting configuration data corresponding to the task owner can be determined from the splitting configuration data to be selected later. The advantage of this setting is that by decoupling the task splitting logic from the business of the task owner, the task owner's business can be quickly accessed, the business requirements of the task owner to submit a task with multiple delivery addresses can be met, and the application experience of the task owner can be improved. At the same time, the task owner can also be supported to configure the splitting rules in the configuration center, so that the subtasks after splitting the tasks issued by the task owner meet the splitting requirements of the task owner, while improving the convenience and flexibility of data configuration, and improving the accuracy of task splitting, so as to achieve the technical effect of meeting the needs of the task owner and improving its user experience.

[0090] S250: Process at least two to-be-split subtasks according to the target splitting configuration data to obtain at least one to-be-processed subtask.

[0091] S260: Configure processing attributes for at least one to-be-processed subtask, and send the to-be-processed subtask and the corresponding processing attributes to the target platform, so that the to-be-processed subtask is processed based on a user corresponding to the target platform.

[0092] The technical solution of the embodiment of the present invention determines the target splitting configuration data according to the priority corresponding to each to-be-selected splitting configuration data; or, determines the target splitting configuration data from the to-be-selected splitting configuration data according to the target sender corresponding to the task to be processed; or, determines the target splitting configuration data from the to-be-selected splitting configuration data according to the specification parameters corresponding to each to-be-split subtask in the task to be processed, so that at least two to-be-split subtasks are processed based on the target splitting configuration data to obtain at least one to-be-processed subtask, which not only ensures that the to-be-processed subtasks after splitting meet the splitting requirements of the target sender, but also ensures that the to-be-split subtasks in the to-be-processed subtasks after splitting have the same specification parameters, thereby improving the delivery efficiency.

[0093] Figure 5 This is a flowchart of a task processing method provided by an embodiment of the present invention. On the basis of the above-mentioned embodiment, in the process of processing a task, the task can also be canceled to meet the application requirements of the task cancellation scenario. The specific implementation method can refer to the technical solution of this embodiment. Among them, the technical terms that are the same or corresponding to the above-mentioned embodiment are not repeated here.

[0094] like Figure 5 As shown, the method includes:

[0095] S310: When a task cancellation instruction is received, obtain a task identifier carried in the task cancellation instruction.

[0096] The task cancellation instruction may be a code or program for instructing to cancel the task. The task identifier may be used to characterize the uniqueness of the task.

[0097] Specifically, when a task cancellation instruction triggered by a task sender or a task executor is received, the task cancellation instruction may be parsed to obtain a task identifier carried in the task cancellation instruction, so as to determine which task is to be canceled based on the task identifier.

[0098] S320: If the task to be canceled corresponding to the task identifier includes at least two subtasks to be split, the task to be canceled is processed based on the target data processing method.

[0099] The task to be cancelled refers to a task that needs to be cancelled, which may be a task to be processed including at least two subtasks to be split, or a task to be processed including one subtask to be split. The target data processing method refers to the execution method for resolving the event of canceling the task.

[0100] In the present embodiment, after determining the task identifier, the pending task corresponding to the task identifier can be used as a task to be canceled, and then determine whether the task to be canceled includes at least two subtasks to be split. If so, it means that the task to be canceled may have been split and processed, and at this time, the pre-configured target data processing method can be used to process the task to be canceled. For example, if at least two of the subtasks to be split in the task to be canceled have been processed, then the result of the cancellation failure and the processing progress and other information can be fed back to the task owner corresponding to the task to be canceled, so that the task to be canceled can be processed and cannot be canceled through the task owner. If at least two of the subtasks to be split in the task to be canceled have not been processed, then the task to be canceled and the corresponding at least two subtasks to be split can be canceled. If the task to be canceled does not include at least two sub-tasks to be split, it means that the task to be canceled has not been split and processed, and it has a delivery address. At this time, it can be directly determined whether the task to be canceled has been processed by the user of the target platform. If it has not been processed, the task to be canceled can be directly marked as canceled, and the result of successful cancellation can be fed back to the task canceling party. If it has been processed, the result of failed cancellation and processing progress and other information will be fed back to the task owner.

[0101] It should be noted that the technical solution provided in this embodiment includes multiple execution stages, including a splitting stage for splitting the tasks to be processed, a configuration stage for configuring the subtasks to be processed, and a sending stage for sending the subtasks to be processed and processing attributes. Based on this, it can be seen that before the subtasks to be processed and the processing attributes are sent to the target platform, the tasks to be processed and the corresponding subtasks to be split can be cancelled. If the subtasks to be processed and the processing attributes are sent to the target platform, but the items to be delivered have not been shipped out of the warehouse, the task can also be cancelled. If the items to be delivered have been shipped out of the warehouse, it means that the items are already in the distribution stage, and the task may not be canceled, and it is necessary to feedback the cancellation failure information. Alternatively, when the items are already in the distribution stage, it can be determined based on the service parameters in the subtasks to be processed whether to cancel the subtasks to be processed. For example, if the service parameters include item recall, the task can be canceled after the items are recalled.

[0102] In actual applications, the implementation method for processing the canceled task based on the target data processing method can be: when the subtask to be split has been processed in the target platform, feedback information of cancellation failure is fed back to the task owner corresponding to the task to be canceled; when the subtask to be split has not been processed in the target platform or the target platform has not received the subtask to be split, feedback information of cancellation success is fed back to the task owner corresponding to the task to be canceled.

[0103] Specifically, it can be determined whether the subtask to be split has been processed on the target platform. If it has been processed on the target platform, it means that the subtask to be split has been executed completely. At this time, the subtask to be split and the corresponding task to be canceled cannot be canceled. For example, if the target platform is a stocking warehouse, if the subtask to be split has been processed in the stocking warehouse, it means that the goods in the subtask to be split have been shipped out of the warehouse, and the task cancellation fails. The feedback information of the cancellation failure can be fed back to the task owner corresponding to the task to be canceled, so that the task owner can be informed of the task cancellation in time. If it has not been processed on the target platform, it may be shipped out of the warehouse. In order to improve the application experience of the task owner, the task to be canceled and all the subtasks to be split contained in the task to be canceled can be canceled, and the feedback information of the successful cancellation can be fed back to the task owner corresponding to the task to be canceled. If the target platform does not receive the subtask to be split, it is considered that the subtask to be split has not been processed. At this time, the task to be canceled and all the subtasks to be split contained in the task to be canceled can be canceled to improve the integrity of the task cancellation and prevent errors in task processing. At the same time, the feedback information of the successful cancellation can be fed back to the task owner corresponding to the task to be canceled.

[0104] In this embodiment, when the cancellation of at least two to-be-split subtasks in the to-be-cancelled task is completed, the task statuses of the at least two to-be-split subtasks are updated to determine the processing progress of the to-be-split subtasks based on the task statuses.

[0105] Among them, the task status can be used to characterize the processing status of the task. For example, the task status can be receiving status, splitting status, configuration status, stocking status, outbound status, delivery status, received status, etc.

[0106] Specifically, when it is detected that the cancellation processing of at least two subtasks to be split in the task to be canceled is completed, the task status of at least two subtasks to be split can be updated to the canceled status, so as to timely know the processing progress of the subtasks to be split based on the task status and realize unified management of tasks.

[0107] For example, see Figure 6 , Figure 6It can be represented as a task processing method diagram. First, the customer can submit task cancellation information to platform A. When platform A receives the customer's cancellation information, it sends a task cancellation instruction to platform B. After receiving the task cancellation instruction, platform B determines whether the task to be canceled corresponding to the task identifier in the task cancellation instruction includes at least two subtasks to be split. If not, the task status of the task to be canceled is updated to be successfully canceled, and the cancellation success information is fed back to platform A; if so, platform C determines whether the subtask to be split is sent to the target platform. If not, the task status of the subtask to be split is updated to be successfully canceled. If it has been sent, a cancellation instruction is sent to the target platform, and the target platform determines whether the subtask to be split is shipped out of the warehouse. If it is shipped out of the warehouse, it returns a cancellation failure. If it is not shipped out of the warehouse, it returns a cancellation success and sends the cancellation result to platform C. After receiving the cancellation result, platform C can determine whether the cancellation result is a successful cancellation. If so, the task status of the task to be canceled is updated to be successfully canceled; if not, the cancellation failure information is fed back to platform A.

[0108] The technical solution of the embodiment of the present invention is to obtain the task identifier carried in the task cancellation instruction when receiving the task cancellation instruction. If the task to be cancelled corresponding to the task identifier includes at least two subtasks to be split, the task to be cancelled is processed based on the target data processing method, so as to cancel the task containing multiple delivery addresses and improve the convenience of task cancellation. At the same time, when canceling the task, the task owner only needs to send the task cancellation instruction according to the task information when it is issued, and can execute the task cancellation operation without considering the subtask information after splitting. While simplifying the cancellation operation process, it achieves the technical effect of satisfying the user application experience.

[0109] Figure 7 A structural diagram of a task processing device provided by an embodiment of the present invention is shown in FIG. Figure 7 As shown, the device includes: a task belonging party determination module 410, a task splitting module 420 and a task sending module 430.

[0110] Among them, the task owner determination module 410 is used to determine the task owner to which the task to be processed belongs when the received task to be processed includes at least two sub-tasks to be split; the task splitting module 420 is used to determine the target splitting configuration data corresponding to the task owner, and process the at least two sub-tasks to be split according to the target splitting configuration data to obtain at least one sub-task to be processed; the task sending module 430 is used to configure processing attributes for the at least one sub-task to be processed, and send the sub-task to be processed and the corresponding processing attributes to the target platform, so as to process the sub-task to be processed based on the user corresponding to the target platform.

[0111] On the basis of the above device, the device further comprises a verification module, which comprises a parameter verification unit and a to-be-processed task determination unit.

[0112] A parameter checking unit, configured to check the overall parameters of each subtask to be split in the original task upon receiving the original task; the overall parameters include the parameters of the goods to be dispatched and the service parameters of each subtask to be split;

[0113] The to-be-processed task determining unit is configured to determine that the original task is the to-be-processed task if the verification result is consistent with a preset verification result.

[0114] On the basis of the above device, the to-be-selected split configuration data corresponding to the task to-be-selected party includes a plurality of split configuration data, and the task splitting module 420 is specifically used to determine the target split configuration data according to the priority corresponding to each of the to-be-selected split configuration data; or,

[0115] Determining the target split configuration data from the split configuration data to be selected according to the target sender corresponding to the task to be processed; or,

[0116] The target splitting configuration data is determined from the splitting configuration data to be selected according to the specification parameters corresponding to each to-be-split subtask in the to-be-processed task.

[0117] Based on the above device, the processing attribute includes a processing timeliness attribute, and the task sending module 430 is further used to configure the processing timeliness attribute for the corresponding subtask to be processed according to the parameters of the items to be distributed in each subtask to be processed.

[0118] Based on the above device, the task sending module 430 includes a task generating unit to be delivered and a task sending unit.

[0119] A to-be-delivered task generating unit, used to generate a to-be-delivered task corresponding to the to-be-processed subtask;

[0120] The task sending unit is used to send the delivery identifier of the task to be delivered and the subtask to be processed to the target platform.

[0121] Based on the above device, the device further includes a task cancellation module, which includes a task identification determination unit and a task cancellation unit.

[0122] A task identifier determining unit, configured to obtain the task identifier carried in the task cancellation instruction upon receiving the task cancellation instruction;

[0123] The task canceling unit is configured to process the task to be canceled based on a target data processing method if the task to be canceled corresponding to the task identifier includes at least two subtasks to be split.

[0124] Based on the above device, the task cancellation unit includes a first feedback subunit and a second feedback subunit.

[0125] A first feedback sub-unit is used to feed back cancellation failure feedback information to the task owner corresponding to the task to be cancelled when the sub-task to be split has been processed in the target platform;

[0126] The second feedback sub-unit is used to feed back cancellation success feedback information to the task owner corresponding to the task to be cancelled when the sub-task to be split has not been processed in the target platform or the target platform has not received the sub-task to be split.

[0127] Based on the above-mentioned device, the device also includes: a status update module, which is used to update the task status of at least two sub-tasks to be split in the task to be canceled when the cancellation of at least two sub-tasks to be split is completed, so as to determine the processing progress of the sub-tasks to be split based on the task status.

[0128] Based on the above device, the subtasks to be split include at least one of delivery location information and task specification information.

[0129] The technical solution of the embodiment of the present invention is to determine the task owner to which the task to be processed belongs when the received task to be processed includes at least two subtasks to be split; determine the target splitting configuration data corresponding to the task owner, and process at least two subtasks to be split according to the target splitting configuration data to obtain at least one subtask to be processed; configure processing attributes for at least one subtask to be processed, and send the subtask to be processed and the corresponding processing attributes to the target platform, so as to process the subtask to be processed based on the user corresponding to the target platform. The technical solution of the embodiment of the present invention solves the problem that only the task owner can pre-process the task in the prior art, while the logistics party cannot pre-process the task, resulting in difficulty in task processing, and realizes that when receiving the task to be processed including at least two subtasks to be split, the target splitting configuration data matching the task owner to which the task to be processed belongs is retrieved to split the at least two subtasks to be split, so that not only the split subtasks to be processed meet the splitting requirements of the task owner, but also the task processing efficiency and distribution efficiency are improved by performing task processing on each subtask to be processed. At the same time, by configuring a processing attribute for at least one subtask to be processed, the subtask to be processed is processed based on the processing attribute, thereby achieving a technical effect of improving user experience while improving task processing effect.

[0130] The task processing device provided in the embodiment of the present invention can execute the task processing method provided in any embodiment of the present invention, and has the corresponding functional modules and beneficial effects of the execution method.

[0131] It is worth noting that the various units and modules included in the above system are only divided according to functional logic, but are not limited to the above division, as long as the corresponding functions can be achieved; in addition, the specific names of the functional units are only for the convenience of distinguishing each other, and are not used to limit the protection scope of the embodiments of the present invention.

[0132] Figure 8 The present invention is a schematic diagram of the structure of an electronic device provided by an embodiment of the present invention. Figure 8 A block diagram of an exemplary electronic device 50 suitable for implementing exemplary embodiments of the present invention is shown. Figure 8 The electronic device 50 shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present invention.

[0133] like Figure 8 As shown, the electronic device 50 is in the form of a general computing device. The components of the electronic device 50 may include but are not limited to: one or more processors or processing units 501, a system memory 502, and a bus 503 connecting different system components (including the system memory 502 and the processing unit 501).

[0134] Bus 503 represents one or more of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, a processor or a local bus using any of a variety of bus structures. For example, these architectures include but are not limited to Industry Standard Architecture (ISA) bus, Micro Channel Architecture (MAC) bus, Enhanced ISA bus, Video Electronics Standards Association (VESA) local bus and Peripheral Component Interconnect (PCI) bus.

[0135] The electronic device 50 typically includes a variety of computer system readable media. These media can be any available media that can be accessed by the electronic device 50, including volatile and non-volatile media, removable and non-removable media.

[0136] System memory 502 may include computer system readable media in the form of volatile memory, such as random access memory (RAM) 504 and / or cache memory 505. Electronic device 50 may further include other removable / non-removable, volatile / non-volatile computer system storage media. By way of example only, storage system 506 may be used to read and write non-removable, non-volatile magnetic media ( Figure 8not shown, usually called a "hard drive"). Although Figure 8 Not shown in the figure, a disk drive for reading and writing to a removable non-volatile disk (e.g., a "floppy disk"), and an optical disk drive for reading and writing to a removable non-volatile optical disk (e.g., a CD-ROM, a DVD-ROM, or other optical media) may be provided. In these cases, each drive may be connected to the bus 503 via one or more data medium interfaces. The memory 502 may include at least one program product having a set (e.g., at least one) of program modules that are configured to perform the functions of the embodiments of the present invention.

[0137] A program / utility 508 having a set (at least one) of program modules 507 may be stored, for example, in the memory 502, such program modules 507 including but not limited to an operating system, one or more application programs, other program modules, and program data, each of which or some combination may include an implementation of a network environment. The program modules 507 generally perform the functions and / or methods of the embodiments described herein.

[0138] The electronic device 50 may also communicate with one or more external devices 509 (e.g., keyboards, pointing devices, displays 810, etc.), may communicate with one or more devices that enable a user to interact with the electronic device 50, and / or may communicate with any device that enables the electronic device 50 to communicate with one or more other computing devices (e.g., a network card, a modem, etc.). Such communication may be performed through an input / output (I / O) interface 511. Furthermore, the electronic device 50 may also communicate with one or more networks (e.g., a local area network (LAN), a wide area network (WAN), and / or a public network, such as the Internet) through a network adapter 512. As shown, the network adapter 512 communicates with other modules of the electronic device 50 through the bus 503. It should be understood that although Figure 8 Not shown, other hardware and / or software modules may be used in conjunction with the electronic device 50, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems.

[0139] The processing unit 501 executes various functional applications and data processing by running the programs stored in the system memory 502, such as implementing the task processing method provided in the embodiment of the present invention.

[0140] An embodiment of the present invention further provides a storage medium containing computer executable instructions, and when the computer executable instructions are executed by a computer processor, they are used to perform a task processing method, the method comprising:

[0141] When the received task to be processed includes at least two subtasks to be split, determining the task owner to which the task to be processed belongs;

[0142] Determine the target splitting configuration data corresponding to the task owner, and process the at least two to-be-split subtasks according to the target splitting configuration data to obtain at least one to-be-processed subtask;

[0143] A processing attribute is configured for the at least one to-be-processed subtask, and the to-be-processed subtask and the corresponding processing attribute are sent to a target platform, so that the to-be-processed subtask is processed based on a user corresponding to the target platform.

[0144] The computer storage medium of the embodiment of the present invention can adopt any combination of one or more computer-readable media. The computer-readable medium can be a computer-readable signal medium or a computer-readable storage medium. The computer-readable storage medium can be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples (non-exhaustive list) of computer-readable storage media include: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In this document, a computer-readable storage medium can be any tangible medium containing or storing a program, which can be used by an instruction execution system, device or device or used in combination with it.

[0145] Computer-readable signal media may include data signals propagated in baseband or as part of a carrier wave, which carry computer-readable program code. Such propagated data signals may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. Computer-readable signal media may also be any computer-readable medium other than a computer-readable storage medium, which may send, propagate, or transmit a program for use by or in conjunction with an instruction execution system, apparatus, or device.

[0146] Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

[0147] Computer program code for performing the operation of embodiments of the present invention may be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages, such as Java, Smalltalk, C++, and conventional procedural programming languages, such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as an independent software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer via any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0148] Note that the above are only preferred embodiments of the present invention and the technical principles used. Those skilled in the art will understand that the present invention is not limited to the specific embodiments herein, and that various obvious changes, readjustments and substitutions can be made by those skilled in the art without departing from the scope of protection of the present invention. Therefore, although the present invention has been described in more detail through the above embodiments, the present invention is not limited to the above embodiments, and may include more other equivalent embodiments without departing from the concept of the present invention, and the scope of the present invention is determined by the scope of the appended claims.

Claims

1. A task processing method, characterized in that: include: When the received task to be processed includes at least two subtasks to be split, determining the task owner to which the task to be processed belongs; Determine the target splitting configuration data corresponding to the task owner, and process the at least two to-be-split subtasks according to the target splitting configuration data to obtain at least one to-be-processed subtask; A processing attribute is configured for the at least one to-be-processed subtask, and the to-be-processed subtask and the corresponding processing attribute are sent to a target platform, so that the to-be-processed subtask is processed based on a user corresponding to the target platform.

2. The method according to claim 1, characterized in that Also includes: When receiving the original task, performing an overall parameter check on each subtask to be split in the original task; The overall parameters include the parameters of the items to be delivered and the service parameters of each of the subtasks to be split; If the verification result is consistent with the preset verification result, the original task is determined to be the task to be processed.

3. The method according to claim 1, characterized in that The to-be-selected split configuration data corresponding to the task belonging party includes a plurality of data, and the determining of the target split configuration data corresponding to the task belonging party includes: Determine the target split configuration data according to the priorities corresponding to the split configuration data to be selected; or, Determining the target split configuration data from the split configuration data to be selected according to the target sender corresponding to the task to be processed; or, The target splitting configuration data is determined from the splitting configuration data to be selected according to the specification parameters corresponding to each to-be-split subtask in the to-be-processed task.

4. The method according to claim 1, characterized in that: The processing attribute includes a processing timeliness attribute, and the configuring the processing attribute for the at least one to-be-processed subtask includes: According to the parameters of the items to be dispatched in each of the subtasks to be processed, a processing timeliness attribute is configured for the corresponding subtask to be processed.

5. The method according to claim 1, characterized in that The sending the to-be-processed subtask and the corresponding processing attributes to the target platform includes: Generate a to-be-delivered task corresponding to the to-be-processed subtask; The delivery identifier of the task to be delivered and the subtask to be processed are sent to the target platform.

6. The method according to claim 1, characterized in that Also includes: When receiving a task cancellation instruction, obtaining the task identifier carried in the task cancellation instruction; If the task to be canceled corresponding to the task identifier includes at least two subtasks to be split, the task to be canceled is processed based on the target data processing method.

7. The method according to claim 6, characterized in that The processing of the task to be cancelled based on the target data processing method includes: When the subtask to be split has been processed in the target platform, feedback information of cancellation failure is fed back to the task owner corresponding to the task to be canceled; When the subtask to be split has not been processed in the target platform or the target platform has not received the subtask to be split, feedback information of successful cancellation is fed back to the task owner corresponding to the task to be canceled.

8. The method according to claim 6, characterized in that Also includes: When cancellation of at least two to-be-split subtasks in the to-be-cancelled task is completed, the task statuses of the at least two to-be-split subtasks are updated to determine the processing progress of the to-be-split subtasks based on the task statuses.

9. The method according to any one of claims 1 to 8, characterized in that: The subtasks to be split include at least one of delivery location information and task specification information.

10. A task processing device, characterized in that: include: A task owner determination module, used to determine the task owner to which the task to be processed belongs when the received task to be processed includes at least two subtasks to be split; A task splitting module, used to determine the target splitting configuration data corresponding to the task owner, and process the at least two to-be-split subtasks according to the target splitting configuration data to obtain at least one to-be-processed subtask; The task sending module is used to configure processing attributes for the at least one to-be-processed subtask, and send the to-be-processed subtask and the corresponding processing attributes to the target platform, so as to process the to-be-processed subtask based on the user corresponding to the target platform.

11. An electronic device, characterized in that: The electronic device comprises: one or more processors; a storage device for storing one or more programs, When the one or more programs are executed by the one or more processors, the one or more processors implement the task processing method according to any one of claims 1 to 9.

12. A storage medium comprising computer executable instructions, wherein the computer executable instructions are used to perform the task processing method according to any one of claims 1 to 9 when executed by a computer processor.

Images