CN111832857A

CN111832857A - Task issuing processing method and device and electronic equipment

Info

Publication number: CN111832857A
Application number: CN201910310029.2A
Authority: CN
Inventors: 范少明
Original assignee: Alibaba Group Holding Ltd
Current assignee: Hema China Co Ltd
Priority date: 2019-04-17
Filing date: 2019-04-17
Publication date: 2020-10-27

Abstract

The embodiment of the application discloses a task issuing processing method and device and electronic equipment. The method comprises the following steps: the task issuing server side obtains configuration information, 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 a plurality of physical stores; wherein 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 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 fulfillment configuration process is facilitated to be simplified, and the later maintenance cost is reduced.

Description

Task issuing processing method and device and electronic equipment

Technical Field

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

Background

In a "new retail" business model, a retailer may open an off-line physical store, and a consumer user may make a purchase of a merchandise object directly to the off-line physical store. Meanwhile, the retailer can also provide an online shop corresponding to the physical shop through an online application program (App), and display the related information of the commodity objects provided by the physical shop to the consumer user through the online shop.

When a consumer user purchases a commodity object through the App, a target entity store which is closest to the consumer user in geographic position can be determined from entity stores set by retailers, and the App provides an online store corresponding to the target entity store for the consumer user to perform online ordering and ordering operations.

Order data submitted by a consumer user through an App can be stored in an order information base, and then a task issuing service end in a fulfillment system provides fulfillment services for orders associated with the entity shop. Specifically, the task issuing server may perform batch processing on order data associated with the same entity store according to related information included in the order data. The related information included in the order data may be identification information of the order, identification information of the target entity store, identification information of a warehouse associated with the target entity store, identification information of a delivery station associated with the target entity store, identification information of a retailer, information of a purchased commodity object, delivery address information, delivery time information, and the like.

In order to realize batch processing of order data associated with the same entity store, the task issuing server needs to provide a plurality of interfaces for realizing different types of tasks for each entity store, and correspondingly, the task issuing client needs to configure a plurality of different types of timing tasks for each entity store and specify an interface called by each timing task. Taking the entity shop a as an example, the task issuing server may provide the following interfaces:

an interface A1 for realizing the issue of order data associated with the entity shop A and synthesizing the batch job task;

an interface A2 for realizing the issuing of warehouse job tasks of order data associated with the entity shop A;

an interface a3 for realizing the delivery job task of the order data associated with the physical store a.

The corresponding task issuing client can be configured with the following timing tasks:

issuing a timing task A1 for synthesizing batch jobs, wherein the task 1 is configured with calling address information of an interface A1;

issuing a timing task A2 of warehouse operation, wherein the task 2 is configured with calling address information of an interface A2;

a timed task A3 for issuing a delivery job is issued, and the call address information of the interface A3 is arranged in task 3.

Therefore, when each timing task is started, an interface provided by the task issuing server can be called, target order data to be fulfilled in the entity shop A is obtained from the order information base, and the target order data is sent to the corresponding operation system to carry out relevant operation.

As can be seen from the above fulfillment processing process, the existing fulfillment configuration process is complex, and as the number of established entity stores increases, the number of interface information and timing task information to be maintained also increases, which results in high post-maintenance cost. In addition, when an entity store is newly added, if configured timing task information and interface information are missing, order data associated with the newly added entity store cannot be acquired for task issuing, so that the newly added entity store cannot perform normally, and the experience of a consumer user is influenced.

Disclosure of Invention

The application provides a task issuing processing method and device and electronic equipment, and a task issuing server can issue different types of tasks based on configuration information shared by a plurality of entity shops, so that the implementation configuration process is facilitated to be simplified, and the later maintenance cost is reduced.

The application provides the following scheme:

a task issuing processing method comprises the following steps:

the task issuing server side obtains configuration information, 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 a plurality of physical stores; wherein 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 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.

A task issuing processing method comprises the following steps:

the method comprises the steps that when a task issuing client side obtains a timing task configuration request submitted by a user, operation options for submitting configuration information are provided, the configuration information comprises timing task information and interface information, and the same configuration information is shared by a plurality of entity shops;

after the configuration information is obtained through the operation options, submitting the configuration information 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.

A task issuing processing method comprises the following steps:

the method comprises the steps that an operation system server side obtains target order data sent by a task issuing server side, wherein the target order data are the target order data which are obtained from an order information base and correspond to target task type information after the task issuing server side determines the target task type information related to a timing task of a calling interface based on configuration information shared by a plurality of entity shops;

and performing task processing on the target order data.

A task issuing processing method comprises the following steps:

the method comprises the steps that an operating system client obtains operating task information sent by an operating system server, the operating task information is obtained after the operating system server performs task processing on target order data sent by a task issuing 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 shops;

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

A task issuing processing device is applied to a task issuing server and comprises:

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 a plurality of physical stores; wherein 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 related to 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.

A task issuing processing device is applied to a task issuing client and comprises:

the system comprises an operation option providing unit, a timing task configuration unit and a configuration information processing unit, wherein the operation option providing unit is used for providing operation options for submitting configuration information when a timing task configuration request submitted by a user is obtained, the configuration information comprises timing task information and interface information, and the same configuration information is shared by a plurality of entity shops;

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 receives the call of the timing task through the interface and then determines the target task type information related to the timing task; 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.

A task issuing processing device is applied to an operating system server and comprises:

the system comprises a target order data obtaining unit, a task issuing server and a task information base, wherein the target order data obtaining unit is used for obtaining target order data sent by the task issuing server, and the target order data is the target order data which is obtained from the order information base and corresponds to the target task type information after the task issuing server determines the target task type information related to the timing task of a calling interface based on the configuration information shared by a plurality of entity shops;

and the task processing unit is used for carrying out task processing on the target order data.

A task issuing processing device is applied to an operating system client and comprises:

the system comprises an operation task information obtaining unit, a task information obtaining unit and a task information processing unit, wherein the operation task information is obtained by performing task processing on target order data sent by an operation system server to a task issuing 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 shops;

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 job system can operate the target order data.

An electronic device, comprising:

one or more processors; and

a memory associated with the one or more processors for storing program instructions that, when read and executed by the one or more processors, perform operations comprising:

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 a plurality of physical stores; wherein the same piece of configuration information is shared by a plurality of entity shops;

An electronic device, comprising:

one or more processors; and

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 configuration information is shared by a plurality of entity shops;

An electronic device, comprising:

one or more processors; and

the method comprises the steps of obtaining target order data sent by a task issuing server, wherein the target order data are the target order data which are obtained from an order information base and correspond to target task type information after the task issuing server determines the target task type information related to a timing task of a calling interface based on configuration information shared by a plurality of entity shops;

and performing task processing on the target order data.

An electronic device, comprising:

one or more processors; and

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

According to the specific embodiments provided herein, the present application discloses the following technical effects:

according to the embodiment of the application, the task issuing server can obtain the configuration information which can be shared by a plurality of entity shops, and the issuing processing of various different types of tasks is realized based on the timing task information and the interface information in the configuration information. Specifically, after the interface receives the call of the timing task, the target task type information associated with the timing task can be determined according to the configuration information, and then the target order data corresponding to the target task type information is acquired from the order information base to issue the task. According to the scheme, the interface and the timing task do not need to be configured for each entity shop one by one, the fulfillment configuration process is facilitated to be simplified, and the later maintenance cost is reduced. Particularly, when the newly added entity shop belongs to the range of the function of the configuration information, the target order data associated with the newly added entity shop can be obtained according to the configuration information for task issuing without independent configuration for the newly added entity shop, the situation that the task cannot be fulfilled is avoided, and the user experience is improved.

Of course, it is not necessary for any product to achieve all of the above-described advantages at the same time for the practice of the present application.

Drawings

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the embodiments will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings without creative efforts.

FIG. 1 is a schematic diagram of a system provided by an embodiment of the present application;

FIG. 2 is a schematic diagram of a first method provided by an embodiment of the present application;

FIG. 3 is a schematic illustration of an interface provided by an embodiment of the present application;

FIG. 4 is a flow chart of a second method provided by an embodiment of the present application;

FIG. 5 is a flow chart of a third method provided by embodiments of the present application;

FIG. 6 is a flow chart of a fourth method provided by embodiments of the present application;

FIG. 7 is a flow chart of a fifth method provided by embodiments of the present application;

FIG. 8 is a schematic view of a first apparatus provided by an embodiment of the present application;

FIG. 9 is a schematic diagram of a second apparatus provided by an embodiment of the present application;

FIG. 10 is a schematic diagram of a third apparatus provided by an embodiment of the present application;

FIG. 11 is a schematic view of a fourth apparatus provided by an embodiment of the present application;

FIG. 12 is a schematic diagram of an architecture of a computer system provided by an embodiment of the present application;

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

Detailed Description

The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments that can be derived from the embodiments given herein by a person of ordinary skill in the art are intended to be within the scope of the present disclosure.

In order to simplify the fulfillment configuration process, the embodiment of the application provides a tool capable of performing task issuing processing without performing separate configuration for each entity store, and the tool may include a task issuing client and a task issuing server. As shown in fig. 1, the task issuing server may be deployed on a cloud server, and provide an interface that can be shared by a plurality of physical stores; the task issuing client can be deployed on terminal equipment associated with developers, configure a timing task shared by a plurality of entity shops and an interface called by the timing task, and submit configuration information comprising timing task information and interface information to the task issuing server. Wherein, the timing task may include: tasks involved in providing fulfillment services for orders associated with the physical stores, such as issuing composite batch (hereinafter referred to as "composite batch") job tasks, issuing warehouse job tasks, and issuing delivery job tasks.

In the embodiment of the application, the configuration information submitted by the task issuing client can include various different implementation modes. For example, in one approach, the configuration information may include a plurality of timing task information and a plurality of interface information corresponding to different types of tasks. That is, the task issuing server may provide a plurality of interfaces corresponding to different types of tasks, for example, an interface 1 corresponding to issuing a batch job task, an interface 2 corresponding to issuing a warehouse job task, and an interface 3 corresponding to issuing a delivery job task. Meanwhile, the task issuing client can be configured with a plurality of timing tasks of different types, for example, a timing task 1 for issuing a combined batch job, a timing task 2 for issuing a warehouse job, and a timing task 3 for issuing a delivery job, where the timing task 1 can call the interface 1, the timing task 2 can call the interface 2, and the timing task 3 can call the interface 3. The task issuing client can submit the configuration information 1 which represents the calling relationship between the timing task and the interface to the task issuing server.

In this embodiment, a plurality of physical stores can share the above 3 timing tasks and 3 interfaces, and task issuing of order data associated with the plurality of physical stores is realized. As an example, the correspondence between the entity stores and the configuration information 1 may be as shown in table 1 below.

TABLE 1

Or, in another mode, the configuration information may include a plurality of pieces of timing task information corresponding to different types of tasks and one piece of interface information. That is to say, the task issuing server may provide a common interface 4 for a plurality of different types of tasks, and a plurality of different types of timing tasks configured by the task issuing client may all call the interface 4 to issue the tasks. For example, the timed task 1 calls the interface 4 to issue the batch job task, the timed task 2 calls the interface 4 to issue the warehouse job task, and the timed task 3 calls the interface 4 to issue the delivery job task. The task issuing client can submit the configuration information 2 representing the calling relationship between the timing task and the interface to the task issuing server.

In this embodiment, a plurality of physical stores can share the above 3 timing tasks and 1 interface, and task issuing of order data associated with the plurality of physical stores is realized. As an example, the correspondence between the physical stores and the configuration information 2 may be as shown in table 2 below.

TABLE 2

In the two modes, the timing tasks configured by the task issuing client correspond to the task types one by one, so that after the interface receives the call of the timing tasks, the target task type corresponding to the timing tasks can be determined according to the call, and then the target order data corresponding to the target task type information is acquired from the order information base for task issuing.

Or, in another mode, the configuration information may include a timing task information and an interface information corresponding to different types of tasks. That is to say, the task issuing server may provide a common interface 5 for a plurality of different types of tasks, the task issuing client may configure a common timing task 4 for a plurality of different types of tasks, and the timing task 4 may call the interface 5 to implement issuing processing of different types of tasks. Similarly, the task issuing client can submit the configuration information 3 representing the calling relationship between the timing task and the interface to the task issuing server.

In this embodiment, a plurality of physical stores can share the 1 timing task and the 1 interface, and task issuing of order data associated with the plurality of physical stores is realized. As an example, the correspondence between the physical stores and the configuration information 3 may be as shown in table 3 below.

TABLE 3

In this embodiment, the timed task 4 may be configured with task type parameters, and the interface 5 may include: the method comprises the steps of implementing common code lines of different types of tasks and distinguishing code lines capable of distinguishing the different types of tasks. Thus, after the interface 5 receives the call of the timing task 4, the distinguishing code line can determine the task type information related to the timing task according to the task type parameter. The following explains the task issuing processing procedure in the present implementation mode with reference to the flowchart shown in fig. 2.

Example 1

S101: the task issuing server side realizes a universal interface, and the universal interface comprises: the method includes implementing common lines of code for a plurality of different types of tasks and distinct lines of code that are capable of distinguishing the plurality of different types of tasks.

For the order data associated with different entity stores, the three types of tasks, namely, the issuing of the batching job task, the issuing of the warehouse job task and the issuing of the distribution job task, can be corresponding to each other, and for the different types of tasks, although the tasks are for the task issuing of the order data to be fulfilled under the type, the same operation actions may be partially executed during the implementation. For example, the order data of the to-be-issued batching job task associated with the physical store 1 is acquired from the order information base, the order data of the to-be-issued warehouse job task associated with the physical store 2 is acquired from the order information base, and the order data of the to-be-issued delivery job task associated with the physical store 3 is acquired from the order information base. As can be seen from the above example, the acquisition of order data associated with the physical store is an operation action to be performed by each type of task, and therefore, a common code line for realizing the same operation action may be included in the interface 5.

In addition, for different types of tasks, different operational actions are also performed when the tasks are implemented. For example, issuing the batching job task needs to acquire order data of the batching job task to be issued from an order information base, and send the acquired order data to a batching job system; the method comprises the steps that a warehouse operation task is issued, order data of the warehouse operation task to be issued are obtained from an order information base, and the obtained order data are sent to a warehouse operation system; the issuing and distribution operation task needs to obtain order data of the distribution operation task to be issued from an order information base and send the obtained order data to a distribution operation system. As can be seen from the above example, what type of order data to be performed is obtained, and what operating system the obtained order data is sent to is different operation actions executed by different types of tasks, so the interface 5 may include a distinguishing code line capable of distinguishing different types of tasks.

In summary, the target task type information may be determined by the distinct code lines, the common code lines and the distinct code lines may be combined to obtain a query condition, and the target order data corresponding to the target task type information may be obtained from the order information base according to the query condition.

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

Taking the configuration of the timed task 4 as an example, when the timed task configuration request submitted by the developer is obtained, the task issuing client may provide the timed task configuration interface shown in fig. 3, and through the interface, an operation option for submitting configuration information may be provided. For example, an operation option for submitting call address information of the interface 5, an operation option for submitting task parameter information, an operation option for submitting task type information, and the like may be included. After configuration information including the timing task information and the interface information is obtained through the operation options, the configuration information can be submitted to the task issuing server, so that after the task issuing server receives the call of the timing task 4 through the interface 5, the target task type information related to the timing task 4 at the moment can be determined, and task issuing processing is carried out.

The task parameter information in the embodiment of the present application may include other parameter information configured according to requirements, in addition to the task type parameter described above, which is described below by way of example.

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

For example, the task parameter information configured by the task issuing client may include query mode information, and dynamic selection may be performed between a database query mode with high real-time performance and a search engine query mode with high query speed, so as to meet different query requirements. That is, the task issuing server may obtain the target order data from the order information base based on the query mode specified by the task parameter information.

For example, the task parameter information configured by the task issuing client may include concurrency lock information. The task issuing server side can issue the concurrency lock information and the target order data to the corresponding operating system, so that the operating system server side can perform anti-concurrency processing according to the concurrency lock information, and repeated operation of the target order data is avoided. The concurrent lock information may be embodied as a database lock and a distributed lock, the database lock may further include an optimistic lock and a general mutual exclusion lock, and the distributed lock may further include a redis lock and a zokeeper lock. The task issuing client can dynamically select the concurrency lock adopted by the operating system server in a mode of modifying the concurrency lock information.

S103: the task issuing server obtains configuration information, and the configuration information is shared by a plurality of entity shops.

The interface 5 and the timing task 4 of the embodiment of the application can be reused among a plurality of entity shops, and do not need to be configured separately for each entity shop, that is, after the interface 5 realized by the task issuing server receives the call of the timing task 4, target order data associated with the entity shops within the action range of each configuration information can be obtained from the order information base, which is helpful for simplifying the fulfillment configuration process and reducing the later maintenance cost. Particularly, when a new entity shop is added, as long as the new entity shop belongs to the action range of the configuration information, the configuration information can be used for providing task issuing service for order data associated with the new entity shop.

The scope of the configuration information can be understood as which entity stores can share the configuration information. For example, in one approach, the configuration information may be scoped to the retailer dimension, i.e., all physical stores associated with the same retailer user may share a share of the configuration information. As shown in table 4 below, the task issuing client may configure a general timing task 41 for 100 physical stores opened by the retailer user 1, and submit corresponding configuration information 31 (which may include timing task information of the timing task 41 and interface information of the interface 5) to the task issuing server; the general timing task 42 is configured for 50 physical shops opened by the retailer user 2, and the corresponding configuration information 32 (which may include the timing task information of the timing task 42 and the interface information of the interface 5) is submitted to the task issuing server.

TABLE 4

In this way, the timing task information in the configuration information may further include identification information of the retailer user, so that the task delivery server determines the scope of action information of the configuration information according to the identification information. For example, if the new physical store has the identification information of the retailer user 1, it can be determined that the new physical store is within the range of the configuration information 31, and the order data associated with the new physical store can be acquired from the order information base based on the configuration information 31 to perform the task issuing process.

Alternatively, in another approach, the configuration information may be scoped to store dimensions, i.e., all physical stores associated with multiple different retailer users may share a single piece of configuration information. As shown in table 5 below, the task issuing client may configure a general timing task 43 for 100 physical stores configured by the retailer user 1 and 50 physical stores configured by the retailer user 2, and submit corresponding configuration information 33 (which may include timing task information of the timing task 43 and interface information of the interface 5) to the task issuing server. In this manner, any newly added entity store can be within the range of the configuration information 33, and therefore, the task issuing service can be provided for all the newly added entity stores based on the configuration information 33.

TABLE 5

In the embodiment of the application, each retailer user can independently develop a set of business system in a 'new retail' mode, and the entity stores associated with each retailer user share one piece of configuration information according to the method, so that the fulfillment services are provided for the orders associated with the entity stores.

In addition, some small and medium sized retail merchants may not be able to afford to consider that the cost of a retailer user to develop a business system alone can be very high. Under such circumstances, a platform providing a "new retail" solution appears, which can create a "new retail" sample plate, "copy the product capability, data capability, operation mode and other elements of the platform to the retailer user by enabling the traditional retailer user, and enable the retailer user to gradually improve the self operation capability based on the same operation standard and execution flow as the operation fields in the" new retail "system. For example, a retailer user may submit commodity information, inventory information in a warehouse, performance capability information, information of a sales end, and the like to a platform, and the platform implements support of a specific business process for the retailer user, so that the retailer user can also provide services to the outside in a "new retail" mode. In such a scenario, the platform can perform timed task configuration based on the store dimension or the retailer dimension according to the requirement, and provide fulfillment services for orders associated with the physical stores associated with each retailer user.

S104: and after receiving the call of the timing task through the interface, determining the target task type information associated with the timing task.

As described above, the task issuing server may determine the target task type information associated with the timed task according to the task type parameter in the timed task information. For example, the task is the first task executed during batch processing, so the task type parameter can be configured as the lower batch job task by default. Therefore, when the timing task 4 starts the calling interface 5, the distinguishing code line can determine the issued batch job task as the target task type according to the task type parameters, further obtain the target order data of the to-be-issued batch job task from the order information base, and send the obtained target order data to the batch job system server side for batch job.

For example, the group operation system server performs task processing on the target order data according to the picking area information (the picking area may be determined according to the type of the goods object included in the target order data, such as a fruit picking area, a seafood picking area, a vegetable picking area, etc.), the delivery address information, the delivery time information, etc., so as to combine the 20 target order data associated with the physical store 1 into two groups. Wherein, batch 1 corresponds to 8 target order data, and batch 2 corresponds to 12 target order data.

For both the warehouse issuing operation task and the issuing and distributing operation task, the tasks are triggered to be executed after the batch operation is completed, so that the task issuing server can update the task type parameters after the batch operation system is determined to complete the batch operation on the target order data, and the differentiated code line determines the warehouse issuing operation task and the issuing and distributing operation task as the target task type according to the updated task type parameters.

Generally, according to the performance logic, warehouse operation is performed to complete picking and packaging, and then distribution operation is performed to distribute the goods to the consumer user. Therefore, the task type parameter can be updated in such a way that after the batch combination operation system is determined to complete the batch combination operation on the target order data, the task issuing server can update the task type parameter into the issued warehouse operation task. Taking "1" as an example of issuing a batch job task, and "2" as an example of issuing a warehouse job task, the task type parameter may be updated to "2", so that when the timing task 4 calls the interface 5 for the 2 nd time, the differentiating code line may determine the warehouse job task issued by "2" as the target task type, further obtain the target order data of the warehouse job task to be issued from the order information base (the synthesized batch is used as the basic processing unit), and send the obtained target order data to the warehouse job system server for picking and packaging.

For example, the warehouse operation system service end performs task processing on 8 target order data corresponding to batch 1, generates 3 picking tasks and 1 packaging task according to the types of commodity objects included in the target order data, and can issue picking task information corresponding to the 3 picking tasks to a warehouse operation system client associated with a picking operator in the entity store 1 and issue packaging task information corresponding to the 1 packaging task to a warehouse operation system client associated with a packaging operator in the entity store 1.

The warehouse operation system client associated with the picking operator can display the obtained picking task information, so that the picking operator can pick 8 target order data corresponding to the batch 1. In addition, after each goods picking operator finishes the goods picking operation, all the goods can be gathered to the packing operator, so that the packing operator can conveniently carry out the packing operation according to the packing operation task information displayed by the associated warehouse operation system client.

Further, the updating of the task type parameter may also be embodied in that after the warehouse operating system is determined to complete the picking and packaging operation on the target order data, the task issuing server may update the task type parameter to issue the delivery operation task. Taking "3" as an example to represent the issued delivery job task, at this time, the task type parameter may be updated to "3", so that when the timing task 4 calls the interface 5 for the 3 rd time, the distinguishing code line may determine the issued delivery job task represented by "3" as the target task type, further obtain the target order data of the delivery job task to be issued from the order information base (still using the synthesized batch as the basic processing unit), and send the obtained target order data to the delivery job system server for delivery job.

For example, the delivery work system server performs task processing to generate 1 delivery task for 8 target order data corresponding to batch 1, and issues the delivery work task information corresponding to the delivery task to the delivery work system client associated with the delivery worker 1 according to the load condition of the delivery station associated with the entity store 1.

The client of the delivery operation system associated with the delivery operator 1 may display the obtained task information of the delivery operation, so that the delivery operator 1 performs the delivery operation on the package packaged by the 8 target order data corresponding to the batch 1.

In addition, in order to achieve the performance capability of the ultimate speed, the warehouse job task and the distribution job task may be executed out of the order. For example, after determining that the service end of the batching operation system completes the batching operation on the target order data and updates the task type parameters, the dispatching warehouse operation task and the dispatching distribution operation task can be determined as the target task type at the same time, and the dispatching processing of the two types of tasks can be respectively carried out. The two types of tasks are processed in parallel, corresponding distribution operators can be scheduled in advance while picking and packaging, and the method is beneficial to shortening of fulfillment time.

S105: and acquiring target order data corresponding to the target task type information from an order information base.

As described above, after the timed task 4 starts the call interface 5, a query condition can be obtained, and if the timed task information further includes query mode information, the task issuing server can obtain target order data corresponding to the target task type information from the order information base based on the query mode specified by the timed task 4 after obtaining the query condition.

It can be understood that the configuration information 3 in this embodiment may be shared by a plurality of physical stores, so that the target order data acquired by the task issuing server from the order information base may correspond to different physical stores, and in order to batch process the target order data associated with the same store, after the target order task is issued to the batching operation system, the batching operation system may perform grouping processing according to the store identification information in the target order data, and perform batching operation on the target order data in the same store identification information group.

S106: and sending the target order data to an operating system server corresponding to the target task type information.

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

Or, in another implementation, the task delivery client may configure the timing task as a grid task, for example, an operation option for submitting grid task type information is provided through the timing task configuration interface, and the grid task type information obtained through the operation option may be submitted to the task delivery server. That is, the timing task information may further include mesh task type information. In this way, the operating system server can be deployed on a plurality of cluster devices corresponding to the grid tasks, and each cluster device can be respectively deployed with the operating system server for realizing a plurality of different types of tasks. For example, the cluster includes 100 devices, and each device is deployed with a batch operating system server, a warehouse operating system server, and a delivery operating system server. Therefore, when the tasks are issued, the tasks of different types can be issued without distinction according to the load condition of each device, so that the operating efficiency of the operating system is improved, and the single-point fault when the single machine is abnormal can be avoided. It should be noted that, when issuing a task in this method, the target task type information and the target order data may be sent to the cluster device, so that the cluster device invokes the operating system server corresponding to the target task type information to perform an operation on the target order data.

As one example, the operating system server may obtain job capability information sent by the associated operating system client to determine a target operating system client to work on the target order data based on the job capability information. For example, in the process of commodity distribution, a plurality of distribution service providers may provide distribution services for consumer users, and when the distribution resources of the distribution service provider 1 are in shortage, the distribution operation system client associated with the distribution service provider 1 may feed back the operation capability information indicating resource shortage to the distribution operation system server, so that the distribution operation system server may determine a target distribution operator from the distribution service provider 2 with sufficient distribution resources, and issue the corresponding distribution operation to the distribution operation system client associated with the target distribution operator.

Example 2

The embodiment 2 is corresponding to the embodiment 1, and provides a task issuing processing method from the perspective of a task issuing server, and referring to fig. 4, the method may specifically include:

s201: the task issuing server side obtains configuration information, 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 a plurality of physical stores; wherein the same piece of configuration information is shared by a plurality of entity shops;

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

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

s204: and sending the target order data to an operating system corresponding to the target task type information.

Example 3

The embodiment 3 is corresponding to the embodiment 1, and provides a task issuing processing method from the perspective of a task issuing client, and referring to fig. 5, the method may specifically include:

s301: the method comprises the steps that when a task issuing client side obtains a timing task configuration request submitted by a user, operation options for submitting configuration information are provided, the configuration information comprises timing task information and interface information, and the same configuration information is shared by a plurality of entity shops;

s302: after the configuration information is obtained through the operation options, submitting the configuration information 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.

Example 4

Embodiment 4 is a method corresponding to embodiment 1, and provides a task issuing processing method from the perspective of an operating system server, and referring to fig. 6, the method may specifically include:

s401: the method comprises the steps that an operation system server side obtains target order data sent by a task issuing server side, wherein the target order data are the target order data which are obtained from an order information base and correspond to target task type information after the task issuing server side determines the target task type information related to a timing task of a calling interface based on configuration information shared by a plurality of entity shops;

s402: and performing task processing on the target order data.

Example 5

The embodiment 5 is corresponding to the embodiment 1, and provides a task issuing processing method from the perspective of an operating system client, and referring to fig. 7, the method may specifically include:

s501: the method comprises the steps that an operating system client obtains operating task information sent by an operating system server, the operating task information is obtained after the operating system server performs task processing on target order data sent by a task issuing 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 shops;

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

For the parts not described in detail in embodiments 2 to 5, reference may be made to the descriptions in the embodiments, which are not repeated herein.

Corresponding to embodiment 1, an embodiment of the present application further provides a task issuing processing device, referring to fig. 8, where the device is applied to a task issuing server, and includes:

a configuration information obtaining unit 601, 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 a plurality of physical stores; wherein the same piece of configuration information is shared by a plurality of entity shops;

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

a target order data obtaining unit 603, configured to obtain target order data corresponding to the target task type information from an order information base;

a target order data sending unit 604, configured to send the target order data to an operating system corresponding to the target task type information.

Wherein the apparatus further comprises:

and the action range information determining unit is used for determining the action range information of the same piece of configuration information, and when an entity shop is newly added, if the newly added entity shop belongs to the action range, the configuration information is used for providing task issuing service for the newly added entity shop.

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

Wherein the scope of action includes all physical stores associated with a plurality of different retailer users.

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

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

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: the method comprises the steps of realizing common code lines of different types of tasks and distinguishing code lines capable of distinguishing the different types of tasks, wherein the distinguishing code lines are used for determining the target task type information according to the task type parameters.

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

the target task type information determining unit is specifically configured to:

and the distinguishing code line determines the target task type information as a delivered warehouse operation task according to a default configured task type parameter.

Wherein the apparatus further comprises:

the task type parameter updating unit is used for updating the task type parameter after the target order data is determined to complete the synthesis batch operation;

and the distinguishing code line determines the target task type information as a delivered warehouse job task according to the updated task type parameters.

Wherein the apparatus further comprises:

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

The timing task is configured as a grid task, and the plurality of corresponding cluster devices are respectively provided with operating systems for realizing a plurality of different types of tasks;

the target order data sending unit is specifically configured to:

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.

Corresponding to embodiment 1, an embodiment of the present application further provides a task issuing processing device, referring to fig. 9, where the device is applied to a task issuing client, and includes:

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

a configuration information submitting unit 702, configured to submit the configuration information obtained through the operation option to a task issuing server, so that the task issuing server receives a call of a timing task through the interface and determines target task type information associated with the timing task; 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.

Corresponding to embodiment 1, an embodiment of the present application further provides a task issuing processing device, referring to fig. 10, where the task issuing processing device is applied to an operating system server, and includes:

a target order data obtaining unit 801, configured to obtain target order data sent by a task issuing server, where the target order data is target order data corresponding to target task type information obtained from an order information base after the task issuing server determines target task type information associated with a timing task of a call interface based on configuration information shared by multiple entity stores;

a task processing unit 802, configured to perform task processing on the target order data.

Corresponding to embodiment 1, an embodiment of the present application further provides a task issuing processing device, referring to fig. 11, where the task issuing processing device is applied to an operating system client, and includes:

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

a job task information displaying unit 902, configured to display the job task information, so that an operator associated with the job system client performs a job on the target order data.

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

one or more processors; and

And an electronic device comprising:

one or more processors; and

And an electronic device comprising:

one or more processors; and

and performing task processing on the target order data.

And an electronic device comprising:

one or more processors; and

Fig. 12 illustrates an architecture of a computer system, which may specifically 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, and the network interface 1014, and the memory 1020 may be communicatively connected by a communication bus 1030.

The processor 1010 may be implemented by a general-purpose CPU (Central Processing Unit), a microprocessor, an Application Specific Integrated Circuit (ASIC), or one or more Integrated circuits, and is configured to execute related programs to implement the technical solution provided by the present Application.

The Memory 1020 may be implemented in the form of a ROM (Read Only Memory), a RAM (Random access Memory), a static storage device, a dynamic storage device, or the like. The memory 1020 may store an operating system 1021 for controlling the operation of the computer system 1000, a Basic Input Output System (BIOS) for controlling low-level operations of the computer system 1000. In addition, a web browser 1023, a data storage management system 1024, a task issuing processing system 1025 and the like can be stored. The task issuing processing system 1025 can be a task issuing server that specifically implements the operations of the foregoing steps in this embodiment of the application. In summary, when the technical solution provided in the present application is implemented by software or firmware, the relevant program codes are stored in the memory 1020 and called for execution by the processor 1010.

The input/output interface 1013 is used for connecting an input/output module to realize information input and output. The i/o module may be configured as a component in a device (not shown) or may be external to the device to provide a corresponding function. The input devices may include a keyboard, a mouse, a touch screen, a microphone, various sensors, etc., and the output devices may include a display, a speaker, a vibrator, an indicator light, etc.

The network interface 1014 is used for connecting a communication module (not shown in the figure) to realize the communication interaction between the device and other devices. The communication module can realize communication in a wired mode (such as USB, network cable and the like) and also can realize communication in a wireless mode (such as mobile network, WIFI, Bluetooth and the like).

Bus 1030 includes a path that transfers information between various components of the device, such as processor 1010, video display adapter 1011, disk drive 1012, input/output interface 1013, network interface 1014, and memory 1020.

In addition, the computer system 1000 may also obtain information of specific obtaining conditions from the virtual resource object obtaining condition information database 1041, so as to perform condition judgment, and the like.

It should be noted that although the above devices only show the processor 1010, the video display adapter 1011, the disk drive 1012, the input/output interface 1013, the network interface 1014, the memory 1020, the bus 1030, etc., in a specific implementation, the device may also include other components necessary for normal operation. Furthermore, it will be understood by those skilled in the art that the apparatus described above may also include only the components necessary to implement the solution of the present application, and not necessarily all of the components shown in the figures.

Where fig. 13 illustratively shows the architecture of an electronic device, device 1100 may be, for example, a mobile telephone, a computer, a digital broadcast terminal, a messaging device, a gaming console, a tablet device, a medical device, a fitness device, a personal digital assistant, an aircraft, or the like.

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

The processing component 1102 generally controls the overall operation of the device 1100, such as operations associated with display, telephone calls, data communications, camera operations, and recording operations. The processing element 1102 may include one or more processors 1120 to execute instructions to perform all or a portion of the steps of the methods provided by the disclosed subject matter. Further, the processing component 1102 may include one or more modules that facilitate interaction between the processing component 1102 and other components. For example, the processing component 1102 may include a multimedia module to facilitate interaction between the multimedia component 1108 and the processing component 1102.

The memory 1104 is configured to store various types of data to support operation at the device 1100. Examples of such data include instructions for any application or method operating on device 1100, contact data, phonebook data, messages, pictures, videos, and so forth. The memory 1104 may be implemented by any type or combination of volatile or non-volatile memory devices 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 or optical disks.

A power component 1106 provides power to the various components of the device 1100. The power components 1106 may 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 a 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 an input signal from a 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 boundary of a 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 facing camera and/or a rear facing camera. The front-facing camera and/or the rear-facing camera may receive external multimedia data when the device 1100 is in an operating mode, such as a shooting mode or a video mode. 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) configured to receive external audio signals when the device 1100 is in operating modes, such as a call mode, a recording mode, and a voice recognition mode. The received audio signals may further be stored in the memory 1104 or transmitted via the communication component 1116. In some embodiments, the audio assembly 1110 further includes a speaker for outputting audio signals.

The I/O interface 1112 provides an interface between the processing component 1102 and peripheral interface modules, which may be 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 state assessment for the device 1100. For example, the sensor assembly 1114 may detect the open/closed state of the device 1100, the relative positioning of components, such as a display and keypad of the device 1100, the sensor assembly 1114 may also detect a change in the position of the device 1100 or a component of the device 1100, the presence or absence of user contact with the device 1100, orientation or acceleration/deceleration of the device 1100, and a change in the temperature 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 a light 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 acceleration sensor, 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 may 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 associated information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communications component 1116 also includes a Near Field Communication (NFC) module to facilitate short-range communications. For example, the NFC module may 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, the 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, micro-controllers, microprocessors or other electronic components for performing the above-described methods.

In an exemplary embodiment, a non-transitory computer-readable storage medium comprising instructions, such as the memory 1104 comprising instructions, executable by the processor 1120 of the device 1100 to perform the methods provided by the disclosed aspects is also provided. For example, the non-transitory computer readable storage medium may be a ROM, a Random Access Memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, and the like.

From the above description of the embodiments, it is clear to those skilled in the art that the present application can be implemented by software plus necessary general hardware platform. Based on such understanding, the technical solutions of the present application may be essentially or partially implemented in the form of a software product, which may be stored in a storage medium, such as a ROM/RAM, a magnetic disk, an optical disk, etc., and includes several instructions for enabling a computer device (which may be a personal computer, a server, or a network device, etc.) to execute the method according to the embodiments or some parts of the embodiments of the present application.

The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, the system or system embodiments are substantially similar to the method embodiments and therefore are described in a relatively simple manner, and reference may be made to some of the descriptions of the method embodiments for related points. The above-described system and system embodiments are only illustrative, wherein the units described as separate parts may or may not be physically separate, and the parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the present embodiment. One of ordinary skill in the art can understand and implement it without inventive effort.

The task issuing processing method, the task issuing processing device and the electronic equipment provided by the application are introduced in detail, a specific example is applied in the text to explain the principle and the implementation mode of the application, and the description of the embodiment is only used for helping to understand the method and the core idea of the application; meanwhile, for a person skilled in the art, according to the idea of the present application, the specific embodiments and the application range may be changed. In view of the above, the description should not be taken as limiting the application.

Claims

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

2. The method of claim 1,

and determining the scope of action information of the same piece of configuration information, and when an entity shop is newly added, if the newly added entity shop belongs to the scope of action, providing task issuing service for the newly added entity shop by using the configuration information.

3. The method of claim 2,

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

4. The method of claim 2,

the scope of coverage includes all physical stores associated with a plurality of different retailer users.

5. The method of claim 1,

6. The method of claim 1,

7. The method of claim 1,

8. The method of claim 7,

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

the determining of the target task type information associated with the timing task includes:

9. The method of claim 8, further comprising:

after the target order data are confirmed to complete the synthesis batch operation, updating the task type parameter;

10. The method of claim 8, further comprising:

11. The method of claim 1,

the timing task is configured as a grid task, and the plurality of corresponding cluster devices are respectively provided with operating systems for realizing various tasks of different types;

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

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

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

and performing task processing on the target order data.

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

15. A task issuing processing device is characterized in that the task issuing processing device is applied to a task issuing server and comprises:

16. A task issuing processing device is applied to a task issuing client and comprises:

17. A task issuing processing device is characterized in that the task issuing processing device is applied to an operating system server side and comprises:

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

19. An electronic device, comprising:

one or more processors; and

20. An electronic device, comprising:

one or more processors; and

21. An electronic device, comprising:

one or more processors; and

and performing task processing on the target order data.

22. An electronic device, comprising:

one or more processors; and