CN111832857B - Task dispatch processing method, device and electronic equipment - Google Patents

Abstract

The embodiment of the application discloses a task issuing processing method, a task issuing processing device and electronic equipment. The method comprises the following steps: the task issuing server obtains configuration information, wherein the configuration information comprises timing task information and interface information, and the timing task comprises: tasks involved in providing fulfillment services for orders associated with physical stores, the physical stores being a plurality; the same piece of configuration information is shared by a plurality of entity shops; after receiving the call of the timing task through the interface, determining the target task type information associated with the timing task; acquiring target order data corresponding to the target task type information from an order information base; and sending the target order data to an operating system corresponding to the target task type information. By the scheme, the implementation configuration process is simplified, and the later maintenance cost is reduced.

Description

Task dispatch processing method, device and electronic equipment

Technical Field

The present application relates to the field of new retail technology, and in particular to a task dispatching and processing method, device and electronic equipment.

Background Art

Under the "new retail" business model, retailers can open offline physical stores, and consumers can directly go to offline physical stores to purchase goods. At the same time, retailers can also provide online stores corresponding to physical stores through online applications (Apps), and display relevant information about goods that physical stores can provide to consumers through online stores.

When consumer users purchase commodity objects through the App, they can first determine a target physical store that is geographically closest to the consumer user from the physical stores opened by the retailer, and then provide the online store corresponding to the target physical store through the App for the consumer users to place orders online.

The order data submitted by the consumer user through the App can be first saved in the order information library, and then the task issuing server in the fulfillment system can provide fulfillment services for the orders associated with the physical store. Specifically, the task issuing server can batch process the order data associated with the same physical store based on the relevant information included in the order data. Among them, the relevant information included in the order data can be the identification information of the order, the identification information of the target physical store, the identification information of the warehouse associated with the target physical store, the identification information of the distribution station associated with the target physical store, the identification information of the retailer, the information of the purchased goods, the delivery address information, and the delivery time information.

In order to achieve batch processing of order data associated with the same physical store, the task delivery server needs to provide multiple interfaces for each physical store to implement different types of tasks. Correspondingly, the task delivery client needs to configure multiple different types of scheduled tasks for each physical store and specify the interface called by each scheduled task. Taking physical store A as an example, the task delivery server can provide the following interfaces:

Interface A1 that implements the batch job task of sending order data associated with physical store A;

Interface A2 that implements the warehouse operation task of sending order data associated with physical store A;

Interface A3 that implements the delivery task of the order data associated with physical store A.

The corresponding task delivery client can configure the following scheduled tasks:

Issue scheduled task A1 of the synthesis batch job, and task 1 is configured with the calling address information of interface A1;

Send the scheduled task A2 of the warehouse operation. Task 2 is configured with the calling address information of interface A2.

A scheduled task A3 of the distribution operation is issued, and the calling address information of the interface A3 is configured in task 3.

In this way, when each scheduled task is started, the interface provided by the task issuing server can be called to obtain the target order data to be fulfilled under the physical store A from the order information library, and the target order data can be sent to the corresponding operation system for related operations.

From the above fulfillment processing process, it can be seen that the existing fulfillment configuration process is relatively complicated, and as the number of physical stores gradually increases, the interface information and scheduled task information that need to be maintained will also double, resulting in high maintenance costs in the later stage. In addition, when adding a new physical store, if the configured scheduled task information and interface information are missing, it is impossible to obtain the order data associated with the newly added physical store for task delivery, resulting in the inability of the newly added physical store to perform the contract normally, affecting the experience of consumer users.

Summary of the invention

The present application provides a task dispatching processing method, device and electronic device. The task dispatching server can dispatch different types of tasks based on configuration information that can be shared by multiple physical stores, which helps to simplify the fulfillment configuration process and reduce subsequent maintenance costs.

This application provides the following solutions:

A task delivery processing method includes:

The task issuing server obtains configuration information, wherein the configuration information includes scheduled task information and interface information, wherein the scheduled task includes: tasks involved in providing fulfillment services for orders associated with a physical store, wherein there are multiple physical stores; wherein the same configuration information is shared by multiple physical stores;

After receiving a call to a scheduled task through the interface, determining target task type information associated with the scheduled task;

Acquire target order data corresponding to the target task type information from an order information database;

The target order data is sent to the operation system corresponding to the target task type information.

A task delivery processing method includes:

When the task issuing client obtains the scheduled task configuration request submitted by the user, it provides an operation option for submitting configuration information, wherein the configuration information includes scheduled task information and interface information, and the same configuration information is shared by multiple physical stores;

After obtaining the configuration information through the operation options, submit it to the task issuing server, so that after the task issuing server receives the call of the scheduled task through the interface, it can determine the target task type information associated with the scheduled task; obtain the target order data corresponding to the target task type information from the order information library and send it to the operating system corresponding to the target task type information.

A task delivery processing method includes:

The operation system server obtains the target order data sent by the task issuing server, wherein the target order data is the target order data corresponding to the target task type information obtained from the order information library after the task issuing server determines the target task type information associated with the scheduled task of the calling interface based on the configuration information shared by multiple physical stores;

Perform task processing on the target order data.

A task delivery processing method includes:

The operation system client obtains the operation task information sent by the operation system server, wherein the operation task information is obtained after the operation system server performs task processing on the target order data sent by the task issuing server, and the task issuing server obtains the target order data from the order information library based on the configuration information shared by multiple physical stores;

The operation task information is displayed so that the operator associated with the operation system client can perform operations on the target order data.

A task delivery processing device, applied to a task delivery server, comprising:

a configuration information obtaining unit, configured to obtain configuration information, wherein the configuration information includes scheduled task information and interface information, wherein the scheduled task includes: tasks involved in the process of providing fulfillment services for orders associated with a physical store, wherein there are multiple physical stores; wherein the same configuration information is shared by multiple physical stores;

A target task type information determining unit, configured to determine the target task type information associated with the scheduled task after receiving a call of the scheduled task through the interface;

A target order data acquisition unit, used to acquire target order data corresponding to the target task type information from an order information database;

The target order data sending unit is used to send the target order data to the operation system corresponding to the target task type information.

A task delivery processing device, applied to a task delivery client, comprising:

An operation option providing unit, used to provide an operation option for submitting configuration information when obtaining a scheduled task configuration request submitted by a user, wherein the configuration information includes scheduled task information and interface information, and the same configuration information is shared by multiple physical stores;

A configuration information submission unit is used to submit the configuration information obtained through the operation options to the task issuing server, so that after the task issuing server receives the call of the scheduled task through the interface, it can determine the target task type information associated with the scheduled task; obtain the target order data corresponding to the target task type information from the order information library and send it to the operating system corresponding to the target task type information.

A task distribution processing device, applied to an operation system server, comprises:

A target order data obtaining unit is used to obtain target order data sent by the task issuing server, wherein the target order data is the target order data corresponding to the target task type information obtained from the order information library after the task issuing server determines the target task type information associated with the scheduled task of the calling interface based on the configuration information shared by multiple physical stores;

A task processing unit is used to perform task processing on the target order data.

A task distribution processing device, applied to an operating system client, comprises:

An operation task information obtaining unit, used to obtain the operation task information sent by the operation system server, wherein the operation task information is obtained after the operation system server performs task processing on the target order data sent by the task issuing server, and the task issuing server obtains the target order data from the order information library based on the configuration information shared by multiple physical stores;

The operation task information display unit is used to display the operation task information so that the operator associated with the operation system client can perform the operation on the target order data.

An electronic device, comprising:

one or more processors; and

A memory associated with the one or more processors, the memory being used to store program instructions, wherein when the program instructions are read and executed by the one or more processors, the following operations are performed:

Obtaining configuration information, wherein the configuration information includes scheduled task information and interface information, wherein the scheduled task includes: tasks involved in providing fulfillment services for orders associated with a physical store, wherein there are multiple physical stores; wherein the same configuration information is shared by multiple physical stores;

After receiving a call to a scheduled task through the interface, determining target task type information associated with the scheduled task;

Acquire target order data corresponding to the target task type information from an order information database;

The target order data is sent to the operation system corresponding to the target task type information.

An electronic device, comprising:

one or more processors; and

A memory associated with the one or more processors, the memory being used to store program instructions, wherein when the program instructions are read and executed by the one or more processors, the following operations are performed:

When obtaining a scheduled task configuration request submitted by a user, an operation option for submitting configuration information is provided. The configuration information includes scheduled task information and interface information. The same configuration information is shared by multiple physical stores.

After obtaining the configuration information through the operation options, submit it to the task issuing server, so that after the task issuing server receives the call of the scheduled task through the interface, it can determine the target task type information associated with the scheduled task; obtain the target order data corresponding to the target task type information from the order information library and send it to the operating system corresponding to the target task type information.

An electronic device, comprising:

one or more processors; and

A memory associated with the one or more processors, the memory being used to store program instructions, wherein when the program instructions are read and executed by the one or more processors, the following operations are performed:

Obtaining target order data sent by the task issuing server, wherein the target order data is the target order data corresponding to the target task type information obtained from the order information library after the task issuing server determines the target task type information associated with the scheduled task calling the interface based on the configuration information shared by multiple physical stores;

Perform task processing on the target order data.

An electronic device, comprising:

one or more processors; and

A memory associated with the one or more processors, the memory being used to store program instructions, wherein when the program instructions are read and executed by the one or more processors, the following operations are performed:

Obtaining the operation task information sent by the operation system server, wherein the operation task information is obtained after the operation system server performs task processing on the target order data sent by the task issuing server, and the task issuing server obtains the target order data from the order information library based on the configuration information shared by multiple physical stores;

The operation task information is displayed so that the operator associated with the operation system client can perform operations on the target order data.

According to the specific embodiments provided in this application, this application discloses the following technical effects:

Through the embodiments of the present application, the task issuing service end can obtain configuration information that can be shared by multiple physical stores, and implement the issuing processing of multiple different types of tasks based on the scheduled task information and interface information in the configuration information. Specifically, after the interface receives the call of the scheduled task, the target task type information associated with the scheduled task can be determined according to the configuration information, and then the target order data corresponding to the target task type information is obtained from the order information library for task issuing. With such a solution, there is no need to configure the interface and scheduled tasks for each physical store one by one, which helps to simplify the fulfillment configuration process and reduce the subsequent maintenance costs. In particular, when a newly added physical store falls within the scope of the configuration information, there is no need to perform a separate configuration for the newly added physical store. The target order data associated with the newly added physical store can be obtained according to the configuration information for task issuing, and there will be no situation where the fulfillment cannot be performed, which helps to improve the user experience.

Of course, any product implementing the present application does not necessarily need to achieve all of the advantages described above at the same time.

BRIEF DESCRIPTION OF THE DRAWINGS

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

FIG1 is a schematic diagram of a system provided in an embodiment of the present application;

FIG2 is a schematic diagram of a first method provided in an embodiment of the present application;

FIG3 is a schematic diagram of an interface provided by an embodiment of the present application;

FIG4 is a flow chart of a second method provided in an embodiment of the present application;

FIG5 is a flow chart of a third method provided in an embodiment of the present application;

FIG6 is a flow chart of a fourth method provided in an embodiment of the present application;

FIG7 is a flow chart of a fifth method provided in an embodiment of the present application;

FIG8 is a schematic diagram of a first device provided in an embodiment of the present application;

FIG9 is a schematic diagram of a second device provided in an embodiment of the present application;

FIG10 is a schematic diagram of a third device provided in an embodiment of the present application;

FIG11 is a schematic diagram of a fourth device provided in an embodiment of the present application;

FIG12 is a schematic diagram of the architecture of a computer system provided in an embodiment of the present application;

FIG. 13 is a schematic diagram of the architecture of an electronic device provided in an embodiment of the present application.

DETAILED DESCRIPTION

The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field belong to the scope of protection of this application.

In order to simplify the fulfillment configuration process, an embodiment of the present application provides a tool that can perform task issuance processing without separate configuration for each physical store, which may include a task issuance client and a task issuance server. As shown in Figure 1, the task issuance server can be deployed on a cloud server, providing an interface that can be shared by multiple physical stores; the task issuance client can be deployed on a terminal device associated with a developer, configure scheduled tasks that can be shared by multiple physical stores, and an interface called by the scheduled task, and submit configuration information including scheduled task information and interface information to the task issuance server. Among them, scheduled tasks may include: tasks involved in the process of providing fulfillment services for orders associated with physical stores, such as issuing composite batch (hereinafter referred to as composite batch) operation tasks, issuing warehouse operation tasks, and issuing distribution operation tasks.

In an embodiment of the present application, the configuration information submitted by the task issuing client may include a variety of different implementation methods. For example, in one method, the configuration information may include multiple scheduled task information corresponding to different types of tasks and multiple interface information. That is to say, the task issuing server may provide multiple interfaces corresponding to different types of tasks, for example, interface 1 corresponding to issuing batch operation tasks, interface 2 corresponding to issuing warehouse operation tasks, and interface 3 corresponding to issuing distribution operation tasks. At the same time, the task issuing client may configure multiple different types of scheduled tasks, for example, scheduled task 1 for issuing batch operations, scheduled task 2 for issuing warehouse operations, and scheduled task 3 for issuing distribution operations, wherein scheduled task 1 may call interface 1, scheduled task 2 may call interface 2, and scheduled task 3 may call interface 3. The task issuing client may submit configuration information 1 representing the calling relationship between scheduled tasks and interfaces to the task issuing server.

In this method, multiple physical stores can share the above three scheduled tasks and three interfaces to implement task delivery for order data associated with the multiple physical stores. As an example, the corresponding relationship between physical stores and configuration information 1 can be shown in Table 1 below.

Table 1

Alternatively, in another manner, the configuration information may include multiple scheduled task information corresponding to different types of tasks and an interface information. That is, the task issuing server may provide a general interface 4 for multiple different types of tasks, and multiple different types of scheduled tasks configured by the task issuing client may call the interface 4 to issue tasks. For example, scheduled task 1 calls interface 4 to issue batch operation tasks, scheduled task 2 calls interface 4 to issue warehouse operation tasks, and scheduled task 3 calls interface 4 to issue distribution operation tasks. The task issuing client may submit the configuration information 2 indicating the calling relationship between the scheduled task and the interface to the task issuing server.

In this method, multiple physical stores can share the above three scheduled tasks and one interface to implement task delivery for order data associated with the multiple physical stores. As an example, the correspondence between physical stores and configuration information 2 can be shown in Table 2 below.

Table 2

In the above two methods, the scheduled tasks configured by the task issuing client correspond to the task type one by one. Therefore, after the interface receives the call of the scheduled task, it can determine the target task type corresponding to the scheduled task, and then obtain the target order data corresponding to the target task type information from the order information library to issue the task.

Alternatively, in another manner, the configuration information may include a scheduled task information and an interface information corresponding to different types of tasks. That is, the task delivery server may provide a general interface 5 for multiple different types of tasks, the task delivery client may configure a general scheduled task 4 for multiple different types of tasks, and the scheduled task 4 may call the interface 5 to implement the delivery processing of different types of tasks. Similarly, the task delivery client may submit the configuration information 3 indicating the calling relationship between the scheduled task and the interface to the task delivery server.

In this method, multiple physical stores can share the above 1 scheduled task and 1 interface to implement task delivery for order data associated with the multiple physical stores. As an example, the correspondence between the physical stores and the configuration information 3 can be shown in Table 3 below.

Table 3

In this mode, the task type parameter can be configured in the scheduled task 4, and the interface 5 can include: common code lines for implementing different types of tasks, and distinguishing code lines that can distinguish the different types of tasks. In this way, after the interface 5 receives the call of the scheduled task 4, the distinguishing code lines can determine the task type information associated with the scheduled task according to the task type parameter. The task dispatching process under this implementation mode is explained below in conjunction with the flow chart shown in Figure 2.

Example 1

S101: The task issuing server implements a general interface, wherein the general interface includes: common code lines for implementing multiple different types of tasks, and distinguishing code lines for distinguishing the multiple different types of tasks.

For the order data associated with different physical stores, there are three types of tasks: issuing batch operation tasks, issuing warehouse operation tasks, and issuing distribution operation tasks. For different types of tasks, although the purpose is to issue tasks for the pending order data of that type, some of the same operation actions may be performed during implementation. For example, the order data of the pending batch operation tasks associated with physical store 1 is obtained from the order information library, the order data of the pending warehouse operation tasks associated with physical store 2 is obtained from the order information library, and the order data of the pending distribution operation tasks associated with physical store 3 is obtained from the order information library. It can be seen from the above examples that obtaining the order data associated with the physical store is an operation action that will be performed by each type of task, so interface 5 can include common code lines for implementing the same operation action.

In addition, for different types of tasks, different operation actions will be performed when the tasks are implemented. For example, issuing a batch operation task requires obtaining the order data of the batch operation task to be issued from the order information library, and sending the obtained order data to the batch operation system; issuing a warehouse operation task requires obtaining the order data of the warehouse operation task to be issued from the order information library, and sending the obtained order data to the warehouse operation system; issuing a distribution operation task requires obtaining the order data of the distribution operation task to be issued from the order information library, and sending the obtained order data to the distribution operation system. From the above examples, it can be seen that obtaining which type of order data to be fulfilled and to which operation system the obtained order data is issued are different operation actions performed by different types of tasks. Therefore, interface 5 can include different code lines that can distinguish different types of tasks.

In summary, the target task type information can be determined by distinguishing code lines, and the common code lines and the distinguishing code lines can be combined to obtain a query condition, and the target order data corresponding to the target task type information can be obtained from the order information library based on the query condition.

S102: The task issuing client configures a general scheduled task and submits configuration information including scheduled task information and interface information to the task issuing server.

Taking the configuration of scheduled task 4 as an example, when obtaining the scheduled task configuration request submitted by the developer, the task issuing client can provide the scheduled task configuration interface shown in Figure 3, through which the operation options for submitting configuration information can be provided. For example, it can include an operation option for submitting the call address information of interface 5, an operation option for submitting task parameter information, and an operation option for submitting task type information. After obtaining the configuration information including the scheduled task information and the interface information through the operation options, it can be submitted to the task issuing server, so that after the task issuing server receives the call of the scheduled task 4 through the interface 5, it can determine the target task type information associated with the scheduled task 4 at this time and perform the task issuing process.

In addition to the task type parameters mentioned above, the task parameter information in the embodiment of the present application may also include other parameter information configured according to requirements, which is illustrated below with examples.

For example, the task issuing server may obtain all order data associated with a physical store at one time, or may obtain a specified number of order data associated with a physical store at one time, that is, the task parameter information configured by the task issuing client may include specified quantity information.

For example, the task parameter information configured by the task issuing client may include query method information, and a dynamic selection may be made between a database query method with strong real-time performance and a search engine query method with fast query speed to meet different query requirements. In other words, the task issuing server may obtain the target order data from the order information library based on the query method specified by the task parameter information.

For example, the task parameter information configured by the task issuing client may include concurrent lock information. The task issuing server may issue the concurrent lock information and the target order data to the corresponding operation system so that the operation system server can perform anti-concurrency processing according to the concurrent lock information to prevent the target order data from being repeatedly operated. Among them, the concurrent lock information can be reflected as a database lock and a distributed lock. The database lock can also include an optimistic lock and a universal mutex lock. The distributed lock can also include a redis lock and a zokeeper lock. The task issuing client can dynamically select the concurrent lock used by the operation system server by modifying the concurrent lock information.

S103: The task issuing server obtains configuration information, and the configuration information is shared by multiple physical stores.

The interface 5 and the scheduled task 4 of the embodiment of the present application can be reused among multiple physical stores, and there is no need to configure each physical store separately. That is, after the interface 5 implemented by the task dispatching service receives the call of the scheduled task 4, it can obtain the target order data associated with multiple physical stores within the scope of each configuration information from the order information library, which helps to simplify the fulfillment configuration process and reduce the subsequent maintenance costs. In particular, when adding a new physical store, as long as the new physical store is within the scope of the configuration information, the configuration information can be used to provide a task dispatching service for the order data associated with the new physical store.

Among them, the scope of the configuration information can be understood as which physical stores can share the configuration information. For example, in one way, the scope of the configuration information can be specific to the retailer dimension, that is, all physical stores associated with the same retailer user can share a copy of the configuration information. As shown in Table 4 below, the task issuing client can configure a general scheduled task 41 for the 100 physical stores opened by retailer user 1, and submit the corresponding configuration information 31 (which may include the scheduled task information of the scheduled task 41 and the interface information of interface 5) to the task issuing server; configure a general scheduled task 42 for the 50 physical stores opened by retailer user 2, and submit the corresponding configuration information 32 (which may include the scheduled task information of the scheduled task 42 and the interface information of interface 5) to the task issuing server.

Table 4

In this method, the scheduled task information in the configuration information may also include the identification information of the retailer user, so that the task issuing server can determine the scope of the configuration information accordingly. For example, if the newly added physical store has the identification information of the retailer user 1, it can be determined that the newly added physical store is within the scope of the configuration information 31, and the order data associated with the newly added physical store can be obtained from the order information library based on the configuration information 31 for task issuing processing.

Alternatively, in another way, the scope of the configuration information can be specific to the store dimension, that is, all physical stores associated with multiple different retailer users can share a set of configuration information. As shown in Table 5 below, the task issuing client can configure a general scheduled task 43 for the 100 physical stores opened by retailer user 1 and the 50 physical stores opened by retailer user 2, and submit the corresponding configuration information 33 (which may include the scheduled task information of the scheduled task 43 and the interface information of the interface 5) to the task issuing server. In this way, any newly added physical store can be within the scope of the configuration information 33, so the task issuing service can be provided for all newly added physical stores based on the configuration information 33.

Table 5

In the embodiment of the present application, each retailer user can independently develop a business system of the "new retail" model, and in accordance with the method described above, enable the physical stores associated with the retailer to share a set of configuration information, and then provide fulfillment services for the orders associated with these physical stores.

In addition, considering that the cost of developing business systems independently by retail users will be very high, some small and medium-sized retailers may not be able to afford it. In this environment, platforms that provide "new retail" solutions have emerged. This platform can create a new retail "model room" by empowering traditional retail users, copying the platform's product capabilities, data capabilities, operating models and other elements to retail users, allowing retail users to gradually improve their own business capabilities based on the same business standards and execution processes as the various business areas in the "new retail" system. For example, retail users can submit their product information, inventory information in the warehouse, fulfillment capability information, sales information, etc. to the platform, and the platform will support them in implementing specific business processes, so that retail users can also provide services to the outside world in accordance with the "new retail" model. In such a scenario, the platform can configure scheduled tasks based on store dimensions or retailer dimensions according to needs, and provide fulfillment services for orders associated with physical stores associated with each retail user.

S104: After receiving the call of the scheduled task through the interface, determine the target task type information associated with the scheduled task.

As described above, the task issuing server can determine the target task type information associated with the scheduled task through the task type parameter in the scheduled task information. Take the task of issuing a batch job as an example. This task is the first task executed during batch processing, so the task type parameter can be configured by default as issuing a batch job task. In this way, when the scheduled task 4 starts calling interface 5, the distinguishing code line can determine the issuing batch job task as the target task type according to the task type parameter, and then obtain the target order data of the batch job task to be issued from the order information library, and send the obtained target order data to the batch job system server for batch operation.

For example, the batch operation system server performs task processing on the target order data according to the picking area information (the picking area can be determined according to the type of commodity objects included in the target order data, such as fruit picking area, seafood picking area, vegetable picking area, etc.), delivery address information, and delivery time information, and combines the 20 target order data associated with physical store 1 into two batches. Among them, batch 1 corresponds to 8 target order data, and batch 2 corresponds to 12 target order data.

For issuing warehouse operation tasks and issuing distribution operation tasks, they need to be triggered for execution only after the batch operation is completed. Therefore, the task issuing server can update the task type parameter after determining that the batch operation system has completed the batch operation for the target order data, so as to distinguish the code lines and determine the issuing of warehouse operation tasks and issuing of distribution operation tasks as the target task type according to the updated task type parameter.

Usually, according to the fulfillment logic, it is necessary to first complete the warehouse operation to pick and pack, and then perform the distribution operation to deliver the goods to the consumer user. Therefore, updating the task type parameter can be reflected in that after determining that the batch operation system completes the batch operation for the target order data, the task issuing server can update the task type parameter to issue the warehouse operation task. Taking "1" for issuing the batch operation task and "2" for issuing the warehouse operation task as an example, the task type parameter can be updated to "2" at this time. In this way, when the scheduled task 4 calls the interface 5 for the second time, the difference code line can determine the warehouse operation task represented by "2" as the target task type, and then obtain the target order data of the warehouse operation task to be issued from the order information library (with the synthesized batch as the basic processing unit), and send the obtained target order data to the warehouse operation system server for picking and packing operations.

For example, the warehouse operation system server performs task processing on the 8 target order data corresponding to batch 1, and generates 3 picking tasks and 1 packing task according to the types of commodity objects included in the target order data. The picking operation task information corresponding to the 3 picking tasks can be sent to the warehouse operation system client associated with the picking operator of the physical store 1, and the packing operation task information corresponding to the 1 packing task can be sent to the warehouse operation system client associated with the packing operator of the physical store 1.

The warehouse operation system client associated with the picking operator can display the obtained picking operation task information so that the picking operator can perform picking operations on the 8 target order data corresponding to batch 1. In addition, after each picking operator completes the picking operation, all the goods can be summarized to the packing operator so that the packing operator can perform the packing operation according to the packing operation task information displayed by the associated warehouse operation system client.

Furthermore, updating the task type parameter can also be reflected in that after determining that the warehouse operation system completes the picking and packing operation for the target order data, the task issuing server can update the task type parameter to issue a distribution operation task. Taking "3" as an example, the task type parameter can be updated to "3". In this way, when the scheduled task 4 calls the interface 5 for the third time, the code line can be distinguished to determine the distribution operation task represented by "3" as the target task type, and then obtain the target order data of the distribution operation task to be issued from the order information library (still taking the synthesized batch as the basic processing unit), and send the obtained target order data to the distribution operation system server for distribution operation.

For example, the distribution operation system server performs task processing, generates one distribution task for the eight target order data corresponding to batch 1, and sends the distribution operation task information corresponding to the distribution task to the distribution operation system client associated with distribution operator 1 based on the load conditions of the distribution station associated with physical store 1.

The delivery operation system client associated with the delivery operation personnel 1 can display the obtained delivery operation task information so that the delivery operation personnel 1 can perform delivery operations on the packages packaged from the 8 target order data corresponding to the batch 1.

In addition, in order to achieve the fastest fulfillment capability, the warehouse operation tasks and the distribution operation tasks may not be executed in the above order. For example, after determining that the batch operation system server completes the batch operation for the target order data and updates the task type parameters, the warehouse operation tasks and the distribution operation tasks can be determined as the target task types at the same time, and the two types of tasks can be issued separately. Processing these two types of tasks in parallel can pre-schedule the corresponding distribution workers while picking and packing, which helps to shorten the fulfillment time.

S105: Acquire target order data corresponding to the target task type information from the order information library.

As described above, after scheduled task 4 starts calling interface 5, it can obtain a query condition. If the scheduled task information also includes query method information, the task issuing server can obtain the target order data corresponding to the target task type information from the order information library based on the query method specified by scheduled task 4 after obtaining the query condition.

It can be understood that the configuration information 3 in this embodiment can be shared by multiple physical stores, so the target order data obtained by the task issuing server from the order information library may correspond to different physical stores. In order to batch process the target order data associated with the same store, after the target order task is issued to the batch operation system, the batch operation system can group the target order data according to the store identification information in the target order data, and perform batch operations on the target order data in the group with the same store identification information.

S106: Send the target order data to the operation system server corresponding to the target task type information.

The operation system server in the embodiment of the present application can have a variety of different implementations. In one implementation, the operation system server can be deployed on a device, for example, the batch operation system server is deployed on device A, and all target order data of batch operation tasks to be issued can be sent to device A for operation; the warehouse operation system server is deployed on device B, and all target order data of warehouse operation tasks to be issued can be sent to device B for operation; the distribution operation system server is deployed on device C, and all target order data of distribution operation tasks to be issued can be sent to device C for operation.

Alternatively, in another implementation mode, the task issuing client can configure the scheduled task as a grid task, for example, an operation option for submitting grid task type information is provided through the scheduled task configuration interface, and the grid task type information can be submitted to the task issuing server after being obtained through the operation option. That is to say, the scheduled task information can also include grid task type information. In this mode, the operation system server can be deployed on multiple cluster devices corresponding to the grid task, and each cluster device can respectively deploy an operation system server that implements multiple different types of tasks. For example, the cluster includes 100 devices, and each device is deployed with a batch operation system server, a warehouse operation system server, and a distribution operation system server. In this way, when issuing tasks, different types of tasks can be issued without distinction according to the load conditions of each device, which not only helps to improve the operation efficiency of the operation system, but also avoids single point failures when a single machine is abnormal. It should be noted that when issuing tasks in this mode, the target task type information and the target order data can be sent to the cluster device so that the cluster device calls the operation system server corresponding to the target task type information to operate the target order data.

As an example, the operation system server can obtain the operation capacity information sent by the associated operation system client, so as to determine the target operation system client that performs the operation on the target order data according to the operation capacity information. For example, during the commodity delivery process, multiple delivery service providers may provide delivery services to consumer users. When the delivery resources of delivery service provider 1 are tight, the delivery operation system client associated with delivery service provider 1 can feed back the operation capacity information indicating the tight resources to the delivery operation system server, so that the delivery operation system server can determine the target delivery operator from delivery service provider 2 with sufficient delivery resources, and send the corresponding delivery operation to the delivery operation system client associated with the target delivery operator.

Example 2

This embodiment 2 corresponds to the embodiment 1, and provides a task delivery processing method from the perspective of the task delivery server. Referring to FIG. 4 , the method may specifically include:

S201: The task issuing server obtains configuration information, wherein the configuration information includes scheduled task information and interface information, wherein the scheduled task includes: tasks involved in the process of providing fulfillment services for orders associated with a physical store, wherein there are multiple physical stores; wherein the same configuration information is shared by multiple physical stores;

S202: after receiving the call of the scheduled task through the interface, determining the target task type information associated with the scheduled task;

S203: Acquire target order data corresponding to the target task type information from an order information database;

S204: Send the target order data to the operation system corresponding to the target task type information.

Example 3

This embodiment 3 corresponds to the embodiment 1, and provides a task delivery processing method from the perspective of the task delivery client. Referring to FIG. 5 , the method may specifically include:

S301: When the task issuing client obtains a scheduled task configuration request submitted by a user, an operation option for submitting configuration information is provided, wherein the configuration information includes scheduled task information and interface information, and the same configuration information is shared by multiple physical stores;

S302: After obtaining the configuration information through the operation options, submit it to the task issuing server, so that after the task issuing server receives the call of the scheduled task through the interface, it can determine the target task type information associated with the scheduled task; obtain the target order data corresponding to the target task type information from the order information library and send it to the operating system corresponding to the target task type information.

Example 4

This embodiment 4 corresponds to the embodiment 1, and provides a task delivery processing method from the perspective of the operation system server. Referring to FIG. 6 , the method may specifically include:

S401: the operation system server obtains target order data sent by the task issuing server, wherein the target order data is the target order data corresponding to the target task type information obtained from the order information database after the task issuing server determines the target task type information associated with the scheduled task of the calling interface based on the configuration information shared by multiple physical stores;

S402: Perform task processing on the target order data.

Example 5

This embodiment 5 corresponds to the embodiment 1, and provides a task delivery processing method from the perspective of the operating system client. Referring to FIG. 7 , the method may specifically include:

S501: The operation system client obtains the operation task information sent by the operation system server, wherein the operation task information is obtained after the operation system server performs task processing on the target order data sent by the task issuing server, and the task issuing server obtains the target order data from the order information library based on the configuration information shared by multiple physical stores;

S502: Display the operation task information so that the operator associated with the operation system client can perform the operation on the target order data.

For the undescribed parts in the aforementioned embodiments 2 to 5, please refer to the records in the aforementioned embodiments, which will not be repeated here.

Corresponding to Example 1, the embodiment of the present application further provides a task delivery processing device, see FIG8 , the device is applied to the task delivery server, including:

The configuration information obtaining unit 601 is used to obtain configuration information, wherein the configuration information includes scheduled task information and interface information, wherein the scheduled task includes: tasks involved in the process of providing fulfillment services for orders associated with a physical store, wherein there are multiple physical stores; wherein the same configuration information is shared by multiple physical stores;

A target task type information determining unit 602 is used to determine the target task type information associated with the scheduled task after receiving a call of the scheduled task through the interface;

The target order data acquisition unit 603 is used to acquire the target order data corresponding to the target task type information from the order information library;

The target order data sending unit 604 is used to send the target order data to the operation system corresponding to the target task type information.

Wherein, the device further comprises:

The scope information determination unit is used to determine the scope information of the same configuration information. When a new physical store is added, if the new physical store belongs to the scope, the configuration information is used to provide task distribution service for the new physical store.

The scope of action includes all physical stores associated with the same retailer user.

The scope of action includes all physical stores associated with multiple different retailer users.

The configuration information includes a plurality of scheduled task information and a plurality of interface information corresponding to different types of tasks.

The configuration information includes a plurality of scheduled task information corresponding to different types of tasks and an interface information.

The configuration information includes a scheduled task information and an interface information corresponding to different types of tasks;

The scheduled task information includes task type parameters, and the interface includes: common code lines for implementing different types of tasks, and distinguishing code lines that can distinguish the different types of tasks, and the distinguishing code lines are used to determine the target task type information according to the task type parameters.

The default configuration of the task type parameter is to issue a synthetic batch job task.

The target task type information determination unit is specifically used to:

The distinguishing code line determines the target task type information as a dispatching warehouse operation task according to the default configured task type parameters.

Wherein, the device further comprises:

A task type parameter updating unit, configured to update the task type parameter after determining that the target order data completes the synthesis batch operation;

The target task type information determination unit is specifically used to:

The distinguishing code line determines the target task type information as a dispatching warehouse operation task according to the updated task type parameter.

Wherein, the device further comprises:

A task type parameter updating unit, configured to update the task type parameter after determining that the target order data completes the synthesis batch operation;

The target task type information determination unit is specifically used to:

The distinguishing code line determines the target task type information as a distribution operation task according to the updated task type parameter.

Wherein, the scheduled tasks are configured as grid tasks, and the corresponding multiple cluster devices are respectively deployed with operation systems for implementing multiple different types of tasks;

The target order data sending unit is specifically used for:

The target task type information and the target order data are sent to the plurality of cluster devices, so that the cluster devices call the operation system corresponding to the target task type information to perform an operation on the target order data.

Corresponding to Example 1, the embodiment of the present application further provides a task delivery processing device, see FIG9 , the device is applied to a task delivery client, including:

The operation option providing unit 701 is used to provide an operation option for submitting configuration information when obtaining a scheduled task configuration request submitted by a user, wherein the configuration information includes scheduled task information and interface information, and the same configuration information is shared by multiple physical stores;

The configuration information submission unit 702 is used to submit the configuration information obtained through the operation option to the task issuing server, so that after the task issuing server receives the call of the scheduled task through the interface, it can determine the target task type information associated with the scheduled task; obtain the target order data corresponding to the target task type information from the order information library and send it to the operating system corresponding to the target task type information.

Corresponding to Example 1, the embodiment of the present application further provides a task delivery processing device, see FIG10 , the device is applied to the operating system server, including:

The target order data obtaining unit 801 is used to obtain the target order data sent by the task issuing server, wherein the target order data is the target order data corresponding to the target task type information obtained from the order information library after the task issuing server determines the target task type information associated with the scheduled task calling the interface based on the configuration information shared by multiple physical stores;

The task processing unit 802 is used to perform task processing on the target order data.

Corresponding to Example 1, the embodiment of the present application further provides a task delivery processing device, see FIG11 , the device is applied to an operating system client, and includes:

The operation task information obtaining unit 901 is used to obtain the operation task information sent by the operation system server, wherein the operation task information is obtained after the operation system server performs task processing on the target order data sent by the task issuing server, and the task issuing server obtains the target order data from the order information library based on the configuration information shared by multiple physical stores;

The operation task information display unit 902 is used to display the operation task information so that the operator associated with the operation system client can perform the operation on the target order data.

In addition, an embodiment of the present application further provides an electronic device, including:

one or more processors; and

A memory associated with the one or more processors, the memory being used to store program instructions, wherein when the program instructions are read and executed by the one or more processors, the following operations are performed:

Obtaining configuration information, wherein the configuration information includes scheduled task information and interface information, wherein the scheduled task includes: tasks involved in providing fulfillment services for orders associated with a physical store, wherein there are multiple physical stores; wherein the same configuration information is shared by multiple physical stores;

After receiving a call to a scheduled task through the interface, determining target task type information associated with the scheduled task;

Acquire target order data corresponding to the target task type information from an order information database;

The target order data is sent to the operation system corresponding to the target task type information.

And an electronic device, comprising:

one or more processors; and

A memory associated with the one or more processors, the memory being used to store program instructions, wherein when the program instructions are read and executed by the one or more processors, the following operations are performed:

When obtaining a scheduled task configuration request submitted by a user, an operation option for submitting configuration information is provided. The configuration information includes scheduled task information and interface information. The same configuration information is shared by multiple physical stores.

After obtaining the configuration information through the operation options, submit it to the task issuing server, so that after the task issuing server receives the call of the scheduled task through the interface, it can determine the target task type information associated with the scheduled task; obtain the target order data corresponding to the target task type information from the order information library and send it to the operating system corresponding to the target task type information.

And an electronic device, comprising:

one or more processors; and

A memory associated with the one or more processors, the memory being used to store program instructions, wherein when the program instructions are read and executed by the one or more processors, the following operations are performed:

Obtaining target order data sent by the task issuing server, wherein the target order data is the target order data corresponding to the target task type information obtained from the order information library after the task issuing server determines the target task type information associated with the scheduled task calling the interface based on the configuration information shared by multiple physical stores;

Perform task processing on the target order data.

And an electronic device, comprising:

one or more processors; and

A memory associated with the one or more processors, the memory being used to store program instructions, wherein when the program instructions are read and executed by the one or more processors, the following operations are performed:

Obtaining the operation task information sent by the operation system server, wherein the operation task information is obtained after the operation system server performs task processing on the target order data sent by the task issuing server, and the task issuing server obtains the target order data from the order information library based on the configuration information shared by multiple physical stores;

The operation task information is displayed so that the operator associated with the operation system client can perform operations on the target order data.

12 exemplarily shows the architecture of a computer system, which may include a processor 1010, a video display adapter 1011, a disk drive 1012, an input/output interface 1013, a network interface 1014, and a memory 1020. The processor 1010, the video display adapter 1011, the disk drive 1012, the input/output interface 1013, the network interface 1014, and the memory 1020 may be communicatively connected via a communication bus 1030.

Among them, the processor 1010 can be implemented by a general-purpose CPU (Central Processing Unit), a microprocessor, an application-specific integrated circuit (Application Specific Integrated Circuit, ASIC), or one or more integrated circuits, and is used to execute relevant programs to implement the technical solution provided in this application.

The memory 1020 can be implemented in the form of ROM (Read Only Memory), RAM (Random Access Memory), static storage device, dynamic storage device, etc. The memory 1020 can store an operating system 1021 for controlling the operation of the computer system 1000, and a basic input and output system (BIOS) for controlling the low-level operation of the computer system 1000. In addition, a web browser 1023, a data storage management system 1024, and a task issuance processing system 1025, etc. can also be stored. The above-mentioned task issuance processing system 1025 can be the task issuance server that specifically implements the aforementioned steps in the embodiment of the present application. In short, when the technical solution provided by the present application is implemented by software or firmware, the relevant program code is stored in the memory 1020 and is called and executed by the processor 1010.

The input/output interface 1013 is used to connect the input/output module to realize information input and output. The input/output module can be configured in the device as a component (not shown in the figure), or it can be externally connected to the device to provide corresponding functions. The input device may include a keyboard, a mouse, a touch screen, a microphone, various sensors, etc., and the output device may include a display, a speaker, a vibrator, an indicator light, etc.

The network interface 1014 is used to connect to a communication module (not shown) to realize communication interaction between the device and other devices. The communication module can realize communication through a wired mode (such as USB, network cable, etc.) or a wireless mode (such as mobile network, WIFI, Bluetooth, etc.).

The bus 1030 comprises a pathway for transmitting information between the various components of the device (eg, the processor 1010, the video display adapter 1011, the disk drive 1012, the input/output interface 1013, the network interface 1014, and the memory 1020).

In addition, the computer system 1000 can also obtain information on specific collection conditions from the virtual resource object collection condition information database 1041 for use in condition judgment, etc.

It should be noted that, although the above device only shows a processor 1010, a video display adapter 1011, a disk drive 1012, an input/output interface 1013, a network interface 1014, a memory 1020, a bus 1030, etc., in the specific implementation process, the device may also include other components necessary for normal operation. In addition, it can be understood by those skilled in the art that the above device may also only include components necessary for implementing the solution of the present application, and does not necessarily include all the components shown in the figure.

Among them, Figure 13 exemplarily shows the architecture of an electronic device. For example, device 1100 can be a mobile phone, a computer, a digital broadcast terminal, a messaging device, a game console, a tablet device, a medical device, a fitness device, a personal digital assistant, an aircraft, etc.

13 , device 1100 may include one or more of the following components: a processing component 1102 , a memory 1104 , a power component 1106 , a multimedia component 1108 , an audio component 1110 , an input/output (I/O) interface 1112 , a sensor component 1114 , and a communication component 1116 .

The processing component 1102 generally controls the overall operation of the device 1100, such as operations associated with display, phone calls, data communications, camera operations, and recording operations. The processing component 1102 may include one or more processors 1120 to execute instructions to complete all or part of the steps of the method provided by the technical solution of the present disclosure. In addition, the processing component 1102 may include one or more modules to facilitate the interaction between the processing component 1102 and other components. For example, the processing component 1102 may include a multimedia module to facilitate the interaction between the multimedia component 1108 and the processing component 1102.

The memory 1104 is configured to store various types of data to support operations on the device 1100. Examples of such data include instructions for any application or method operating on the device 1100, contact data, phone book data, messages, pictures, videos, etc. The memory 1104 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk or optical disk.

The power supply component 1106 provides power to the various components of the device 1100. The power supply component 1106 can include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power for the device 1100.

The multimedia component 1108 includes a screen that provides an output interface between the device 1100 and the user. In some embodiments, the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive input signals from the user. The touch panel includes one or more touch sensors to sense touch, slide, and gestures on the touch panel. The touch sensor may not only sense the boundaries of the touch or slide action, but also detect the duration and pressure associated with the touch or slide operation. In some embodiments, the multimedia component 1108 includes a front camera and/or a rear camera. When the device 1100 is in an operating mode, such as a shooting mode or a video mode, the front camera and/or the rear camera may receive external multimedia data. Each front camera and rear camera may be a fixed optical lens system or have a focal length and optical zoom capability.

The audio component 1110 is configured to output and/or input audio signals. For example, the audio component 1110 includes a microphone (MIC), and when the device 1100 is in an operating mode, such as a call mode, a recording mode, and a speech recognition mode, the microphone is configured to receive an external audio signal. The received audio signal can be further stored in the memory 1104 or sent via the communication component 1116. In some embodiments, the audio component 1110 also includes a speaker for outputting audio signals.

I/O interface 1112 provides an interface between processing component 1102 and peripheral interface modules, such as keyboards, click wheels, buttons, etc. These buttons may include but are not limited to: a home button, a volume button, a start button, and a lock button.

The sensor assembly 1114 includes one or more sensors for providing various aspects of status assessment for the device 1100. For example, the sensor assembly 1114 can detect the open/closed state of the device 1100, the relative positioning of components, such as the display and keypad of the device 1100, and the sensor assembly 1114 can also detect the position change of the device 1100 or a component of the device 1100, the presence or absence of user contact with the device 1100, the orientation or acceleration/deceleration of the device 1100, and the temperature change of the device 1100. The sensor assembly 1114 may include a proximity sensor configured to detect the presence of a nearby object without any physical contact. The sensor assembly 1114 may also include an optical sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, the sensor assembly 1114 may also include an accelerometer, a gyroscope sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.

The communication component 1116 is configured to facilitate wired or wireless communication between the device 1100 and other devices. The device 1100 can access a wireless network based on a communication standard, such as WiFi, 2G or 3G, or a combination thereof. In an exemplary embodiment, the communication component 1116 receives a broadcast signal or broadcast-related information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communication component 1116 also includes a near field communication (NFC) module to facilitate short-range communication. For example, the NFC module can be implemented based on radio frequency identification (RFID) technology, infrared data association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology and other technologies.

In an exemplary embodiment, device 1100 may be implemented by one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic components to perform the above methods.

In an exemplary embodiment, a non-transitory computer-readable storage medium including instructions is also provided, such as a memory 1104 including instructions, and the above instructions can be executed by a processor 1120 of the device 1100 to complete the method provided by the technical solution of the present disclosure. For example, the non-transitory computer-readable storage medium can be a ROM, a random access memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, etc.

It can be known from the description of the above implementation methods that those skilled in the art can clearly understand that the present application can be implemented by means of software plus a necessary general hardware platform. Based on such an understanding, the technical solution of the present application can be essentially or partly contributed to the prior art in the form of a software product, which can be stored in a storage medium such as ROM/RAM, a magnetic disk, an optical disk, etc., and includes several instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to execute the methods described in the various embodiments of the present application or certain parts of the embodiments.

Each embodiment in this specification is described in a progressive manner, and the same or similar parts between the embodiments can refer to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the system or system embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can refer to the partial description of the method embodiment. The system and system embodiments described above are merely schematic, wherein the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the scheme of this embodiment. Ordinary technicians in this field can understand and implement it without paying creative labor.

The task dispatch processing method, device and electronic device provided by the present application are introduced in detail above. The principle and implementation method of the present application are explained by using specific examples in this article. The description of the above embodiments is only used to help understand the method and core idea of the present application. At the same time, for those skilled in the art, according to the idea of the present application, there will be changes in the specific implementation method and application scope. In summary, the content of this specification should not be understood as limiting the present application.

Claims (22)

1. The task issuing processing method is characterized by comprising the following steps of:

The task issuing server obtains configuration information, wherein the configuration information comprises timing task information and interface information, and the timing task comprises: tasks involved in providing fulfillment services for orders associated with physical stores, the physical stores being a plurality; the same piece of configuration information is shared by a plurality of entity shops;

after receiving the call of the timing task through the interface, determining the target task type information associated with the timing task;

acquiring target order data corresponding to the target task type information from an order information base;

And sending the target order data to an operating system corresponding to the target task type information.

2. The method of claim 1, wherein the step of determining the position of the substrate comprises,

Determining the action range information of the same piece of configuration information, and providing task issuing service for a newly added entity store by utilizing the configuration information if the newly added entity store belongs to the action range when the entity store is newly added;

the action range information is used for representing entity stores which can share the configuration information.

3. The method of claim 2, wherein the step of determining the position of the substrate comprises,

The scope includes all physical stores associated with the same retailer user.

4. The method of claim 2, wherein the step of determining the position of the substrate comprises,

The reach includes all physical stores associated with a plurality of different retailers.

5. The method of claim 1, wherein the step of determining the position of the substrate comprises,

The configuration information comprises a plurality of timing task information and a plurality of interface information corresponding to different types of tasks.

6. The method of claim 1, wherein the step of determining the position of the substrate comprises,

The configuration information comprises a plurality of timing task information and interface information corresponding to different types of tasks.

7. The method of claim 1, wherein the step of determining the position of the substrate comprises,

The configuration information comprises timing task information and interface information corresponding to different types of tasks;

The timing task information includes a task type parameter, and the interface includes: and the different code lines are used for determining the target task type information according to the task type parameters.

8. The method of claim 7, wherein the step of determining the position of the probe is performed,

The task type parameter is configured by default to issue a composite batch job task,

The determining the target task type information associated with the timing task comprises the following steps:

and the distinguishing code row determines the target task type information as a task for issuing warehouse operation according to the task type parameter configured by default.

9. The method as recited in claim 8, further comprising:

After the target order data is determined to finish the batch synthesis operation, updating the task type parameter;

the determining the target task type information associated with the timing task comprises the following steps:

and the distinguishing code row determines the target task type information as a task for issuing warehouse operation according to the updated task type parameter.

10. The method as recited in claim 8, further comprising:

After the target order data is determined to finish the batch synthesis operation, updating the task type parameter;

the determining the target task type information associated with the timing task comprises the following steps:

And the distinguishing code row determines the target task type information as a task for issuing and distributing the job according to the updated task type parameter.

11. The method of claim 1, wherein the step of determining the position of the substrate comprises,

The timing tasks are configured as grid tasks, and operating systems for realizing various tasks are respectively deployed in a plurality of corresponding cluster devices;

The sending the target order data to the operating system corresponding to the target task type information includes:

And sending the target task type information and the target order data to the plurality of cluster devices so that the cluster devices call an operating system corresponding to the target task type information to operate the target order data.

12. The task issuing processing method is characterized by comprising the following steps of:

when a task issuing client obtains a timing task configuration request submitted by a user, providing operation options for submitting configuration information, wherein the configuration information comprises timing task information and interface information, and the same configuration information is shared by a plurality of entity stores;

the configuration information is obtained through the operation options and then submitted to a task issuing server, so that the task issuing server can determine target task type information associated with the timing task after receiving the call of the timing task through the interface; and acquiring target order data corresponding to the target task type information from an order information base, and sending the target order data to an operating system corresponding to the target task type information.

13. The task issuing processing method is characterized by comprising the following steps of:

The method comprises the steps that an operating system server side obtains target order data sent by a task issuing server side, wherein the target order data is target order data corresponding to target task type information obtained from an order information base after determining target task type information related to a timing task of a calling interface by the task issuing server side based on configuration information shared by a plurality of entity stores;

And performing task processing on the target order data.

14. The task issuing processing method is characterized by comprising the following steps of:

The method comprises the steps that an operating system client obtains operation task information sent by an operating system server, the operation task information is obtained after task processing is carried out on target order data sent by a task issuing server by the operating system server, and the task issuing server obtains the target order data from an order information base based on configuration information shared by a plurality of entity stores;

and displaying the job task information so that the operator associated with the operating system client can operate the target order data.

15. The task issuing processing device is characterized by being applied to a task issuing server and comprising:

A configuration information obtaining unit, configured to obtain configuration information, where the configuration information includes timing task information and interface information, and the timing task includes: tasks involved in providing fulfillment services for orders associated with physical stores, the physical stores being a plurality; the same piece of configuration information is shared by a plurality of entity shops;

The target task type information determining unit is used for determining target task type information associated with the timing task after receiving the call of the timing task through the interface;

The target order data acquisition unit is used for acquiring target order data corresponding to the target task type information from an order information base;

And the target order data sending unit is used for sending the target order data to the operating system corresponding to the target task type information.

16. The task issuing processing device is characterized by being applied to a task issuing client and comprising:

an operation option providing unit, configured to provide operation options for submitting configuration information when obtaining a timing task configuration request submitted by a user, where the configuration information includes timing task information and interface information, and the same set of configuration information is shared by multiple entity stores;

The configuration information submitting unit is used for submitting the configuration information to a task issuing server after the configuration information is obtained through the operation options, so that the task issuing server can determine the target task type information associated with the timing task after receiving the call of the timing task through the interface; and acquiring target order data corresponding to the target task type information from an order information base, and sending the target order data to an operating system corresponding to the target task type information.

17. The task issuing processing device is characterized by being applied to an operating system server and comprising:

The system comprises a target order data acquisition unit, a task issuing server and a task information base, wherein the target order data acquisition unit is used for acquiring target order data sent by the task issuing server, wherein the target order data is target order data corresponding to target task type information acquired from an order information base after the target order data is determined by the task issuing server based on configuration information shared by a plurality of entity stores and related to a timing task of a calling interface;

And the task processing unit is used for performing task processing on the target order data.

18. A task issuing processing device, which is applied to an operating system client, and comprises:

A job task information obtaining unit, configured to obtain job task information sent by an operating system server, where the job task information is obtained after the operating system server performs task processing on target order data sent by a task issuing server, the task issuing server obtains the target order data from an order information base based on configuration information shared by a plurality of entity stores;

And the job task information display unit is used for displaying the job task information so that the operator associated with the client of the operating system can operate the target order data.

19. An electronic device, comprising:

One or more processors; and

A memory associated with the one or more processors, the memory for storing program instructions that, when read for execution by the one or more processors, perform the operations of:

obtaining configuration information, wherein the configuration information comprises timing task information and interface information, and the timing task comprises: tasks involved in providing fulfillment services for orders associated with physical stores, the physical stores being a plurality; the same piece of configuration information is shared by a plurality of entity shops;

after receiving the call of the timing task through the interface, determining the target task type information associated with the timing task;

acquiring target order data corresponding to the target task type information from an order information base;

And sending the target order data to an operating system corresponding to the target task type information.

20. An electronic device, comprising:

One or more processors; and

A memory associated with the one or more processors, the memory for storing program instructions that, when read for execution by the one or more processors, perform the operations of:

Providing operation options for submitting configuration information when a timing task configuration request submitted by a user is obtained, wherein the configuration information comprises timing task information and interface information, and the same piece of configuration information is shared by a plurality of entity stores;

the configuration information is obtained through the operation options and then submitted to a task issuing server, so that the task issuing server can determine target task type information associated with the timing task after receiving the call of the timing task through the interface; and acquiring target order data corresponding to the target task type information from an order information base, and sending the target order data to an operating system corresponding to the target task type information.

21. An electronic device, comprising:

One or more processors; and

A memory associated with the one or more processors, the memory for storing program instructions that, when read for execution by the one or more processors, perform the operations of:

acquiring target order data sent by a task issuing server, wherein the target order data is target order data corresponding to target task type information acquired from an order information base after the task issuing server determines target task type information related to a timing task of a calling interface based on configuration information shared by a plurality of entity stores;

And performing task processing on the target order data.

22. An electronic device, comprising:

One or more processors; and

A memory associated with the one or more processors, the memory for storing program instructions that, when read for execution by the one or more processors, perform the operations of:

acquiring job task information sent by an operating system server, wherein the job task information is acquired after the operating system server performs task processing on target order data sent by a task issuing server, and the task issuing server acquires the target order data from an order information base based on configuration information shared by a plurality of entity stores;

and displaying the job task information so that the operator associated with the operating system client can operate the target order data.