Task processing method and device, electronic equipment, storage medium and program product

Abstract

The application discloses a task processing method and device, electronic equipment, storage medium and program product. The method comprises the following steps: receiving a first task meeting a task merging condition, screening a second task similar to the first task in a task pool; the task pool contains tasks meeting the task merging condition generated before the first task; in the case of screening the second task, performing single processing on the first task and the second task according to the task state of the first task and the task state of the second task; and pushing a single generation notification generated by the single to a placing user of the first task and a placing user of the second task respectively, so as to match different tasks into a single, reduce the task failure condition, improve the task processing efficiency, and promote the logistics single reduction.

Description

Technical Field

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

[0002] Currently, most of the products offered by e-commerce platforms are created after the platform receives an order request from a user for a specific product. The platform then creates a task for the user and sends the task information to the user who initiated the request. The user then forwards the task to their friends to help complete the order, and the platform waits to receive order participation requests from other users for that task.

[0003] However, this task processing method often involves a large number of tasks being initiated. Because some users cannot find friends to complete the order, the e-commerce platform cannot receive other users' order requests, and the tasks fail due to timeouts, resulting in low task processing efficiency for the e-commerce platform. Summary of the Invention

[0004] The purpose of this application is to provide a task processing method, apparatus, electronic device, storage medium, and program product that addresses the shortcomings of the prior art. This purpose is achieved through the following technical solutions.

[0005] A first aspect of this application proposes a task processing method, the method comprising:

[0006] Receive a first task that meets the task merging criteria, and filter a second task similar to the first task from the task pool; the task pool includes tasks that meet the task merging criteria that were generated before the first task.

[0007] If a second task is selected, the first task and the second task are combined into one task based on the task status of the first task and the task status of the second task.

[0008] The order completion notification generated by the combined order will be pushed to the user who placed the order for the first task and the user who placed the order for the second task, respectively.

[0009] In some embodiments, receiving a first task that meets the task merging conditions includes:

[0010] Receive a main state order generated by the main state payment, wherein the main state payment is a task initiated by the user to pay for the order;

[0011] Based on the preset delivery rules and the user's selected processing intention carried by the main status order, determine whether the main status order meets the task merging conditions;

[0012] If the conditions for task merging are met, the main state unit will be designated as the first task.

[0013] In some embodiments, determining whether the main order meets the task merging conditions based on preset delivery rules and the user's selected processing intention carried by the main order includes:

[0014] If the region to which the main order belongs is a delivery region in the preset delivery rules and the processing intention is to agree to merge tasks, a timer is set for the main order according to the region to which it belongs, and the timer starts counting down; the timeout period of the timer is the merging delay time corresponding to the region to which it belongs in the preset delivery rules;

[0015] If the timer times out and the task status of the main state unit is in progress, it is determined that the main state unit meets the task merging condition;

[0016] If the area to which the main order belongs does not belong to the delivery area in the preset delivery rules, or the processing intention is to disagree with the task merging, or the task status of the main order is a successful order after the timer expires, then the main order is determined to not meet the task merging conditions.

[0017] In some embodiments, receiving a first task that meets the task merging conditions includes:

[0018] Receive customer-state payment orders generated by customer-state payments, where the customer-state payment is made by the user participating in a task to pay for the order;

[0019] If the task in which the customer-state order participates is a virtual task and the customer-state order is the first order of the virtual task, then obtain the order completion conditions of the virtual task; the virtual task refers to a task initiated by the system.

[0020] If the order completion condition is a multi-person order and the area to which the customer-state order belongs belongs to the delivery area in the preset delivery rules, the customer-state order will be regarded as the first task that meets the task merging condition.

[0021] In some embodiments, filtering a second task similar to the first task from the task pool includes:

[0022] Determine the user distance and merchant distance between the first task and each task in the task pool;

[0023] Based on the user distance and / or the merchant distance, a second task similar to the first task is selected from the task pool.

[0024] In some embodiments, the step of merging the first task and the second task based on the task status of the first task and the task status of the second task includes:

[0025] If the second task includes an order, and the task status of the first task is in progress and the task status of the second task is in progress, the first task and the second task are merged to obtain an order completion notification.

[0026] If the second task includes two or more orders, the tasks in the second task that are in progress will be merged with the first task to obtain a completion notification.

[0027] Remove the second task from the task pool.

[0028] In some embodiments, after filtering a second task similar to the first task from the task pool, the method further includes:

[0029] If no second task is found, the first task is added to the task pool.

[0030] If the first task is of the "no-combination" type, the order placement time corresponding to the region to which the first task belongs is obtained from the preset delivery rules;

[0031] Set a timer for the first task and start timing. The timeout period of the timer is the order pressing time.

[0032] If the timer expires and the task status of the first task is still in progress, the first task is deleted from the task pool, and a completion notification is generated for the first task to be pushed to the user who placed the order.

[0033] A second aspect of this application proposes a task processing method applied to a client, the method comprising:

[0034] The server sends an order payment message for the first task to the server so that the server can merge the first task and the second task in the task pool according to the first task meeting the task merging conditions; wherein, the task pool includes tasks that meet the task merging conditions that were generated before the first task, and the second task is a task in the task pool that is similar to the first task.

[0035] Receive the order completion notification returned by the server.

[0036] In some embodiments, sending the order payment message for the first task to the server includes:

[0037] Based on the order type initiated by the user for the first task, display the order payment page corresponding to the order type, which includes either a primary order or a secondary order.

[0038] Upon receiving an order submission request triggered by a user on the order payment page, the system sends the first task's order payment message to the server.

[0039] A third aspect of this application provides a task processing apparatus for use on a server, the apparatus comprising:

[0040] The receiving module is used to receive the first task that meets the task merging conditions;

[0041] A filtering module is used to filter second tasks that are similar to the first task from a task pool; the task pool includes tasks that meet the task merging conditions and were generated before the first task.

[0042] The merging module is used to merge the first task and the second task into one order when the second task is selected.

[0043] The order push module is used to push the order completion notification generated by the combined order to the order placement user of the first task and the order placement user of the second task, respectively.

[0044] A fourth aspect of this application provides a task processing apparatus for use on a client, the apparatus comprising:

[0045] The sending module is used to send an order payment message for the first task to the server, so that the server can merge the first task and the second task in the task pool according to the first task meeting the task merging conditions; wherein, the task pool includes tasks that meet the task merging conditions that were generated before the first task, and the second task is a task in the task pool that is similar to the first task.

[0046] The receiving module is used to receive the order completion notification returned by the server.

[0047] The fifth aspect of this application provides an electronic device including a memory, a processor, and a computer program stored in the memory and executable on the processor, the processor executing the program to implement the method as described in the first or second aspect above.

[0048] The sixth aspect of this application provides a computer-readable storage medium having a computer program stored thereon, the program being executed by a processor to implement the method as described in the first or second aspect above.

[0049] An embodiment of the seventh aspect of this application provides a computer program product including a computer program that is executed by a processor to implement the method described in the first or second aspect above.

[0050] Based on the task processing method, apparatus, electronic device, storage medium, and program product described above, this application has at least the following beneficial effects or advantages:

[0051] Upon receiving a first task that meets the task merging criteria, a second task similar to the first task is selected from the task pool. Based on the task status of both tasks, the first and second tasks are merged. A notification of the merged task is then pushed to the user who placed the order. This process combines different tasks into a single order, reducing task failures and improving processing efficiency. Furthermore, because a second task similar to the first task is used for merging, although the first and second tasks are different, they share certain similarities, such as proximity of users or similar merchant locations. This can effectively aggregate logistics orders and reduce merging costs.

[0052] The above description is only an overview of the technical solution of this application. In order to better understand the technical means of this application, it can be implemented according to the contents of the specification. In order to make the above and other objects, features and advantages of this application more obvious and understandable, specific embodiments of this application are given below. Attached Figure Description

[0053] The accompanying drawings, which are included to provide a further understanding of this application and form part of this application, illustrate exemplary embodiments and are used to explain this application, but do not constitute an undue limitation of this application. In the drawings:

[0054] Figure 1 This is an architecture diagram of a task processing system according to an exemplary embodiment;

[0055] Figure 2 This is an architectural diagram of another task processing system according to an exemplary embodiment;

[0056] Figure 3 This is a flowchart illustrating an embodiment of a task processing method according to an exemplary embodiment;

[0057] Figure 4 This is a schematic diagram of an order payment page according to an exemplary embodiment;

[0058] Figure 5 This is a schematic diagram of a state machine for task processing according to an exemplary embodiment;

[0059] Figure 6 This is a timing diagram of the main state single-processing in a task processing method according to an exemplary embodiment;

[0060] Figure 7 This is a processing timing diagram of a client-side task in a task processing method according to an exemplary embodiment;

[0061] Figure 8 This is a schematic diagram illustrating the structure of a task processing apparatus according to an exemplary embodiment;

[0062] Figure 9 This is a schematic diagram of the hardware structure of an electronic device according to an exemplary embodiment;

[0063] Figure 10 This is a schematic diagram illustrating the structure of a storage medium according to an exemplary embodiment. Detailed Implementation

[0064] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of systems and methods consistent with some aspects of this application as detailed in the appended claims.

[0065] The terminology used in this application is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. The singular forms “a,” “the,” and “the” used in this application and the appended claims are also intended to include the plural forms unless the context clearly indicates otherwise. It should also be understood that the term “and / or” as used herein refers to and includes any or all possible combinations of one or more of the associated listed items.

[0066] It should be understood that although the terms first, second, third, etc., may be used in this application to describe various information, such information should not be limited to these terms. These terms are only used to distinguish information of the same type from one another. For example, without departing from the scope of this application, first information may also be referred to as second information, and similarly, second information may also be referred to as first information. Depending on the context, the word "if" as used herein may be interpreted as "when," "when," or "in response to determination."

[0067] Furthermore, it should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties. Moreover, the collection, use and processing of the relevant data must comply with the relevant laws, regulations and standards of the relevant countries and regions, and corresponding operation portals are provided for users to choose to authorize or refuse.

[0068] As mentioned earlier, the various products currently offered by e-commerce platforms are created by users initiating tasks and sharing them with their friends so that they can participate in the tasks. Users can also participate in other people's tasks in order to complete a sale.

[0069] However, this task processing method often results in task failure or incomplete tasks due to the inability to find matching friends, making the task processing efficiency relatively low.

[0070] Based on this, to improve task processing efficiency, this application proposes a task processing method. Upon receiving a first task that meets the task merging conditions, a second task similar to the first task is selected from the task pool. Based on the task status of the first and second tasks, the first and second tasks are merged. Then, a notification of the merged task is pushed to the ordering user. This allows the system to intelligently schedule and combine different tasks into a single order, reducing task failures and improving processing efficiency. Furthermore, since a second task similar to the first task is used for merging, although the first and second tasks are different, they share certain similarities, such as proximity of users or the same user, proximity of merchants or the same merchant. This can, to some extent, facilitate logistics order aggregation and reduce merging costs.

[0071] The technical solution of this application and how it solves the aforementioned technical problems are described in detail below with specific embodiments. The listed specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments. The embodiments of this application will be described in detail below with reference to the accompanying drawings.

[0072] See Figure 1 , Figure 1 This specification illustrates an architecture diagram of a task processing system according to an embodiment of the present specification. The speech recognition system may include a client 100 and a server 200.

[0073] Client 100 is used to send the order payment message for the first task to server 200;

[0074] Server 200 is used to filter a second task similar to the first task from the task pool based on the first task meeting the task merging conditions; the task pool includes tasks that meet the task merging conditions that were generated before the first task; when a second task is selected, the first task and the second task are merged according to the task status of the first task and the task status of the second task.

[0075] Client 100 is also used to receive order completion notifications sent by server 200.

[0076] The solution implemented in this specification involves obtaining a first task that meets the task merging conditions, filtering a second task similar to the first task from the task pool, and merging the first and second tasks according to their respective task statuses. A notification of the merged task is then pushed to the user who placed the order. This intelligent scheduling by the system combines different tasks into a single order, reducing task failures and improving task processing efficiency. Furthermore, since a second task similar to the first task is used for merging, although the first and second tasks are different, they share certain similarities, such as proximity of users or similar user / merchant location. This can, to some extent, facilitate logistics order aggregation and reduce merging costs.

[0077] See Figure 2 , Figure 2 This specification illustrates an architecture diagram of another task processing system provided in one embodiment. The speech recognition system may include multiple clients 100 and a server 200, wherein the clients 100 may be edge devices, and the server 200 may be cloud devices. Multiple clients 100 can establish communication connections through the server 200. In a group-buying scenario, the server 200 is used to provide group-buying services among the multiple clients 100. Each client 100 can act as a sender or receiver, communicating through the server 200.

[0078] Users can interact with server 200 through client 100 to receive data sent by other clients 100, or send data to other clients 100, etc. In a group-buying order scenario, users can publish order payment data streams to server 200 through client 100. Server 200 generates order completion notifications based on the order payment data streams and pushes the order completion notifications to other clients that have established communication connections with server 200, such as merchant clients.

[0079] In this system, client 100 and server 200 establish a connection via a network. The network provides the medium for communication between client 100 and server 200. The network can include various connection types, such as wired or wireless communication links or fiber optic cables. Data transmitted by client 100 may need to undergo encoding, transcoding, compression, or other processing before being published to server 200.

[0080] Client 100 can be a browser, an app (application), a web application such as an H5 (HyperText Markup Language 5) application, a lightweight application (also known as a mini-program), or a cloud application. Client 100 can be developed based on the software development kit (SDK) of the corresponding service provided by server 200, such as a real-time communication (RTC) SDK. Client 100 can be deployed on electronic devices and depends on the device or certain apps on the device to run. Electronic devices may have displays and support information browsing, such as personal mobile terminals like mobile phones, tablets, and personal computers. Various other types of applications can also be configured on electronic devices, such as human-computer interaction applications, model training applications, text processing applications, web browser applications, shopping applications, search applications, instant messaging tools, email clients, and social media platform software.

[0081] Server 200 may include servers providing various services, such as servers providing communication services to multiple clients, servers supporting backend training of models used on clients, and servers processing data sent by clients. It should be noted that server 200 can be implemented as a distributed server cluster composed of multiple servers, or as a single server. The server can also be a server in a distributed system, or a server integrated with blockchain. The server can also be a cloud server providing basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, content delivery networks (CDNs), and big data and artificial intelligence platforms, or an intelligent cloud computing server or intelligent cloud host with artificial intelligence technology.

[0082] It is worth noting that the task processing methods provided in the embodiments of this specification are generally executed by the server. However, in other embodiments of this specification, the client may also have similar functions to the server, thereby executing the task processing methods provided in the embodiments of this specification. In other embodiments, the task processing methods provided in the embodiments of this specification may also be executed jointly by the client and the server.

[0083] Figure 3 This is a flowchart illustrating an embodiment of a task processing method according to an exemplary embodiment, such as... Figure 3 As shown, it includes the following steps 301-303:

[0084] Step 301: Receive the first task that meets the task merging conditions, and filter the second task that is similar to the first task in the task pool. The task pool contains the generated tasks that meet the task merging conditions.

[0085] Step 302: If a second task is found, combine the first task and the second task into one order based on the task status of the first task and the task status of the second task.

[0086] Step 303: Push the order completion notification generated by the combined order to the user who placed the order in the first task and the user who placed the order in the second task, respectively.

[0087] This embodiment is applied to applications, websites, or mini-programs with task processing functions. By deploying order merging logic on the application, website, or mini-program, different tasks are matched into orders through intelligent scheduling by the system.

[0088] The task merging condition can be understood as the condition that needs to be met to execute the merging logic. This task merging condition represents the trigger condition for executing the merging logic. By using this task merging condition, a buffer opportunity can be provided for the first task to be processed in the traditional task processing method, avoiding the immediate execution of the merging logic for the currently generated task.

[0089] The task pool can be understood as a collection of tasks that can participate in the merging logic. All tasks recorded in the task pool were generated before the first task and meet the task merging conditions. The data representation of tasks recorded in the task pool can adopt a key-value structure, for example, the key includes merchant identifier, task identifier, user identifier, etc.

[0090] Both the first and second tasks are user-triggered order tasks. It is important to note that while the first and second tasks are different tasks, they share similar characteristics, such as the users being close to each other or the users being the same, or the merchants being close to each other or the merchants being the same.

[0091] Task status can be understood as the current state of a task. This status can include in progress, order completion, timeout, and order completion. In progress means that the task is still in progress. Order completion means that the task is generating an order completion notification. Order completion means that an order completion notification has been pushed to the user who placed the order. Order completion is complete. Timeout means that the task has expired.

[0092] Order completion notifications can be used to instruct order users that their paid orders have been successfully completed.

[0093] For example, suppose a task A that meets the task merging conditions is received. A task B that is similar to task A is filtered out from the task pool. Based on the task status of task A and task B, task A and task B are merged. Then, the order completion notification generated by the merged order is pushed to user A of task A and user B of task B respectively.

[0094] This completes the above. Figure 3 The task processing flow shown involves receiving a first task that meets the task merging criteria. It then filters a second task similar to the first task from the task pool. Based on the task status of both tasks, the first and second tasks are merged. A notification of the merged task is then pushed to the user who placed the order. This intelligent system scheduling combines different tasks into a single order, reducing task failures and improving processing efficiency. Furthermore, because a second task similar to the first task is used for merging, although the first and second tasks are different, they share certain similarities, such as proximity of users or similar merchant locations. This can effectively aggregate logistics orders and reduce merging costs.

[0095] In one optional embodiment of this application, receiving the first task that meets the task merging conditions in step 301 above includes the following specific steps:

[0096] Receive the main state payment order generated by the main state payment, which is a task initiated by the user to pay for the order.

[0097] Based on the preset delivery rules and the user's selected processing intention carried by the main status order, determine whether the main status order meets the task merging conditions;

[0098] If the conditions for merging tasks are met, the primary state single will be designated as the first task.

[0099] A master order can be understood as an order generated by a user-initiated task. When a master order is generated, a task is started for the master order and the task is initialized to generate task parameters. These task parameters may include, but are not limited to, task identifier, initiation time, validity period, user information, product information, and task type.

[0100] The delivery rules can be understood as the conditions that must be met for the merging logic to be applied. These rules are typically generated by operations personnel in the backend based on their needs. These rules may include, but are not limited to, delivery regions, merging delay times, no-merging types, and order retention times. Specifically, the delivery region indicates which regions will receive the merging logic; the merging delay time indicates how long after a task is generated it will the merging logic be triggered (i.e., the earliest merging time); no-merging types indicate which no-merging types of tasks will not be automatically generated immediately, but will wait until the order retention time has elapsed before automatically generating orders if the merging fails; and the order retention time indicates the maximum time that no-merging types of tasks will remain in the task pool.

[0101] Processing intention can be understood as the choice made by the user, according to their own wishes, whether or not to agree to the task merging when placing an order and making payment.

[0102] For example, such as Figure 4 As shown, on the order payment page of the main order, if the user selects the option "Sync to nearby tasks for faster order completion," the main order indicates that the user agrees to the task merging process; if the user does not select the option, the main order indicates that the user does not agree to the task merging process.

[0103] In this embodiment, for the main payment order, the system determines whether the main payment order can participate in task merging by combining the delivery rules and the user's processing intention, which satisfies both the needs of the operators and the wishes of the users.

[0104] In one optional embodiment of this application, based on preset delivery rules and the user's selected processing intention carried by the main status message, it is determined whether the main status message meets the task merging conditions, specifically including:

[0105] If the main order belongs to a region that falls within the preset delivery rules and the processing intention is to merge the tasks, a timer is set based on the region to which the main order belongs, and the timer starts counting down. The timeout period of this timer is the merging delay time corresponding to the region in the preset delivery rules.

[0106] If the timer times out and the task status of the main state unit is in progress, it is determined that the main state unit meets the task merging condition;

[0107] If the area to which the main order belongs is not a delivery area in the preset delivery rules, or the processing intention is to disagree with task merging, or the task status of the main order is successfully completed after the timer expires, then the main order is determined not to meet the task merging conditions.

[0108] The region to which the main order belongs can be understood as the location of the user who placed the order, and the region granularity can be a city. For example, assuming that the delivery region configured in the delivery rule includes city A, city B, and city C, if the user who placed the order is located in city C, then the main order has hit the delivery rule.

[0109] The timer can be understood as a delayed scheduling task created based on the merge delay time. It provides a waiting time for the main task group to complete the task processing in the traditional way. For example, in the traditional way, the user who placed the order (i.e., the initiating user) shares the task they initiated with friends. In other words, if the task status of the main task is still in progress after the timer expires, the merge logic is executed on the main task to merge it with other tasks. In the delivery rules, different delivery regions can be configured with different merge delay times according to actual needs, but the merge delay time will not exceed the validity period set for the task.

[0110] For example, assuming the merging delay time for city A is configured to be 180 seconds and the merging delay time for city B is configured to be 30 seconds in the delivery rules, if the user who placed the order for the main order is located in city B, then when setting the timer for the main order, the timeout time is set to 30 seconds.

[0111] In this embodiment, if the main order meets the delivery area requirements configured in the delivery rules and the user's processing intention is to agree to the task merging, a timer is further created for the main order and the timer starts counting. The main order is considered to meet the task merging conditions only if the main order has not been completed after the timer expires. This provides a waiting time for the task initiated by the main order to be completed using the traditional method, ensuring the normal operation of the traditional method.

[0112] In one optional embodiment of this application, receiving the first task that meets the task merging conditions in step 301 above includes the following specific steps:

[0113] Receive customer-state payment orders generated by customer-state payments, where the customer-state payment is made by the user participating in a task.

[0114] If the objective order participates in a virtual task and is the first order of the virtual task, obtain the completion conditions of the virtual task; a virtual task refers to a task initiated by the system.

[0115] If the order completion condition is that there are multiple orders and the customer-state order belongs to the delivery area in the preset delivery rules, the customer-state order will be regarded as the first task that meets the task merging condition.

[0116] A customer-state order can be understood as an order generated by a user participating in a virtual task. When a customer-state order is generated, its relevant parameters can be recorded, including but not limited to the task identifier and participation time.

[0117] Virtual tasks are system-initiated tasks. The difference between virtual and user-initiated tasks is that the trigger for a virtual task is not a real user, but rather the system automatically triggers it. Therefore, for system-initiated virtual tasks, there are no real users during task initialization, while for user-initiated tasks, there are real users during initialization. It's important to note that since the user who placed the order for a virtual task is not the initiating user, this user cannot share the task.

[0118] The completion condition can be understood as the number of participants required for the completion of a virtual task as defined when the system initiates the task. For example, the completion condition can include multi-person tasks and two-person tasks. That is, for a two-person virtual task, as long as one real user participates, the task can be completed, and there is no need to use the merging logic to complete the task. For a multi-person virtual task, at least two real users need to participate to complete the task. In addition to waiting for real users to participate, the merging logic can also be used to complete the task.

[0119] In this embodiment, if the task in which the customer-state order participates is a virtual task and the customer-state order is the first order of the virtual task, by obtaining the order completion conditions of the virtual task, when the order completion conditions are multiple orders and the region to which the customer-state order belongs meets the requirements of the delivery region configured in the delivery rules, the customer-state order can be used as the first task that meets the task merging conditions. This not only enriches the source of tasks for merging, but also improves the processing efficiency of virtual tasks.

[0120] It should be noted that, in addition to the methods for determining whether a task meets the conditions for merging, any type of task that is not yet full can also be considered to meet the conditions for merging, that is, any task whose status is in progress can be considered to meet the conditions for merging.

[0121] In one optional embodiment of this application, step 301 above, which involves filtering a second task similar to the first task from the task pool, includes the following specific steps:

[0122] Determine the user distance and merchant distance between the first task and each task in the task pool;

[0123] Based on user distance and / or merchant distance, select a second task from the task pool that is similar to the first task.

[0124] User distance can be understood as the distance between the locations of the users who placed orders for two tasks. It represents the distance between the destinations of the two tasks. If the user distance is zero, it means that the destinations of the two tasks are the same.

[0125] Merchant distance can be understood as the distance between the locations of merchants in two tasks. It represents the distance between the starting points of the two tasks. If the merchant distance is zero, it means that the starting points of the two tasks are the same, that is, the merchants are the same.

[0126] The filtering methods for selecting second tasks similar to the first task from the task pool based on user distance and / or merchant distance can include the following:

[0127] The first screening method is "same pick-up, different delivery", which means selecting tasks from the task pool that are zero distance from the merchants as the second task similar to the first task;

[0128] The second filtering method is "same pick-up and nearby delivery", which means filtering tasks in the task pool where the user is within a preset distance, and then filtering tasks where the merchant is zero distance from the selected tasks as the second task similar to the first task.

[0129] The third filtering method is to select different tasks and send them to the same task, that is, to select tasks in the task pool that are zero distance from users as the second task that is similar to the first task.

[0130] The fourth filtering method is "nearby pickup and delivery", which means filtering tasks from the task pool where the merchant is within a preset distance, and then filtering tasks from the selected tasks where the user is at zero distance as the second task similar to the first task.

[0131] The fifth filtering method is "nearby pickup, different delivery", which means selecting tasks from the task pool whose merchants are within a preset distance as the second task similar to the first task.

[0132] The above five filtering methods are merely illustrative examples. Different filtering methods can be adopted according to different strategy requirements. For example, filtering methods such as same-day pickup and delivery or nearby pickup and delivery can also be included. This application does not specifically limit the filtering method for similar tasks based on user distance and / or merchant distance.

[0133] It should be noted that the second task, which is similar to the first task, includes at least one task.

[0134] In this embodiment, by determining the user distance and merchant distance between each task in the task pool and the first task, a second task similar to the first task is selected, so as to play a role in logistics aggregation to a certain extent and reduce the merging cost.

[0135] In one optional embodiment of this application, step 302 above, which involves merging the first task and the second task based on their respective task states, specifically includes:

[0136] If the second task includes one order, and both the first and second tasks are in progress, the first and second tasks are merged to generate a completion notification. If the second task includes two or more orders, the tasks in the second task that are in progress are merged with the first task to generate a completion notification, and finally the second task is removed from the task pool.

[0137] The merging of the first and second tasks may include updating task status and establishing association relationships.

[0138] In this embodiment, merging is performed under the premise that the first task is in progress and the second task is in progress, which can avoid the conflict caused by the second task or the first task being completed during the merging logic process.

[0139] In one optional embodiment of this application, after step 301 of filtering a second task similar to the first task from the task pool, the following specific steps are further included:

[0140] If no second task is found, add the first task to the task pool;

[0141] If the first task is of the "no-combination" type, obtain the order placement time corresponding to the region of the first task from the preset placement rules;

[0142] Set a timer for the first task and start timing. The timer's timeout period is the order pressing time.

[0143] If the timer expires and the first task is still in progress, the first task will be removed from the task pool, and a completion notification will be generated for the first task to be pushed to the user who placed the order.

[0144] "No-group-buying" type can be understood as a task type where a user can complete the order without the participation of others. This type can include no-group-buying for existing customers, no-group-buying for new customers, and individual purchases. In practice, the primary order usually involves no-group-buying; therefore, if the first task is of the no-group-buying type, then the first task originates from the primary order.

[0145] The order holding time can be understood as the longest time a task of the "no-combination" type remains in the task pool. Within this time range, it can participate in the merging logic.

[0146] For example, assuming that no similar second task is found in the task pool for the first task A, and the first task A is a no-group-buying type for returning customers, the order placement time corresponding to the region to which the first task A belongs is obtained from the preset delivery rules, for example, 120 seconds. After the first task is added to the task pool, a timer is created for the first task and the timer starts counting. When the timer reaches 120 seconds, if the task status of the first task A is still in progress, it means that the first task A has not yet been matched and merged with other tasks. Therefore, the first task A is deleted from the task pool, and a completion notification is immediately generated for the first task A.

[0147] In this embodiment, if no second task is selected, the first task is added to the task pool so that it can participate in the subsequent selection process. When the first task is of the no-combination type, a timer is created for the first task and the timer starts counting down until the timer expires. Then the first task is removed from the task pool and made into a separate order. This can improve the merging rate of different tasks and also retain the function of no-combination type tasks being made into separate orders.

[0148] Based on the above Figure 3 Based on the illustrated embodiment, Figure 5 This is a schematic diagram of a state machine for task processing according to an exemplary embodiment, such as... Figure 5 As shown, timed scheduling, task pool, and system scheduling are the processing modules introduced in this application. Among them, timed scheduling refers to creating a timer for the first task and starting the timer, with the timeout period being the merging delay time; system scheduling refers to selecting similar second tasks from the task pool for merging the first task. If the merging is successful, the task enters the order completion status and an order completion notification is pushed; if the merging fails, the first task is added to the task pool.

[0149] Taking the main state payment order generated by the main state payment as the first task as an example, the state machine processing flow is introduced as follows:

[0150] When a primary payment order is generated, task initialization is performed, and the task enters an in-process state. Then, if the primary order's region belongs to the delivery region defined in the delivery rules and the user's processing intention is to agree to task merging, it enters scheduled scheduling. After the merging delay time, if the task initiated by the primary order is still in progress, it enters system scheduling to select similar second tasks from the task pool for merging. During scheduled and system scheduling, if a customer order participates in the task initiated by the primary order, it can also enter a successful order state and receive a successful order notification. However, if the validity period of the task initiated by the primary order has expired, and neither a customer order nor a successful order merging has occurred, it enters a failed order state, and the primary order can be deleted from the task pool.

[0151] Figure 6 The following is a sequence diagram illustrating the processing of a main task in a task processing method according to an exemplary embodiment. The interaction flow between the core task module, task pool, operation backend, timed scheduling, and task completion processing module is as follows:

[0152] First, when the core task module receives the main order, it reads the delivery rules from the operations backend. Based on the delivery rules and the user's selected processing intention, it verifies whether the main order can be merged. If so, it adds a merge flag to the task parameters of the main order.

[0153] Then, the task core module creates a timer for the main order through timed scheduling. The timer timeout is set to the merging delay time corresponding to the region to which the main order belongs in the delivery rules. After the timed scheduling detects that the timer has expired, it notifies the task core module. The task core module scans the task pool to filter tasks that meet the conditions for the main order. If a task that meets the conditions is found, the task parameters of the main order and the selected task are assembled, and a merging message is sent to the order processing module. If no task that meets the conditions is found, the main order is added to the task pool.

[0154] Finally, when the task core module receives the order completion notification from the order processing module, it pushes the order completion notification.

[0155] It should be noted that the preferred embodiment of this example can be found in [reference needed]. Figure 1 The relevant descriptions in the illustrated embodiments will not be repeated here.

[0156] Figure 7 The following is a sequence diagram illustrating the processing of a customer-state order in a task processing method according to an exemplary embodiment. The interaction flow between the core task module, the task pool, the operations backend, and the order processing module is as follows:

[0157] First, when the core task module receives a customer order, it reads the delivery rules from the operations backend. Based on the delivery rules, it verifies whether the customer order can be merged. If the task involved in the customer order is a virtual task and the completion condition is a multi-person order, the core task module scans the task pool to filter tasks that meet the conditions for the customer order. If a task that meets the conditions is found, a merge message is sent to the order processing module. If no task that meets the conditions is found, the customer order is added to the task pool.

[0158] Finally, when the task core module receives the order completion notification from the order processing module, it pushes the order completion notification.

[0159] It should be noted that the preferred embodiment of this example can be found in [reference needed]. Figure 1 The relevant descriptions in the illustrated embodiments will not be repeated here.

[0160] Based on the server-side task processing methods described in the above embodiments, this application also provides a client-side task processing method, which includes the following steps on the client side:

[0161] Step 401: Send the order payment message for the first task to the server so that the server can merge the first task and the second task in the task pool according to the first task meeting the task merging conditions; wherein, the task pool contains tasks that meet the task merging conditions that were generated before the first task, and the second task is a task in the task pool that is similar to the first task.

[0162] Step 402: Receive the order completion notification returned by the server.

[0163] Optionally, when sending the order payment message for the first task to the server, the order payment page corresponding to the order type can be displayed according to the order type initiated by the user. The order type includes either a primary order or a secondary order. Upon receiving the order submission request triggered by the user on the order payment page, the order payment message for the first task can be sent to the server.

[0164] For details on the implementation process of each step in the above client-side method, please refer to the corresponding implementation process in the above server-side method, which will not be repeated here.

[0165] Corresponding to the embodiments of the aforementioned task processing method, this application also provides embodiments of a task processing apparatus.

[0166] Figure 8 This is a schematic diagram illustrating the structure of a task processing apparatus according to an exemplary embodiment. The apparatus is used to execute the task processing method provided in the above-described server-side embodiment, such as... Figure 8 As shown, the task processing device includes:

[0167] The receiving module 810 is used to receive the first task that meets the task merging conditions;

[0168] The filtering module 820 is used to filter a second task similar to the first task from the task pool; the task pool includes tasks that meet the task merging conditions and were generated before the first task.

[0169] The merging module 830 is used to merge the first task and the second task according to the task status of the first task and the task status of the second task when the second task is selected.

[0170] The order push module 840 is used to push the order completion notification generated by the combined order to the ordering user of the first task and the ordering user of the second task, respectively.

[0171] In one optional implementation, the receiving module 810 is specifically used to receive a main state order generated by a main state payment, wherein the main state payment is a task initiated by the user to pay for an order; based on the preset delivery rules and the processing intention selected by the user carried in the main state order, it determines whether the main state order meets the task merging conditions; if it is determined that the task merging conditions are met, the main state order is taken as the first task.

[0172] In an optional implementation, the receiving module 810 is specifically configured to, during the process of determining whether a main order meets the task merging conditions based on preset delivery rules and the user's selected processing intention carried by the main order, set a timer for the main order according to the region it belongs to and start timing when the region to which the main order belongs is a delivery region in the preset delivery rules and the processing intention is to agree to task merging; the timeout time of the timer is the merging delay time corresponding to the region in the preset delivery rules; if the timer times out and the task status of the main order is in progress, determine that the main order meets the task merging conditions; if the region to which the main order belongs does not belong to a delivery region in the preset delivery rules, or the processing intention is to disagree with task merging, or the task status of the main order is a successful order after the timer times out, determine that the main order does not meet the task merging conditions.

[0173] In an optional implementation, the receiving module 810 is specifically used to receive customer-state orders generated by customer-state payments, where the customer-state payment is an order payment made by a user participating in a task; when the task in which the customer-state order participates is a virtual task and the customer-state order is the first order of the virtual task, the module obtains the order completion conditions of the virtual task; the virtual task refers to a task initiated by the system; when the order completion conditions are multiple orders and the area to which the customer-state order belongs belongs to the delivery area in the preset delivery rules, the customer-state order is regarded as the first task that meets the task merging conditions.

[0174] In an optional implementation, the filtering module 820 is specifically used to determine the user distance and merchant distance between the first task and each task in the task pool; and to filter a second task similar to the first task in the task pool based on the user distance and / or the merchant distance.

[0175] In an optional implementation, the merging module 830 is specifically used to: when the second task includes one task, if the task status of the first task is in progress and the task status of the second task is in progress, merge the first task and the second task to obtain a completion notification; when the second task includes two or more tasks, merge the tasks in the second task whose task status is in progress with the first task to obtain a completion notification; and delete the second task from the task pool.

[0176] In an alternative implementation, the apparatus further includes ( Figure 8 (Not shown in the image):

[0177] The order processing module is used to: after the filtering module 820 filters a second task similar to the first task in the task pool, add the first task to the task pool if no second task is found; if the first task is of the "no-combination" type, obtain the order processing time corresponding to the region to which the first task belongs from the preset delivery rules; set a timer for the first task and start timing, the timeout time of the timer being the order processing time; if the timer expires and the task status of the first task is still in progress, delete the first task from the task pool and generate an order completion notification for the first task to be pushed to the user who placed the order.

[0178] The specific implementation process of the functions and roles of each unit in the above device can be found in the implementation process of the corresponding steps in the above method, and will not be repeated here.

[0179] For the device embodiments, since they basically correspond to the method embodiments, the relevant parts can be referred to in the description of the method embodiments. The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this application according to actual needs. Those skilled in the art can understand and implement this without creative effort.

[0180] Corresponding to the aforementioned embodiments of the task processing method, this application also provides an embodiment of another task processing apparatus for executing the aforementioned task processing method provided on the client side. This task processing apparatus includes:

[0181] The sending module is used to send an order payment message for the first task to the server, so that the server can merge the first task and the second task in the task pool according to the first task meeting the task merging conditions; wherein, the task pool includes tasks that meet the task merging conditions that were generated before the first task, and the second task is a task in the task pool that is similar to the first task.

[0182] The receiving module is used to receive the order completion notification returned by the server.

[0183] This application also provides an electronic device corresponding to the task processing method provided in the foregoing embodiments, for executing the task processing method described above.

[0184] Figure 9 The present invention illustrates a hardware structure diagram of an electronic device according to an exemplary embodiment. The electronic device includes a communication interface 601, a processor 602, a memory 603, and a bus 604. The communication interface 601, processor 602, and memory 603 communicate with each other via the bus 604. The processor 602 can execute the task processing method described above by reading and executing machine-executable instructions corresponding to the control logic of the task processing method in the memory 603. The specific content of this method is described in the above embodiment and will not be repeated here.

[0185] The memory 603 mentioned in this application can be any electronic, magnetic, optical, or other physical storage system, and can contain stored information such as executable instructions, data, etc. Specifically, the memory 603 can be RAM (Random Access Memory), flash memory, storage drive (such as hard disk drive), any type of storage disk (such as optical disc, DVD, etc.), or similar storage media, or combinations thereof. Communication between this system network element and at least one other network element is achieved through at least one communication interface 601 (which can be wired or wireless), and the Internet, wide area network, local area network, metropolitan area network, etc., can be used.

[0186] Bus 604 can be an ISA bus, PCI bus, or EISA bus, etc. The bus can be divided into an address bus, a data bus, a control bus, etc. The memory 603 is used to store programs, and the processor 602 executes the programs after receiving execution instructions.

[0187] Processor 602 may be an integrated circuit chip with signal processing capabilities. In implementation, each step of the above method can be completed by the integrated logic circuitry in the hardware of processor 602 or by instructions in software form. The processor 602 can be a general-purpose processor, including a network processor (NP), digital signal processor (DSP), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this application can be directly manifested as execution by a hardware decoding processor, or execution by a combination of hardware and software modules in the decoding processor.

[0188] The electronic device provided in this application embodiment and the task processing method provided in this application embodiment are based on the same inventive concept and have the same beneficial effects as the methods they adopt, operate or implement.

[0189] This application also provides a computer-readable storage medium corresponding to the task processing method provided in the foregoing embodiments. Please refer to... Figure 10 As shown, the computer-readable storage medium is an optical disc 30, on which a computer program (i.e., a program product) is stored. When the computer program is run by a processor, it executes the task processing method provided in any of the foregoing embodiments.

[0190] It should be noted that examples of the computer-readable storage medium may also include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other optical and magnetic storage media, which will not be elaborated here.

[0191] The computer-readable storage medium provided in the above embodiments of this application and the task processing method provided in the embodiments of this application are based on the same inventive concept and have the same beneficial effects as the methods adopted, run or implemented by the applications stored therein.

[0192] This application also provides a computer program product corresponding to the task processing method provided in the foregoing embodiments. The computer program product includes a computer program that is executed by a processor to implement the task processing method provided in the foregoing embodiments.

[0193] The computer program products provided in the above embodiments of this application and the task processing methods provided in the embodiments of this application are based on the same inventive concept and have the same beneficial effects as the methods adopted, run or implemented by the applications stored therein.

[0194] Other embodiments of this application will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of this application that follow the general principles of this application and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this application are indicated by the following claims.

[0195] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

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

Claims

1. A task processing method, characterized in that, Applied to the server side, the method includes: Receive a first task that meets the task merging criteria, and filter a second task similar to the first task from the task pool; the task pool includes tasks that meet the task merging criteria that were generated before the first task. If a second task is selected, the first task and the second task are combined into one order based on the task status of the first task and the task status of the second task. The order completion notification generated by the combined order will be pushed to the user who placed the order for the first task and the user who placed the order for the second task, respectively.

2. The method of claim 1, wherein, Receiving the first task that meets the task merging conditions includes: Receive a main state order generated by the main state payment, wherein the main state payment is a task initiated by the user to pay for the order; Based on the preset delivery rules and the user's selected processing intention carried by the main status order, determine whether the main status order meets the task merging conditions; If the conditions for task merging are met, the main state unit will be designated as the first task.

3. The method of claim 2, wherein, The step of determining whether the main order meets the task merging conditions based on preset delivery rules and the user's selected processing intention carried by the main order includes: If the region to which the main order belongs is a delivery region in the preset delivery rules and the processing intention is to agree to merge tasks, a timer is set for the main order according to the region to which it belongs, and the timer starts counting down; the timeout period of the timer is the merging delay time corresponding to the region to which it belongs in the preset delivery rules; If the timer times out and the task status of the main state unit is in progress, it is determined that the main state unit meets the task merging condition; If the area to which the main order belongs does not belong to the delivery area in the preset delivery rules, or the processing intention is to disagree with the task merging, or the task status of the main order is a successful order after the timer expires, then the main order is determined to not meet the task merging conditions.

4. The method of claim 1, wherein, Receiving the first task that meets the task merging conditions includes: Receive customer-state payment orders generated by customer-state payments, where the customer-state payment is made by the user participating in a task to pay for the order; If the task in which the customer-state order participates is a virtual task and the customer-state order is the first order of the virtual task, then obtain the order completion conditions of the virtual task; the virtual task refers to a task initiated by the system. If the order completion condition is a multi-person order and the area to which the customer-state order belongs belongs to the delivery area in the preset delivery rules, the customer-state order will be regarded as the first task that meets the task merging condition.

5. The method according to claim 1, characterized in that, The step of filtering a second task similar to the first task from the task pool includes: Determine the user distance and merchant distance between the first task and each task in the task pool; Based on the user distance and / or the merchant distance, a second task similar to the first task is selected from the task pool.

6. The method of claim 1, wherein, The step of merging the first task and the second task based on the task status of the first task and the task status of the second task includes: If the second task includes an order, and the task status of the first task is in progress and the task status of the second task is in progress, the first task and the second task are merged to obtain an order completion notification. If the second task includes two or more orders, the tasks in the second task that are in progress will be merged with the first task to obtain a completion notification. Remove the second task from the task pool.

7. The method according to claim 1, characterized in that, After filtering a second task similar to the first task from the task pool, the method further includes: If no second task is found, the first task is added to the task pool. If the first task is of the "no-combination" type, the order placement time corresponding to the region to which the first task belongs is obtained from the preset delivery rules; Set a timer for the first task and start timing. The timeout period of the timer is the order pressing time. If the timer expires and the task status of the first task is still in progress, the first task is deleted from the task pool, and a completion notification is generated for the first task to be pushed to the user who placed the order.

8. A task processing method characterized by, Applied to a client, the method includes: The server sends an order payment message for the first task to the server so that the server can merge the first task and the second task in the task pool according to the first task meeting the task merging conditions; wherein, the task pool includes tasks that meet the task merging conditions that were generated before the first task, and the second task is a task in the task pool that is similar to the first task. Receive the order completion notification returned by the server.

9. The method of claim 8, wherein, The step of sending the order payment message for the first task to the server includes: Based on the order type initiated by the user for the first task, display the order payment page corresponding to the order type, which includes either a primary order or a secondary order. Upon receiving an order submission request triggered by a user on the order payment page, the system sends the first task's order payment message to the server.

10. An electronic device comprising a memory, a processor, and a computer program stored on the memory and executable on the processor, characterized in that, The processor executes the program to implement the method as described in any one of claims 1-9.

Images